Phase 4: Execute phase 4 and release evidence #319
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
#331 Phase 5: Implement regions and deterministic allocation
erikinkinen/AES
#330 Phase 5: Freeze material authority and recovery semantics
erikinkinen/AES
#332 Phase 5: Implement authenticated token carriers
erikinkinen/AES
#333 Phase 5: Implement release and retyping events
erikinkinen/AES
#336 Phase 5: Implement quarantine region reuse
erikinkinen/AES
#335 Phase 5: Implement permissive region reuse
erikinkinen/AES
#342 Phase 5: Implement crash transitions
erikinkinen/AES
#341 Phase 5: Filter and purge checkpoint authority
erikinkinen/AES
#338 Phase 5: Implement provenance-guarded loading
erikinkinen/AES
#337 Phase 5: Implement scrub cleanup policy
erikinkinen/AES
#340 Phase 5: Capture and rotate modeled images
erikinkinen/AES
#345 Phase 5: Validate restored tokens and origins
erikinkinen/AES
#349 Phase 5: Replay and hash material recovery state
erikinkinen/AES
#348 Phase 5: Encode version-6 material transitions
erikinkinen/AES
#346 Phase 5: Implement validity durability
erikinkinen/AES
#344 Phase 5: Select images and recreate resource mappings
erikinkinen/AES
#350 Phase 5: Implement lifecycle tapes and matrices
erikinkinen/AES
#357 Phase 5: Prepare the csaII recovery-view supplement
erikinkinen/AES
#352 Phase 5: Implement csaIV statistical analysis
erikinkinen/AES
#356 Phase 5: Prepare the csaI material witness supplement
erikinkinen/AES
#351 Phase 5: Implement residue and transition measurements
erikinkinen/AES
#353 Phase 5: Produce memory and recovery figures
erikinkinen/AES
#354 Phase 5: Validate material semantics
erikinkinen/AES
#363 Phase 5: Store durable operational authority records
erikinkinen/AES
#360 Phase 5: Separate cleanup and durability controls
erikinkinen/AES
#361 Phase 5: Plan factorial and long-horizon comparisons
erikinkinen/AES
#370 Phase 5: Minimize weakened-assumption witnesses
erikinkinen/AES
#364 Phase 5: Commit withdrawal before acknowledgement
erikinkinen/AES
#372 Phase 5: Implement framed service transport
erikinkinen/AES
#369 Phase 5: Enumerate the bounded crash model
erikinkinen/AES
#368 Phase 5: Check the remaining recovery obligations F5.2/F5.3
erikinkinen/AES
#367 Phase 5: Prove acknowledged-withdrawal safety F5.1
erikinkinen/AES
#365 Phase 5: Enforce recovery load and use barriers
erikinkinen/AES
#377 Phase 5: Export service monitoring and source identity
erikinkinen/AES
#378 Phase 5: Run the standalone capability-service suite
erikinkinen/AES
#380 Phase 5: Inject deterministic process crashes
erikinkinen/AES
#376 Phase 5: Publish service checkpoints atomically
erikinkinen/AES
#375 Phase 5: Make service mutations idempotent
erikinkinen/AES
#374 Phase 5: Persist service authority transactions
erikinkinen/AES
#373 Phase 5: Authenticate service tokens and protected reads
erikinkinen/AES
#381 Phase 5: Emulate storage-prefix loss independently
erikinkinen/AES
#382 Phase 5: Plan and compare the crash campaign
erikinkinen/AES
#384 Phase 5: Generate three-way conformance tapes
erikinkinen/AES
#385 Phase 5: Compare recovery observations and evidence
erikinkinen/AES
#390 Phase 5: Implement factorial pilot precision stages
erikinkinen/AES
#388 Phase 5: Define monitor availability and latency references
erikinkinen/AES
#387 Phase 5: Implement service microbenchmark collection
erikinkinen/AES
#395 Phase 5: Enforce inherited authenticated expiry
erikinkinen/AES
#403 Phase 5: Prove recent-volume retention bound F5.5
erikinkinen/AES
#401 Phase 5: Implement the lease-only comparator
erikinkinen/AES
#400 Phase 5: Implement the generation-reset comparator
erikinkinen/AES
#399 Phase 5: Collect expired authority subtrees transactionally
erikinkinen/AES
#402 Phase 5: Prove collection safety and selectivity F5.4
erikinkinen/AES
#397 Phase 5: Check expiry and trusted-time boundaries
erikinkinen/AES
#408 Phase 5: Report contract-specific reclamation outcomes
erikinkinen/AES
#407 Phase 5: Plan the four-contract reclamation campaign
erikinkinen/AES
#405 Phase 5: Explore collection crashes and negative controls
erikinkinen/AES
#404 Phase 5: Prove the recovery information boundary F5.6
erikinkinen/AES
#411 Phase 5: Implement the sharing workflow
erikinkinen/AES
#412 Phase 5: Implement the sharing requirement oracle
erikinkinen/AES
#415 Phase 5: Implement the plugin workflow
erikinkinen/AES
#416 Phase 5: Implement the plugin requirement oracle
erikinkinen/AES
#413 Phase 5: Implement the job workflow
erikinkinen/AES
#414 Phase 5: Implement the job requirement oracle
erikinkinen/AES
#419 Phase 5: Review and freeze the sharing case contract
erikinkinen/AES
#417 Phase 5: Plan application development conformance
erikinkinen/AES
#422 Phase 5: Validate application and recovery prerequisites
erikinkinen/AES
#420 Phase 5: Review and freeze the job case contract
erikinkinen/AES
#421 Phase 5: Review and freeze the plugin case contract
erikinkinen/AES
#424 Phase 5: Compare exact recovery properties with prior work
erikinkinen/AES
#431 Phase 5: Execute the phase-5 AES production matrices
erikinkinen/AES
#426 Phase 5: Freeze the recovery contribution qualification
erikinkinen/AES
#429 Phase 5: Execute the phase-5 pilot
erikinkinen/AES
#428 Phase 5: Verify phase-5 readiness and pilot capacity
erikinkinen/AES
#432 Phase 5: Execute service recovery conformance
erikinkinen/AES
#430 Phase 5: Select N5 and freeze the phase-5 production design
erikinkinen/AES
#436 Phase 5: Execute service microbenchmarks
erikinkinen/AES
#433 Phase 5: Execute service crash and no-crash controls
erikinkinen/AES
#434 Phase 5: Execute service reclamation evidence
erikinkinen/AES
#435 Phase 5: Execute application development evidence
erikinkinen/AES
#437 Phase 5: Produce phase-5 inference and recovery evidence
erikinkinen/AES
#438 Phase 5: Review and archive the phase-5 evidence release
erikinkinen/AES
#320 Phase 4: Verify phase-4 readiness and pilot capacity
erikinkinen/AES
#321 Phase 4: Execute the phase-4 pilot
erikinkinen/AES
#323 Phase 4: Execute the phase-4 AES production matrices
erikinkinen/AES
#322 Phase 4: Select N4 and freeze the phase-4 AES design
erikinkinen/AES
#329 Phase 4: Review and archive the phase-4 evidence release
erikinkinen/AES
#325 Phase 4: Execute native selector-rule calibration
erikinkinen/AES
#326 Phase 4: Freeze native coefficients and selection rules
erikinkinen/AES
#327 Phase 4: Execute native evaluation
erikinkinen/AES
#328 Phase 4: Produce phase-4 inference and design-rule evidence
erikinkinen/AES
#324 Phase 4: Execute native primitive calibration
erikinkinen/AES
Reference
erikinkinen/AES#319
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:
P4-24Record type: Tracking parent; no implementation PR
Scientific protocol: 2.2 · Backlog revision: 2.2.1
Specification: sections 8, 11.1, 17.1, 17.2.
Source:
AES_PHASES_2_6_PLAN.md, issue heading at line 6559.Plan SHA-256:
8acdaeb52d6a94fcad7de64d64521cd465f608344d63560b45f9202f5af71212Protocol snapshot: Download the complete governing plan.
Goal
deliver all historical experiments and close the phase.
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.milestone 5 closes with complete controls and supported, opposite
or inconclusive conditional conclusions.
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/P4-24/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.