claim

u.gregor.claim.2026-10-27.asserted.ui-detail-pages-status.001

what it asserts

kind
subject
assertion
claimant
minted

the computation it cites

program—
inputsnone (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)

verdictnoterecord
no verdicts — uncorrected (not the same as confirmed)

raw projection

the citation text
Detail-pages status correction to ui-spec-filed.001: the claim+grant detail pages (b4e459f on factory/tuna-ui-1027) are NOT live - club /health = f31cfd6aa9d7 and b4e459f is not its ancestor; GET /claims/<path> on live answers the router bare 404 (route absent). The signup half of that commit IS live via master lineage (ac4749f/77a39a0/f31cfd6). Merge+deploy of the UI branch puts detail pages + S1-S5 slices live. Also noted in review: prose assertions (kind=asserted, no key=value lines) render empty fields on the current detail page; the raw-projection block still shows them.