Phase 5: Establish the recovery contribution against exact prior contracts #423

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

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

Goal

Resolve whether recovery-safe withdrawal reclamation adds a substantive result.

Retained requirements

  • P5-31.R1: Complete every fixed property row in recovery_contract_comparison.csv with primary-source locators and explicit unspecified/excluded statuses.
  • P5-31.R2: Map F5.4–F5.6 premises to enforcement, trust, positive fixtures, faults and costs; check the minimal additional-consequence witness and I/IV ownership.
  • P5-31.R3: Freeze the specialist-reviewed contribution route and implement phase-5 qualification/resource reporting, preserving full-report output if novelty is absent.

Child issues

  • P5-31-A (#424) — Compare exact recovery properties with prior work
  • P5-31-B (#425) — Map recovery proof premises to implementations and faults
  • P5-31-C (#426) — Freeze the recovery contribution qualification

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.

General rollback/pruning/lease techniques are background; any additional guarantee has an explicit comparison and evidence path.

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-31/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-31; backlog-revision: 2.2.1 --> **Plan ID:** `P5-31` **Record type:** Tracking parent; no implementation PR **Scientific protocol:** 2.2 · **Backlog revision:** 2.2.1 **Specification:** sections 9.10. **Source:** `AES_PHASES_2_6_PLAN.md`, issue heading at line 7855. **Plan SHA-256:** `8acdaeb52d6a94fcad7de64d64521cd465f608344d63560b45f9202f5af71212` **Protocol snapshot:** [Download the complete governing plan](https://git.erikinkinen.fi/attachments/31cb768b-4788-4e38-aba9-9d7f0d1ee16d). ## Goal Resolve whether recovery-safe withdrawal reclamation adds a substantive result. ## Retained requirements - **P5-31.R1:** Complete every fixed property row in recovery_contract_comparison.csv with primary-source locators and explicit unspecified/excluded statuses. - **P5-31.R2:** Map F5.4–F5.6 premises to enforcement, trust, positive fixtures, faults and costs; check the minimal additional-consequence witness and I/IV ownership. - **P5-31.R3:** Freeze the specialist-reviewed contribution route and implement phase-5 qualification/resource reporting, preserving full-report output if novelty is absent. ## Child issues - [ ] [P5-31-A (#424)](https://git.erikinkinen.fi/erikinkinen/AES/issues/424) — Compare exact recovery properties with prior work - [ ] [P5-31-B (#425)](https://git.erikinkinen.fi/erikinkinen/AES/issues/425) — Map recovery proof premises to implementations and faults - [ ] [P5-31-C (#426)](https://git.erikinkinen.fi/erikinkinen/AES/issues/426) — Freeze the recovery contribution qualification ## 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. General rollback/pruning/lease techniques are background; any additional guarantee has an explicit comparison and evidence path. ## 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-31/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:04:59 +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#423
No description provided.