Phase 2: Freeze phase 2 scope and protocol #84
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
#85 Phase 2: Record and preserve legacy behavior
erikinkinen/AES
#88 Phase 2: Introduce operation counter contracts
erikinkinen/AES
#116 Phase 2: Lock the analysis environment
erikinkinen/AES
#124 Phase 2: Archive literature searches and source identities
erikinkinen/AES
#148 Phase 2: Pin and boot the seL4 harness
erikinkinen/AES
Reference
erikinkinen/AES#84
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:
P2-01Record type: Gate leaf
Scientific protocol: 2.2 · Backlog revision: 2.2.1
Specification: sections 2, 6; common contracts in sections 3–5, 11 and 17.4.
Source:
AES_PHASES_2_6_PLAN.md, issue heading at line 3598.Plan SHA-256:
8acdaeb52d6a94fcad7de64d64521cd465f608344d63560b45f9202f5af71212Protocol snapshot: Download the complete governing plan.
Goal
establish the normative specification before implementation.
Prerequisites
None.
Steps
Definition of Done
every phase 2 requirement maps to a numbered issue and a validation
artifact; memory, restart and partial observation cannot be enabled.
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/P2-01/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.
Published backlog inventory
Download all 521 plan-to-Forgejo mappings.
The inventory includes phase, milestone, labels, assignee, parent and dependency issue numbers. All records were created open; scientific work remains pending.