Phase 6: Lock article plans and implement evidence-to-prose exports #526

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

Plan ID: P6-29
Record type: Tracking parent; no implementation PR
Scientific protocol: 2.2 · Backlog revision: 2.2.1
Specification: sections 4.6, 11.3, 11.5, 11.7.
Source: AES_PHASES_2_6_PLAN.md, issue heading at line 9146.
Plan SHA-256: 8acdaeb52d6a94fcad7de64d64521cd465f608344d63560b45f9202f5af71212
Protocol snapshot: Download the complete governing plan.

Goal

Prepare the concrete writing inputs for all five complete manuscripts.

Retained requirements

  • P6-29.R1: Create the article_plan, result_inventory, claim_map and initial publication decisions against the final evidence lock and exact existing chapter paths.
  • P6-29.R2: Implement aes_manuscripts evidence-check/export/claim-check/build/release-check, numeric macros and same-data PDF figure generation.
  • P6-29.R3: Pin the manuscript toolchain, map every central result/display/appendix requirement and verify an export/build fixture without reading unapproved datasets.

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.

Writing consumes frozen evidence; every required result has a planned source location and missing evidence has an explicit status.

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/P6-29/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: P6-29; backlog-revision: 2.2.1 --> **Plan ID:** `P6-29` **Record type:** Tracking parent; no implementation PR **Scientific protocol:** 2.2 · **Backlog revision:** 2.2.1 **Specification:** sections 4.6, 11.3, 11.5, 11.7. **Source:** `AES_PHASES_2_6_PLAN.md`, issue heading at line 9146. **Plan SHA-256:** `8acdaeb52d6a94fcad7de64d64521cd465f608344d63560b45f9202f5af71212` **Protocol snapshot:** [Download the complete governing plan](https://git.erikinkinen.fi/attachments/31cb768b-4788-4e38-aba9-9d7f0d1ee16d). ## Goal Prepare the concrete writing inputs for all five complete manuscripts. ## Retained requirements - **P6-29.R1:** Create the article_plan, result_inventory, claim_map and initial publication decisions against the final evidence lock and exact existing chapter paths. - **P6-29.R2:** Implement aes_manuscripts evidence-check/export/claim-check/build/release-check, numeric macros and same-data PDF figure generation. - **P6-29.R3:** Pin the manuscript toolchain, map every central result/display/appendix requirement and verify an export/build fixture without reading unapproved datasets. ## Child issues - [ ] [P6-29-A (#527)](https://git.erikinkinen.fi/erikinkinen/AES/issues/527) — Validate manuscript evidence locks - [ ] [P6-29-B (#528)](https://git.erikinkinen.fi/erikinkinen/AES/issues/528) — Export numerical prose inputs - [ ] [P6-29-C (#529)](https://git.erikinkinen.fi/erikinkinen/AES/issues/529) — Export manuscript figures and result indices - [ ] [P6-29-D (#530)](https://git.erikinkinen.fi/erikinkinen/AES/issues/530) — Validate manuscript claims and coverage - [ ] [P6-29-E (#531)](https://git.erikinkinen.fi/erikinkinen/AES/issues/531) — Pin and automate manuscript builds - [ ] [P6-29-F (#532)](https://git.erikinkinen.fi/erikinkinen/AES/issues/532) — Freeze the five concrete article writing plans ## 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. Writing consumes frozen evidence; every required result has a planned source location and missing evidence has an explicit status. ## 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/P6-29/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 6 milestone 2026-10-20 15:05:16 +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#526
No description provided.