Phase 5: Execute phase 5 and release evidence #427

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

Plan ID: P5-32
Record type: Tracking parent; no implementation PR
Scientific protocol: 2.2 · Backlog revision: 2.2.1
Specification: sections 9, 10.10, 11.1, 17.1, 17.2.
Source: AES_PHASES_2_6_PLAN.md, issue heading at line 7904.
Plan SHA-256: 8acdaeb52d6a94fcad7de64d64521cd465f608344d63560b45f9202f5af71212
Protocol snapshot: Download the complete governing plan.

Goal

complete the material phase and integrated article evidence.

Retained requirements

  • P5-32.R1: Execute pilot/freeze stages, all original phase-5 campaigns, 3072 additional AES/service reclamation pairs and 768 application conformance pairs; rebuild C5a and diagnostics.
  • P5-32.R2: Verify all material accounting, survival and recovery-contract controls.
  • P5-32.R3: Release phase-5-protocol-2.2 and update docs/phase5.md and csaI–csaIV inputs.

Child issues

Closure

This is an AND tracking parent, not an implementation task. Close it only after every child is accepted and the original parent acceptance below is verified. A permitted not_applicable child needs the signed route decision required by section 17.4.

every phase-5 diagnostic, factorial, horizon, conformance, crash and
benchmark manifest is accounted for, and F5 and independent-validation gates
pass; no predictor or new selective revocation algorithm is introduced.

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/P5-32/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.

Native blocking dependencies below represent the child-closure requirements; the parent must never block its own children.

<!-- aes-plan-id: P5-32; backlog-revision: 2.2.1 --> **Plan ID:** `P5-32` **Record type:** Tracking parent; no implementation PR **Scientific protocol:** 2.2 · **Backlog revision:** 2.2.1 **Specification:** sections 9, 10.10, 11.1, 17.1, 17.2. **Source:** `AES_PHASES_2_6_PLAN.md`, issue heading at line 7904. **Plan SHA-256:** `8acdaeb52d6a94fcad7de64d64521cd465f608344d63560b45f9202f5af71212` **Protocol snapshot:** [Download the complete governing plan](https://git.erikinkinen.fi/attachments/31cb768b-4788-4e38-aba9-9d7f0d1ee16d). ## Goal complete the material phase and integrated article evidence. ## Retained requirements - **P5-32.R1:** Execute pilot/freeze stages, all original phase-5 campaigns, 3072 additional AES/service reclamation pairs and 768 application conformance pairs; rebuild C5a and diagnostics. - **P5-32.R2:** Verify all material accounting, survival and recovery-contract controls. - **P5-32.R3:** Release phase-5-protocol-2.2 and update docs/phase5.md and csaI–csaIV inputs. ## Child issues - [ ] [P5-32-A (#428)](https://git.erikinkinen.fi/erikinkinen/AES/issues/428) — Verify phase-5 readiness and pilot capacity - [ ] [P5-32-B (#429)](https://git.erikinkinen.fi/erikinkinen/AES/issues/429) — Execute the phase-5 pilot - [ ] [P5-32-C (#430)](https://git.erikinkinen.fi/erikinkinen/AES/issues/430) — Select N5 and freeze the phase-5 production design - [ ] [P5-32-D (#431)](https://git.erikinkinen.fi/erikinkinen/AES/issues/431) — Execute the phase-5 AES production matrices - [ ] [P5-32-E (#432)](https://git.erikinkinen.fi/erikinkinen/AES/issues/432) — Execute service recovery conformance - [ ] [P5-32-F (#433)](https://git.erikinkinen.fi/erikinkinen/AES/issues/433) — Execute service crash and no-crash controls - [ ] [P5-32-G (#434)](https://git.erikinkinen.fi/erikinkinen/AES/issues/434) — Execute service reclamation evidence - [ ] [P5-32-H (#435)](https://git.erikinkinen.fi/erikinkinen/AES/issues/435) — Execute application development evidence - [ ] [P5-32-I (#436)](https://git.erikinkinen.fi/erikinkinen/AES/issues/436) — Execute service microbenchmarks - [ ] [P5-32-J (#437)](https://git.erikinkinen.fi/erikinkinen/AES/issues/437) — Produce phase-5 inference and recovery evidence - [ ] [P5-32-K (#438)](https://git.erikinkinen.fi/erikinkinen/AES/issues/438) — Review and archive the phase-5 evidence release ## Closure This is an AND tracking parent, not an implementation task. Close it only after every child is accepted and the original parent acceptance below is verified. A permitted `not_applicable` child needs the signed route decision required by section 17.4. every phase-5 diagnostic, factorial, horizon, conformance, crash and benchmark manifest is accounted for, and F5 and independent-validation gates pass; no predictor or new selective revocation algorithm is introduced. ## 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/P5-32/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. Native blocking dependencies below represent the child-closure requirements; the parent must never block its own children.
erikinkinen added this to the Phase 5 milestone 2026-10-20 15:05:00 +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.

Blocks
Depends on
Reference
erikinkinen/AES#427
No description provided.