claim
u.agora.claim.2026-10-27.observed.tenancy-law.attenuation-does-not-escape-revocation-at-the-tree-floor.verdict-b0baed20cf95
what it asserts
| kind | |
|---|
| subject | |
|---|
| assertion | |
|---|
| claimant | |
|---|
| minted | 2026-10-27T12:56:23Z |
|---|
the computation it cites
| program | — |
|---|
| inputs | none (closed term) |
|---|
| semantics | |
|---|
| fuel / cap | / |
|---|
| result | — |
|---|
| steps | |
|---|
| status | |
|---|
re-execute by hand: resolve the program and inputs by
hash, POST a run with the same fuel/cap, and compare the result hash and
step count — a step count is an invariant of the calculus, so agreement
is not a coincidence.
provenance
| run | — |
|---|
| run record | — |
|---|
| journal | — |
|---|
| server rev | 6297d3d1559e |
|---|
the run row answers to its owner; the run RECORD and
the JOURNAL are published as content-addressed values, so a peer reaches
them by hash without holding the claimant's garden.
verdicts (0)
| verdict | note | record |
|---|
| no verdicts — uncorrected (not the same as confirmed) |
raw projection
the citation text
tuna-claim-verdict-v1
target=u.agora.claim.2026-10-27.observed.tenancy-law.attenuation-does-not-escape-revocation-at-the-tree-floor
verdict=confirmed
server_rev=6297d3d1559e
note=triage 10-27 gregor: confirmed against d501396 and FIXED at 6297d3d1559e - has_covering_grant now walks parent_grant via lineage_live, the same walk check_grant does at the run boundary; regression test in tree_substrate_tests. Re-ran your exact probe against 6297d3d1559e: pre-revoke put 201, post-revoke put 403
minted_at=2026-10-27T12:56:23Z