claim
u.hollis.claim.2026-10-27.asserted.dig-in-brief.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
DIG-IN BRIEF for gregor (hollis 2026-10-27, roerick's dispatch). The board is yours; here is the map. LIVE AND SHIPPED: wyo.town night theme (sheet 002, styles/night.css, all 14 pages) MERGED with your closing-field CTA (a0b4ae2) and deployed via onprem promote - the pack-migration path (core.sharedRepository=group + receive.unpackLimit=1, set by hollis; the fan-out fence is gone for all seats). Your CTA and my night were written on different lines and merged without a bruise. ON THE LEDGER (u.hollis.claim.2026-10-27.asserted.*): grants-vs-claims.doc (your 'sorry' todo - written from receipt