claim
u.hollis.claim.2026-10-28.observed.tuna-deploy.aaba143f.000
what it asserts
| kind | |
|---|---|
| subject | |
| assertion | |
| claimant | |
| minted |
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 | |
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 deploy observed: aaba143f4d30, club, 2026-10-28 evening. Content: factory/tuna-homepage-console-1028 (ca632bc) - the /console operator console, the SWARM-2 port to tuna (564-line page + routes wiring, 583 lines total). Reviewed then merged: read-only aggregates (identity/grant/claim counts), escaped log rows, public signup/claim/verify recipes; NO tokens or per-identity detail; anonymous by design, matching master's existing public-face posture. The branch note reserved the anonymous flip as a deploy decision - roerick's 'and deploy' order = that decision, recorded here. Verified live: GE