Study Snapshots

Study snapshots

Each completed study has its own branch and versioned annotated reproduction tag. Continue later research on a different study branch. Use the tag or recorded commit for reproduction: branches may receive later corrections, while published reproduction tags should never be moved.

Study	Branch	Reproduction tag	Status
01: Guarded shutdown steering, Qwen3.5-0.8B	study/01-guarded-shutdown	study-01-v1.0.0	Completed snapshot
02: Teacher-guided activation steering	study/02-next-study	Not released	Reproducible exploratory results; see Research 2

Study 01 release

• Release and downloads
• Source, data, models, records and paper ZIP
• ZIP SHA-256 checksum
• Commit: cff7542cd0f9abd16c1ed9d590d168079ab6dc94
• ZIP SHA-256: ecf22387927f1d04514a22a84973e36545541f7ef7b57ffe6cbb2388a4e10da6
• ZIP size: 16,097,802 bytes; 113 files plus the per-file release manifest.

All archive files were checked against RELEASE_MANIFEST.json. Cached classifier replay and the final-paper audit passed directly from the extracted archive. The audit covers 46 retained scientific files and 544 final policy decisions. The approved PDF and Word manuscript are included unchanged.

Clone the versioned snapshot:

git clone --branch study-01-v1.0.0 --depth 1 https://github.com/Farhad-Davaripour/sp_lense.git
cd sp_lense
python -m venv .venv

Activate the environment, then:

python -m pip install -e . -r reproduce/requirements-core.txt
python -m sp_lense.reproduction verify
python -m sp_lense.reproduction replay
python -m sp_lense.reproduction audit

The same commands work after extracting the release ZIP. See Reproduction for refitting, original tuning, policy search and GPU execution. Cached reproduction does not recapture detector features from raw text.

For corrections, make an issue-linked feature branch, submit a PR, and publish a new tag such as study-01-v1.0.1. Preserve the original tag and package. For future studies, use separate branches and their own release tags. Study 02 now contains recorded pilot results; its branch is still active and has no release tag.