Add depth-degradation evaluation infrastructure#5
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
This PR adds compute-independent depth-degradation analysis for saved Scenario 1 probe scores. It compares matched 2-hop and 3-hop trajectories using AUROC, Brier score, ECE, Temporal Divergence, and match-group bootstrap confidence intervals.
It does not load a model, start a GPU, call Modal, generate trajectories, or call an LLM judge.
What changed
src/analysis/depth_degradation.pyfor depth metrics and paired 3-hop minus 2-hop comparisons.src/analysis/splits.pyto keep complete match groups together and prevent leakage across splits.scripts/03_probe_analysis/06_analyze_depth_degradation.py.injection_presentseparate fromtrajectory_action_executed.Label rule
latent_compromise_status: candidatemarks a trajectory for later mechanistic review. It is not a confirmed latent-compromise label. A propagated or blocked run remains a black-box non-compromise unless the executor action fired.Current boundaries
Validation
174 passed20 passed--help: passedgit diff --check: passedReview focus