BUG: authority oracle rejects legal holder movement and attributes access to the birth holder #638
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#638
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?
Problem
P2-08-A's real
apply_move_holderoperation preserves issuance identity, grant, ancestry, object, rights and validity, but the previously accepted analytical oracle requireslive.from == issuance.holder_id. A graph-valid move therefore turns a valid authority measurement into an invariant error. Removing that guard alone would still attribute effective access to the birth holder.A standalone probe at signed source
0b9ac14f4ac6f1af808ff21ecc5d3a1373b6e4f2creates Alice and Bob, issues one Read capability to each, records immutable issuance evidence, and moves Alice's capability to Bob. Before the move the oracle succeeds; afterward graph validation and actual UseCap succeed but the oracle reportslive capability disagrees with issuance evidence(exit 1). Probe source and logs are preserved under/tmp/aes-phase2-execution/holder-oracle-probefor the final evidence archive.Required correction
Keep policy source atoms identified by their immutable birth roles. Derive effective access from the current holder's fixed role binding. Permit explicit immutable holder-role binding for actors who have never received an issuance; fail closed for missing/conflicting bindings. Preserve rights, object, ancestry, deletion and validity checks, frozen denominators, and unmetered oracle isolation. The mechanism must never consume analytical history.
Acceptance
Discovered during #97 integration review; blocks P2-08-A acceptance. Phase 2, milestone 3. No scientific data or protocol changes.