Phase 2: Freeze phase 2 scope and protocol #84

Closed
opened 2026-10-20 15:04:08 +02:00 by erikinkinen · 0 comments
Owner

Plan ID: P2-01
Record type: Gate leaf
Scientific protocol: 2.2 · Backlog revision: 2.2.1
Specification: sections 2, 6; common contracts in sections 3–5, 11 and 17.4.
Source: AES_PHASES_2_6_PLAN.md, issue heading at line 3598.
Plan SHA-256: 8acdaeb52d6a94fcad7de64d64521cd465f608344d63560b45f9202f5af71212
Protocol snapshot: Download the complete governing plan.

Goal

establish the normative specification before implementation.

Prerequisites

None.

Steps

  • Add docs/phase2.md with sections 2, 3 and 6 of this protocol and phase boundaries.
  • Add protocol-2.2 scope and the supported/unsupported/inconclusive exit language to milestone documentation.
  • Add a source-to-requirement matrix covering all eleven PDFs and the live tracker revision.

Definition of Done

every phase 2 requirement maps to a numbered issue and a validation
artifact; memory, restart and partial observation cannot be enabled.

Execution and acceptance contract

Apply the governing semantic/data/statistical contracts in sections 3–5 and the relevant phase section, plus the section-11 checks applicable to this task. Section 17.4 defines the required acceptance evidence. Store the outcome and immutable prerequisite/input/output hashes at

artifacts/backlog/2.2.1/P2-01/acceptance.json.

Only explicit dependency and parent-closure edges govern readiness; numbering adds no predecessor dependency. Checkboxes are work/acceptance items, not commit quotas. Keep implementation changes independently reviewable using the existing PR template. Execution, review and gate tasks close with their evidence/decision records and a PR only when tracked artifacts change.

An unsupported scientific effect is a valid result. Missing correctness validation, invalid inference or absent required review is not completion. Do not change endpoints, matrices, margins, inference rules or sample sizes outside the protocol change-control process.

Published backlog inventory

Download all 521 plan-to-Forgejo mappings.

The inventory includes phase, milestone, labels, assignee, parent and dependency issue numbers. All records were created open; scientific work remains pending.

<!-- aes-plan-id: P2-01; backlog-revision: 2.2.1 --> **Plan ID:** `P2-01` **Record type:** Gate leaf **Scientific protocol:** 2.2 · **Backlog revision:** 2.2.1 **Specification:** sections 2, 6; common contracts in sections 3–5, 11 and 17.4. **Source:** `AES_PHASES_2_6_PLAN.md`, issue heading at line 3598. **Plan SHA-256:** `8acdaeb52d6a94fcad7de64d64521cd465f608344d63560b45f9202f5af71212` **Protocol snapshot:** [Download the complete governing plan](https://git.erikinkinen.fi/attachments/31cb768b-4788-4e38-aba9-9d7f0d1ee16d). ## Goal establish the normative specification before implementation. ## Prerequisites None. ## Steps - [x] Add docs/phase2.md with sections 2, 3 and 6 of this protocol and phase boundaries. - [x] Add protocol-2.2 scope and the supported/unsupported/inconclusive exit language to milestone documentation. - [x] Add a source-to-requirement matrix covering all eleven PDFs and the live tracker revision. ## Definition of Done every phase 2 requirement maps to a numbered issue and a validation artifact; memory, restart and partial observation cannot be enabled. ## Execution and acceptance contract Apply the governing semantic/data/statistical contracts in sections 3–5 and the relevant phase section, plus the section-11 checks applicable to this task. Section 17.4 defines the required acceptance evidence. Store the outcome and immutable prerequisite/input/output hashes at `artifacts/backlog/2.2.1/P2-01/acceptance.json`. Only explicit dependency and parent-closure edges govern readiness; numbering adds no predecessor dependency. Checkboxes are work/acceptance items, not commit quotas. Keep implementation changes independently reviewable using the existing PR template. Execution, review and gate tasks close with their evidence/decision records and a PR only when tracked artifacts change. An unsupported scientific effect is a valid result. Missing correctness validation, invalid inference or absent required review is not completion. Do not change endpoints, matrices, margins, inference rules or sample sizes outside the protocol change-control process. ## Published backlog inventory [Download all 521 plan-to-Forgejo mappings](https://git.erikinkinen.fi/attachments/042a50d6-4784-4b03-8704-54a56fc92ce7). The inventory includes phase, milestone, labels, assignee, parent and dependency issue numbers. All records were created open; scientific work remains pending.
erikinkinen added this to the Phase 2 milestone 2026-10-20 15:04:08 +02:00
Sign in to join this conversation.
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.

Reference
erikinkinen/AES#84
No description provided.