Phase 2: Freeze scope and source traceability (#84) #607

Merged
erikinkinen merged 2 commits from phase2/p2-01-freeze-protocol into main 2026-10-20 15:38:35 +02:00
Owner

Task

Closes #84

Plan ID: P2-01 · Scientific protocol 2.2 · Backlog revision 2.2.1

Summary

Phase 2 had a published plan but no repository specification or source-to-issue traceability, and its milestone still required a positive divergence result. Freeze the governing protocol and its Phase 2 extract, map all 294 Phase 2 requirements to actual issues and acceptance paths, and replace the milestone's exit with supported/unsupported/inconclusive outcomes under the frozen evidence rules.

Scope

  • docs/phase2.md: protocol sections 2, 3 and 6 with explicit phase boundaries and the owner's one-branch/PR-per-issue execution instruction.
  • docs/research/protocol-2.2.txt: byte-identical published plan; the bulk of this diff consists of immutable protocol and tracker/CSV records.
  • Eleven historical PDF identities, 968 source/requirement links, all 521 published issue mappings and the dependency/coverage registries.
  • Milestone 3 description updated and read back; before/after evidence archived.
  • A documentation scope checker in CI and the P2-01 acceptance record with 17 output hashes.

Design intent

Preserve exact scientific contracts while making the specification and ownership reviewable from a checkout. The source register treats the PDFs as historical motivation and the protocol as the revised normative specification. Its artifact paths are planned evidence, not completed results. The milestone permits negative results but still requires valid methods, controls and required validation.

Phase discipline

The scope lock forbids memory carriers, persistence, restart, partial observation and depth-retention policies in Phase 2. Research parser enforcement remains explicitly assigned to P2-12-A with P2-16/P2-31-A rejection checks; this documentation change does not claim those implementations exist. F2.7 recovery execution remains Phase 5. No simulator semantics changed.

Verification

  • python3 tools/research/check_phase2_scope.py --workspace ..: passed; all eleven local PDF digests match, all 116 Phase 2 records and 294 requirements are mapped, and the three extracted protocol sections match after presentation normalization.
  • The same checker without the workspace option passes for a standalone checkout.
  • All 17 acceptance output hashes independently checked.
  • All eight repository hooks passed; actual signed commits and push hooks passed without bypass.
  • Markdown CLI and git diff --check: passed.
  • Required Forgejo checks must pass at the PR head before merge.

Notes

The local hook defect found during this work was filed as #605 and resolved separately in #606. The frozen tracker snapshot predates that maintenance issue; it preserves the 521 planned records and does not claim to be a continuously updated inventory.

# Task Closes #84 **Plan ID:** `P2-01` · Scientific protocol 2.2 · Backlog revision 2.2.1 ## Summary Phase 2 had a published plan but no repository specification or source-to-issue traceability, and its milestone still required a positive divergence result. Freeze the governing protocol and its Phase 2 extract, map all 294 Phase 2 requirements to actual issues and acceptance paths, and replace the milestone's exit with supported/unsupported/inconclusive outcomes under the frozen evidence rules. ## Scope - `docs/phase2.md`: protocol sections 2, 3 and 6 with explicit phase boundaries and the owner's one-branch/PR-per-issue execution instruction. - `docs/research/protocol-2.2.txt`: byte-identical published plan; the bulk of this diff consists of immutable protocol and tracker/CSV records. - Eleven historical PDF identities, 968 source/requirement links, all 521 published issue mappings and the dependency/coverage registries. - Milestone 3 description updated and read back; before/after evidence archived. - A documentation scope checker in CI and the P2-01 acceptance record with 17 output hashes. ## Design intent Preserve exact scientific contracts while making the specification and ownership reviewable from a checkout. The source register treats the PDFs as historical motivation and the protocol as the revised normative specification. Its artifact paths are planned evidence, not completed results. The milestone permits negative results but still requires valid methods, controls and required validation. ## Phase discipline The scope lock forbids memory carriers, persistence, restart, partial observation and depth-retention policies in Phase 2. Research parser enforcement remains explicitly assigned to P2-12-A with P2-16/P2-31-A rejection checks; this documentation change does not claim those implementations exist. F2.7 recovery execution remains Phase 5. No simulator semantics changed. ## Verification - `python3 tools/research/check_phase2_scope.py --workspace ..`: passed; all eleven local PDF digests match, all 116 Phase 2 records and 294 requirements are mapped, and the three extracted protocol sections match after presentation normalization. - The same checker without the workspace option passes for a standalone checkout. - All 17 acceptance output hashes independently checked. - All eight repository hooks passed; actual signed commits and push hooks passed without bypass. - Markdown CLI and `git diff --check`: passed. - Required Forgejo checks must pass at the PR head before merge. ## Notes The local hook defect found during this work was filed as #605 and resolved separately in #606. The frozen tracker snapshot predates that maintenance issue; it preserves the 521 planned records and does not claim to be a continuously updated inventory.
erikinkinen added this to the Phase 2 milestone 2026-10-20 15:35:54 +02:00
Phase 2: Record scope acceptance evidence (#84)
All checks were successful
markdownlint / markdown-lint (pull_request) Successful in 21s
clang-format / check-format (pull_request) Successful in 22s
ci / smoke (pull_request) Successful in 2m23s
markdownlint / markdown-lint (push) Successful in 13s
clang-format / check-format (push) Successful in 15s
ci / smoke (push) Successful in 1m56s
7fe60aa840
Sign in to join this conversation.
No reviewers
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set

Reference
erikinkinen/AES!607
No description provided.