Phase 6: Expand csaII into a complete article #543
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
#588 Phase 6: Update book framework and methodology
erikinkinen/AES
#584 Phase 6: Decide standalone merger and report packaging
erikinkinen/AES
#594 Phase 6: Review csaII and resolve its scientific comments
erikinkinen/AES
#545 Phase 6: Write csaII formal model or method
erikinkinen/AES
#544 Phase 6: Write csaII context and semantic contract
erikinkinen/AES
#552 Phase 6: Integrate and audit the complete csaII
erikinkinen/AES
#550 Phase 6: Write csaII introduction abstract and conclusion
erikinkinen/AES
#551 Phase 6: Complete csaII appendices and artifact statement
erikinkinen/AES
#546 Phase 6: Write csaII completed study design
erikinkinen/AES
#547 Phase 6: Write csaII complete results
erikinkinen/AES
#548 Phase 6: Write csaII interpretation and validity limits
erikinkinen/AES
#549 Phase 6: Write csaII related-work comparison
erikinkinen/AES
Reference
erikinkinen/AES#543
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-31Record type: Tracking parent; no implementation PR
Scientific protocol: 2.2 · Backlog revision: 2.2.1
Specification: sections 11.3–11.5, 11.7.
Source:
AES_PHASES_2_6_PLAN.md, issue heading at line 9343.Plan SHA-256:
8acdaeb52d6a94fcad7de64d64521cd465f608344d63560b45f9202f5af71212Protocol snapshot: Download the complete governing plan.
Goal
Write the full csaII manuscript from the completed analysis.
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.csaII is a full readable evidence-grounded manuscript, with no unfilled results placeholders; report/merger status is preserved.
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-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.