Phase 6: Lock article plans and implement evidence-to-prose exports #526
Labels
No labels
bug
cli
core
docs
event
experiment
figure
invariant
metrics
oracle
phase-0
phase-1
phase-2
phase-3
phase-4
phase-5
phase-6
provenance
revocation
tests
workload
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Blocks
Depends on
#534 Phase 6: Write csaI context and semantic contract
erikinkinen/AES
#539 Phase 6: Write csaI related-work comparison
erikinkinen/AES
#544 Phase 6: Write csaII context and semantic contract
erikinkinen/AES
#549 Phase 6: Write csaII related-work comparison
erikinkinen/AES
#559 Phase 6: Write csaIII related-work comparison
erikinkinen/AES
#554 Phase 6: Write csaIII context and semantic contract
erikinkinen/AES
#564 Phase 6: Write csaIV context and semantic contract
erikinkinen/AES
#574 Phase 6: Write csaV context and semantic contract
erikinkinen/AES
#569 Phase 6: Write csaIV related-work comparison
erikinkinen/AES
#579 Phase 6: Write csaV related-work comparison
erikinkinen/AES
#527 Phase 6: Validate manuscript evidence locks
erikinkinen/AES
#528 Phase 6: Export numerical prose inputs
erikinkinen/AES
#529 Phase 6: Export manuscript figures and result indices
erikinkinen/AES
#530 Phase 6: Validate manuscript claims and coverage
erikinkinen/AES
#531 Phase 6: Pin and automate manuscript builds
erikinkinen/AES
#532 Phase 6: Freeze the five concrete article writing plans
erikinkinen/AES
Reference
erikinkinen/AES#526
Loading…
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Plan ID:
P6-29Record 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:
8acdaeb52d6a94fcad7de64d64521cd465f608344d63560b45f9202f5af71212Protocol snapshot: Download the complete governing plan.
Goal
Prepare the concrete writing inputs for all five complete manuscripts.
Retained requirements
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_applicablechild 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.