Main SR files
Files that carry resume, backlog and SR controls.
Main SR files
Once SR is installed in a repo, some files become the sources of resume and control.
| File | Practical role |
|---|---|
AGENTS.md | Instructions Codex must follow in the repo. |
docs/CURRENT_STATE.md | Short product state and next safe action. |
docs/codex/PROJECT_PROFILE.yaml | Project profile: knowledge mode, skills policy, SR obligations. |
docs/codex/SKILL_DIGEST.md | Short router to choose skills without loading everything. |
docs/codex/SKILL_MAP.md | More complete declaration of available skills. |
docs/codex/SR_LOTS.yaml | Living SR lot backlog. |
docs/codex/SR_PASSES.yaml | Optional orchestration of several lots into bounded passes. |
docs/codex/SR_INBOX.yaml | Inbox for ideas, bugs, feedback and decisions to triage. |
docs/codex/CODEBASE_MAP.md | Short codebase map. |
docs/codex/tasks/... | Detailed memory of lots and tasks. |
scripts/codex/ | Verification, audit, context and contract scripts. |
Lots and passes
SR_LOTS.yaml remains the source of truth for the atomic backlog. Each lot carries its scope, acceptance criteria, authorized paths, stop conditions, and status.
SR_PASSES.yaml only organizes the execution of several related lots. It describes included lots, order, dependencies, shared preflight, human validations, external actions, possible migrations, and grouped E2E tests.
The prompt docs/codex/prompts/08_define_sr_passes_from_lots.md proposes or updates these passes from existing lots. The script scripts/codex/validate_pass_contract.py verifies that lot references and dependency order are coherent.
If you are lost
Ask Codex to reread in this order:
AGENTS.md
docs/CURRENT_STATE.md
docs/codex/SR_BOOTSTRAP.md
docs/codex/SR_LOTS.yaml
docs/codex/SR_PASSES.yaml
latest memory in docs/codex/tasks/Important
These files do not replace reading real code. They guide Codex, but code, tests and logs decide.