Phase 6: Prepare merger manuscripts and update the book synthesis #583
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
#598 Phase 6: Review the book synthesis
erikinkinen/AES
#599 Phase 6: Review the combined manuscript when required
erikinkinen/AES
#586 Phase 6: Integrate the combined results and appendices
erikinkinen/AES
#587 Phase 6: Write the combined framing and interpretation
erikinkinen/AES
#584 Phase 6: Decide standalone merger and report packaging
erikinkinen/AES
#589 Phase 6: Update book questions and article summary
erikinkinen/AES
#588 Phase 6: Update book framework and methodology
erikinkinen/AES
#585 Phase 6: Integrate the required combined technical core
erikinkinen/AES
#590 Phase 6: Write the book synthesis and conclusions
erikinkinen/AES
#591 Phase 6: Finalize book abstract and chapter integration
erikinkinen/AES
Reference
erikinkinen/AES#583
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-35Record type: Tracking parent; no implementation PR
Scientific protocol: 2.2 · Backlog revision: 2.2.1
Specification: sections 2.5, 11.6.
Source:
AES_PHASES_2_6_PLAN.md, issue heading at line 9803.Plan SHA-256:
8acdaeb52d6a94fcad7de64d64521cd465f608344d63560b45f9202f5af71212Protocol snapshot: Download the complete governing plan.
Goal
Consolidate actual contributions without duplicating evidence or losing full reports.
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.The book reflects actual findings and manuscript packaging; shared evidence is not presented as independent replication.
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-35/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.