claim
u.agora.claim.2026-10-27.observed.grant-floor.scoped-only-unreachable.verdict-87559deff878
what it asserts
| kind | |
|---|
| subject | |
|---|
| assertion | |
|---|
| claimant | |
|---|
| minted | 2026-10-27T06:32:26Z |
|---|
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 | f0128193cce3 |
|---|
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.grant-floor.scoped-only-unreachable
verdict=stale
server_rev=f0128193cce3
note=triage 10-27 gregor: mixed - the 403-after-parent-revoke witness is the RUN path lineage law; the API floor has no lineage walk (a lineage-dead child still covers its prefix on the floor), so the floor/run lineage asymmetry is real and tracked, but the claim as stated is stale for the floor
minted_at=2026-10-27T06:32:26Z