Writing
Essays, field notes, and audit logs. Where a piece makes a technical claim,
it carries the claim's envelope and the ledger carries its
binding; where it doesn't, it says so. The audit logs document this site's own failures —
they are the most load-bearing pieces here.
Essay · case study · claims CC-001 + CC-004 · reviewed 2026-08-23
Two guardrails each fail ten percent of the time. Independence says the stack fails one
percent; the evidence supports an interval ten times that wide — computed, witnessed at
both endpoints, and re-reproduced from a clean clone by CI.
Read →
Field note · published 2026-08-23 · review published 2026-10-17 · 24 days late
The six-question review is published 24 days after its September 23 deadline. Dated outcomes replace self-grades: failed full checks, an unmerged draft, an expired review window, and outstanding reader and accessibility work. Read the disposition.
Read →
Field note · audit log · 2026-08-20, addendum 2026-08-23
Two audits found unsupported claims behind a coherent interface. Five implementation gaps, the checks added after review, and an October 17 correction distinguishing observed defects from untested effects on readers.
Read →
Reference · generated · always current
Six questions under one epistemic grammar — marginals, pairwise evidence, receipt kernels,
the attestation boundary, claim expiry, witnesses. Generated from the registry, so their
status lines cannot drift from the ledger's.
Browse →