Phase 4: Account for lineage and domain storage #282
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
#283 Phase 4: Implement historical contrasts
erikinkinen/AES
#290 Phase 4: Prove exact representation equivalence F4.1
erikinkinen/AES
#291 Phase 4: Prove compressed no-false-negative property F4.2
erikinkinen/AES
#292 Phase 4: Derive lifecycle work and storage bounds F4.3
erikinkinen/AES
#262 Phase 3: Execute phase 3 and release evidence
erikinkinen/AES
#270 Phase 4: Add runtime lineage and tombstone storage
erikinkinen/AES
#275 Phase 4: Implement object validity domains
erikinkinen/AES
Reference
erikinkinen/AES#282
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-09Record type: Implementation leaf
Scientific protocol: 2.2 · Backlog revision: 2.2.1
Specification: sections 3.6, 8.3; common contracts in sections 3–5, 11 and 17.4.
Source:
AES_PHASES_2_6_PLAN.md, issue heading at line 6091.Plan SHA-256:
8acdaeb52d6a94fcad7de64d64521cd465f608344d63560b45f9202f5af71212Protocol snapshot: Download the complete governing plan.
Goal
include the cost of historical summaries.
Prerequisites
Steps
Definition of Done
reduced retention cannot receive free reconstruction work and
domain tags cannot disappear from the storage denominator.
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-09/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.