{"ok":true,"query":"attestation","count":8,"method":"BM25 over the published corpus, title/summary weighted. Deterministic — the same query always returns the same ranking.","results":[{"title":"Attestation & audit","kind":"Method layer","url":"/#the-work","summary":"Months later, reconstruct what happened and why it was permitted.","score":3.6507,"matched":["attestation"]},{"title":"Chat logs are not traceability","kind":"Primitive","url":"/writing/the-attestation-problem","summary":"The reviewer shows up months later with four simple questions — what was done, who authorized it, what rule was checked, what did the system see — and the chat transcript answers none of them, for reasons no logging upgrade fixes. The four records that do answer them, what they honestly cost, and why they nearly write themselves once the rest of the stack exists.","score":3.5881,"matched":["attestation"]},{"title":"Design and build","kind":"Engagement","url":"/engagements/design-and-build","summary":"The governance layer itself — entitlement, policy-enforcement and attestation architecture — taken to production.","score":3.4372,"matched":["attestation"]},{"title":"Agent governance readiness benchmark","kind":"Research","url":"/research/agent-governance-benchmark","summary":"What organizations actually score across entitlements, enforcement, attestation and model risk.","score":3.4324,"matched":["attestation"]},{"title":"Your access recertification covers people. Most of your principals are not people.","kind":"Teardown","url":"/writing/recertification-covers-people","summary":"Quarterly access recertification is one of the most mature controls a bank runs: a closed population, a named approver, a signed decision, retained evidence. It is scoped to employees. Machine principals are handled by a separate process with a different cadence, a different owner and no attestation requirement — and agent deployments grow that second population while every control investment continues to land in the first. This teardown argues the gap is structural rather than negligent, because the object in the second population has no agreed definition anywhere, and it stops deliberately short of the design.","score":3.3889,"matched":["attestation"]},{"title":"Twenty-one things I refused to build","kind":"Field report","url":"/writing/twenty-one-things-i-refused-to-build","summary":"A portfolio review of fifty-four planned components ended with twenty-one of them killed — not deferred, not descoped, killed — because each one re-implemented open-source infrastructure that is more mature, more widely deployed and more adversarially tested than my version could ever have become. This is the report on how that decision was made, what each kill cost, what it bought, and the one place where the discipline is genuinely dangerous. The argument is not that building less is virtuous. It is that in this particular layer, the defensible novelty is unification, and every component that duplicates a consumed primitive actively weakens the claim.","score":3.193,"matched":["attestation"]},{"title":"Your first AI incident","kind":"Position","url":"/writing/your-first-ai-incident","summary":"Every agent program will have one. Whether it becomes a footnote or a filing is decided before it happens — by five documents and one rehearsal almost nobody schedules. The full version: what each artifact does in the first hour, why the reporting clocks start before you understand anything, and what the tabletop actually tests.","score":3.1214,"matched":["attestation"]},{"title":"What your receipt is entitled to claim","kind":"Field report","url":"/writing/what-your-receipt-is-entitled-to-claim","summary":"The sharpest review finding on the system I am building was that a trusted core which agents call advisorily is exactly as bypassable as the policy engine it replaced. Non-bypassability is not a property of my code. It is a property of a deployment topology I do not own. There were two honest responses available: assert the guarantee anyway and hope nobody checks, or state the condition, record which mode each deployment actually achieved, and refuse to let any artifact claim more than it earned. This is the report on taking the second — what it costs, what it forecloses commercially, and why the resulting contract is the part of this work I would defend hardest in front of a board.","score":2.9808,"matched":["attestation"]}]}