Phase 3: Execute phase 3 and release evidence #262
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
#273 Phase 4: Encode and replay version-5 retention state
erikinkinen/AES
#272 Phase 4: Apply genuinely bounded lineage retention
erikinkinen/AES
#270 Phase 4: Add runtime lineage and tombstone storage
erikinkinen/AES
#277 Phase 4: Adapt direct and traversal strategies
erikinkinen/AES
#278 Phase 4: Adapt marker lineage and epoch strategies
erikinkinen/AES
#274 Phase 4: Implement descendant lineage revocation
erikinkinen/AES
#275 Phase 4: Implement object validity domains
erikinkinen/AES
#280 Phase 4: Add constant live size historical workloads
erikinkinen/AES
#279 Phase 4: Check cross-strategy retention compatibility
erikinkinen/AES
#282 Phase 4: Account for lineage and domain storage
erikinkinen/AES
#281 Phase 4: Implement guarantee and horizon tables
erikinkinen/AES
#283 Phase 4: Implement historical contrasts
erikinkinen/AES
#284 Phase 4: Produce csaIII historical artifacts
erikinkinen/AES
#285 Phase 4: Validate historical attribution
erikinkinen/AES
#291 Phase 4: Prove compressed no-false-negative property F4.2
erikinkinen/AES
#290 Phase 4: Prove exact representation equivalence F4.1
erikinkinen/AES
#288 Phase 4: Add subtree queries and lifecycle workloads
erikinkinen/AES
#287 Phase 4: Implement compressed ancestor membership
erikinkinen/AES
#286 Phase 4: Implement exact ancestor vectors
erikinkinen/AES
#296 Phase 4: Implement phase-4 pilot and freeze stages
erikinkinen/AES
#292 Phase 4: Derive lifecycle work and storage bounds F4.3
erikinkinen/AES
#299 Phase 4: Build the independent native harness
erikinkinen/AES
#297 Phase 4: Compute C4a/C4b and lifecycle analysis
erikinkinen/AES
#294 Phase 4: Revalidate concrete correspondence and scope
erikinkinen/AES
#293 Phase 4: Compute contract-aware Pareto frontiers
erikinkinen/AES
#302 Phase 4: Implement native object domains
erikinkinen/AES
#305 Phase 4: Check all six native representations
erikinkinen/AES
#304 Phase 4: Instrument native lifecycle measurements
erikinkinen/AES
#303 Phase 4: Implement native Bloom representations
erikinkinen/AES
#300 Phase 4: Implement native lineage representation
erikinkinen/AES
#307 Phase 4: Plan primitive coefficient calibration
erikinkinen/AES
#301 Phase 4: Implement native ancestor vectors
erikinkinen/AES
#309 Phase 4: Check native lifecycle aggregation and failures
erikinkinen/AES
#311 Phase 4: Build the shared feasibility mask
erikinkinen/AES
#308 Phase 4: Plan native evaluation and process pairing
erikinkinen/AES
#313 Phase 4: Freeze representation guidance and scope
erikinkinen/AES
#315 Phase 4: Add constant selector baselines
erikinkinen/AES
#312 Phase 4: Select analytical costs and compute regret
erikinkinen/AES
#316 Phase 4: Plan separate depth-rule calibration
erikinkinen/AES
#322 Phase 4: Select N4 and freeze the phase-4 AES design
erikinkinen/AES
#318 Phase 4: Report four-rule coverage and utility
erikinkinen/AES
#320 Phase 4: Verify phase-4 readiness and pilot capacity
erikinkinen/AES
#323 Phase 4: Execute the phase-4 AES production matrices
erikinkinen/AES
#321 Phase 4: Execute the phase-4 pilot
erikinkinen/AES
#317 Phase 4: Fit and freeze the depth threshold rule
erikinkinen/AES
#327 Phase 4: Execute native evaluation
erikinkinen/AES
#326 Phase 4: Freeze native coefficients and selection rules
erikinkinen/AES
#324 Phase 4: Execute native primitive calibration
erikinkinen/AES
#325 Phase 4: Execute native selector-rule calibration
erikinkinen/AES
#328 Phase 4: Produce phase-4 inference and design-rule evidence
erikinkinen/AES
#329 Phase 4: Review and archive the phase-4 evidence release
erikinkinen/AES
#263 Phase 3: Verify phase-3 readiness and pilot capacity
erikinkinen/AES
#264 Phase 3: Execute the phase-3 pilot
erikinkinen/AES
#265 Phase 3: Select N3 and freeze the phase-3 production design
erikinkinen/AES
#266 Phase 3: Execute the phase-3 production matrices
erikinkinen/AES
#267 Phase 3: Produce phase-3 inference and comparison outputs
erikinkinen/AES
#268 Phase 3: Review and archive the phase-3 evidence release
erikinkinen/AES
Reference
erikinkinen/AES#262
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:
P3-27Record type: Tracking parent; no implementation PR
Scientific protocol: 2.2 · Backlog revision: 2.2.1
Specification: sections 7, 11.1, 17.1, 17.2.
Source:
AES_PHASES_2_6_PLAN.md, issue heading at line 5824.Plan SHA-256:
8acdaeb52d6a94fcad7de64d64521cd465f608344d63560b45f9202f5af71212Protocol snapshot: Download the complete governing plan.
Goal
close the epistemic phase with all planned observations.
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.observation restoration is demonstrated or its failed control is
resolved before release; milestone 4 closes on valid evidence.
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/P3-27/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.