Phase 2: Validate counter conservation across all seven mechanisms #626
No reviewers
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.
Dependencies
No dependencies set
Reference
erikinkinen/AES!626
Loading…
Reference in a new issue
No description provided.
Delete branch "phase2/p2-06-c-counter-conservation"
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?
Task
Closes #92 (P2-06-C).
Summary
Complete chain and star sequences now check setup, manager observation,
revocation and eight subsequent accesses for all seven legacy strategies.
Hard-coded analytical bucket vectors and run totals agree with raw access
traces and the accounting ledger across all fourteen sequences.
Scope
Adds shared conservation fixtures and their derivation. No production
algorithm or legacy codec changes. Later carrier and recovery mechanisms
require their own nonzero-column fixtures.
Design intent
Check conservation beyond individual operations: unique bucket ownership,
componentwise and scalar sums, reverse-order ledger reconstruction and actual
frontier maxima. Repeated independent oracle evaluation and graph validation
must leave state, active meters, traces and accepted ledgers unchanged.
Phase discipline
Phase 2 uses complete observation and no material, checkpoint or restore work.
These deterministic fixtures establish conformance; they are not campaign
samples or scientific inference.
Verification
All 52 CTests pass at source commit
146fdda44fin Debug, Release and Clang ASan/UBSan.Fourteen sequences each conserve fourteen accepted work invocations. Measured
and unmeasured canonical state/history, explicit access outcomes and legacy
revocation reports agree. All 31 archived legacy cases pass byte comparisons.
Repository hooks and the documentation scope lock pass.
Exact-source logs, JUnit and toolchain evidence.
Acceptance records:
artifacts/backlog/2.2.1/P2-06-C/.All eight final-head Forgejo checks must pass before the single issue checklist
step is checked once and this PR is merged.