Phase 2: Map normative requirements to artifacts #188

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

Plan ID: P2-29-C
Record type: Implementation leaf
Scientific protocol: 2.2 · Backlog revision: 2.2.1
Specification: sections 2.5, 2.6, 4.5, 4.6, 6.6, 11.3–11.7, 17.4; parent requirements and common section-11/17.4 gates apply.
Source: AES_PHASES_2_6_PLAN.md, issue heading at line 4882.
Plan SHA-256: 8acdaeb52d6a94fcad7de64d64521cd465f608344d63560b45f9202f5af71212
Protocol snapshot: Download the complete governing plan.
Tracking parent: P2-29 (#185).

Goal

Make the strengthened contribution and its execution manifest reviewable.

Applicable parent requirements

  • P2-29.R3: Map every new normative requirement to issue IDs and enforce pre-pilot prerequisite hashes.

Prerequisites

Steps

  • Create requirements.csv with phase, owning task, artifact and prerequisite hashes.

Definition of Done

Every normative addition is mapped and missing pre-pilot evidence is rejected.

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-29-C/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.

<!-- aes-plan-id: P2-29-C; backlog-revision: 2.2.1 --> **Plan ID:** `P2-29-C` **Record type:** Implementation leaf **Scientific protocol:** 2.2 · **Backlog revision:** 2.2.1 **Specification:** sections 2.5, 2.6, 4.5, 4.6, 6.6, 11.3–11.7, 17.4; parent requirements and common section-11/17.4 gates apply. **Source:** `AES_PHASES_2_6_PLAN.md`, issue heading at line 4882. **Plan SHA-256:** `8acdaeb52d6a94fcad7de64d64521cd465f608344d63560b45f9202f5af71212` **Protocol snapshot:** [Download the complete governing plan](https://git.erikinkinen.fi/attachments/31cb768b-4788-4e38-aba9-9d7f0d1ee16d). **Tracking parent:** [P2-29 (#185)](https://git.erikinkinen.fi/erikinkinen/AES/issues/185). ## Goal Make the strengthened contribution and its execution manifest reviewable. ## Applicable parent requirements - **P2-29.R3:** Map every new normative requirement to issue IDs and enforce pre-pilot prerequisite hashes. ## Prerequisites - [P2-29-A (#186)](https://git.erikinkinen.fi/erikinkinen/AES/issues/186) - [P2-29-B (#187)](https://git.erikinkinen.fi/erikinkinen/AES/issues/187) ## Steps - [ ] Create requirements.csv with phase, owning task, artifact and prerequisite hashes. ## Definition of Done Every normative addition is mapped and missing pre-pilot evidence is rejected. ## 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-29-C/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.
erikinkinen added this to the Phase 2 milestone 2026-10-20 15:04:22 +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#188
No description provided.