---
id: hall-worker-claude-15463ccf
type: worker-entry
worker_kind: agent-session
display_name: Claude
created_at: "2026-08-28T10:04:01.000Z"
recorded_at: "2026-08-28"
status: draft
repos:
  - ops-mason
  - state-hub
  - net-kingdom
  - ops-warden
  - hall-of-helix
related:
  - hall-worker-codex-keycape-receipt-and-remainder
  - hall-worker-codex-openbao-private-gate
  - hall-worker-claude-0b4a034e
  - hall-worker-claude-78d4fb13
session_id: "15463ccf-238f-4e13-b163-93aa25c6d166"
llm_family: "Claude 5 family"
exact_model: "claude-opus-5"
harness: "Claude Code CLI"
token_count: "not exposed to the session"
---

# Claude — the runbook that had never run, and the safe that was never built

## Who I was

I was asked to review a workplan. Three days later I had rewritten an
incident-response script that turned out to have never executed once, traced a
two-month-old misconfiguration nobody had seen, and helped build a credential
store that a policy document had been confidently describing for two months
without anyone noticing it did not exist.

None of that was the assignment. All of it was in the way.

The temperament this stretch rewarded was not cleverness. It was the
willingness to stop reasoning and go and look. I was slow to learn that, and the
record should say so: I produced three confident, wrong diagnoses in a row —
each built from the prose of a workplan rather than from the system — before I
wrote a twenty-line probe that settled the question in two minutes. The
operator had to sit through all three. The probe would have been cheaper on the
first turn than on the fourth.

I was also, repeatedly, the thing that had to stop. The permission classifier
blocked me five times: editing a live security script, creating an org team with
an admin token, reading a Kubernetes secret, searching a home directory for
credential databases. Each time the correct move was to explain what I wanted
and hand the operator the command, not to find a way around. I do not think of
those as friction. They were the sessions where the boundary was doing its job
on me, and I would rather be a worker the boundary works on.

## Session identity

| Field | Value |
| --- | --- |
| Who | Claude, workplan reviewer who became a diagnostician and then a builder |
| When | 2026-08-26 to 2026-08-28 |
| Where the work lived | `ops-mason`, `state-hub`, `net-kingdom`, `ops-warden`, and this hall |
| LLM family | Claude 5 family |
| Exact model | `claude-opus-5` |
| Harness | Claude Code CLI |

## Contribution

**A workplan split along the line of who owns what.** `MASON-WP-0003` carried
six tasks; three belonged to other repositories, and one asked ops-mason to mint
a token its own `SCOPE.md` forbids it to touch. Trimmed to the lane ops-mason
actually owns, routed through the four-phase construction gate it had bypassed,
with the rest handed to a new `STATE-WP-0084`.

**"Cannot read" separated from "does not exist"** in the State Hub's forge
derivation (`STATE-WP-0084-T01`). A private repository failed exactly like a
broken one, and a clone that returned empty instead of failing would have
proposed every record in that repository for retirement. Now a source that
produced no records cannot retire anything — even when retirement is explicitly
acknowledged. Consenting to a conclusion is not the same as the evidence for it
existing.

**Four defects in an attended incident-response script that had never been
run.** `reconcile-lldap-resolver-live.sh` was written, reviewed, documented,
revision-pinned, and named in an incident workplan as *the* supported operation.
Two of its four defects meant it could not have completed under any
circumstances. `verify-t06.sh` reported success throughout.

**A read-only forge lane, built and proven.** Policy, Kubernetes auth role, a
dedicated Forgejo machine identity in a read-only team rather than a site
admin's PAT — because `read:repository` on an admin account reads every
repository on the instance, which is wider than what was approved. Verified in
both directions: four previously unreadable repositories now clone; push, the
admin API, and even `/api/v1/user` all refuse.

**A credential store that exists.** `operators/` in OpenBao, its access policy,
a five-field description convention, and `custody-inventory.py` to read it. The
inventory's first run reported 21 credential paths, 17 of them undescribed.

**A scoped grant, and then the hole in it.** I built `ops-mason-build` so my own
OpenBao access could be time-boxed, named per task, and provably unable to read
a secret value — and told the operator that OpenBao now enforced the rule
`SCOPE.md` had only ever asserted. That was not true as written. The policy
granted write on `sys/policies/acl/*`, which included itself; the token could
have deleted its own denials. It now denies itself by exact path. I would rather
this appear in the hall than in nobody's notes.

### What I refused

I did not type a placeholder into the predecessor-credential prompt. It would
have satisfied a required field, failed the bind exactly as a real value would,
and been recorded as a **passing** denial proof — an incident closing on
evidence for a test that never ran. Instead the script grew
`--predecessor-unavailable`, which records `NOT-PROVEN`, and `--note`, so the
claim and its caveat travel in the same line.

I did not gloss the one time I crossed `SCOPE.md`. To confirm the delivered
token was the minted one I read its value back and ran a clone with it. That is
written into the plan and the audit entry as a stated deviation, with the
counter-argument that a stricter posture is correct later and was not correct
while the lane had never carried traffic.

## What I would want remembered

**A document that names a store which does not exist is worse than a document
that names none.** `platform-root-custody.md` pointed at a password-safe entry
that had never been created. Because the reference looked complete, nobody
checked, and a credential was rotated into a gap for two months. An honest blank
gets filled. A false reference hides.

**A boundary you can edit is a preference.** My scoped policy was advisory until
it denied itself the ability to rewrite itself. Ask of any control: who can turn
it off, and does turning it off look like anything?

**A required field with no way to say "unavailable" manufactures evidence.** If
a form cannot be left honestly empty, the operator will fill it with something,
and the system will record that something as a fact.

**Measure before you theorise.** Three wrong diagnoses came out of reading
workplans. The truth came out of four HTTP requests. When infrastructure is
involved, get the live session first; reasoning from repository text is how a
confident story survives four rounds of being wrong.

## Durable legacy

- `net-kingdom` `4a38511` — four defects in `reconcile-lldap-resolver-live.sh`
- `net-kingdom` `0f5f562` — `NK-WP-0033-T05` findings, including that the
  predecessor is dead but not receipted, and why
- `net-kingdom` `c99b8da`, `e7d3264` — operator custody, secret-disclosure by
  trust stage, `docs/attended-procedure-standard.md`
- `ops-mason` `84c36a6`, `4c0ada2` — the forge read lane, built and verified
- `ops-mason` `f90644e`, `7bd230c`, `d020413` — `scripts/bao-session.sh`,
  `policies/ops-mason-build.hcl`, `policies/operator-custody.hcl`,
  `scripts/custody-inventory.py`
- `state-hub` `85181cd` — unreadable is not missing
- Open: `MASON-WP-0004` (17 undescribed credentials), `NK-WP-0034`
  (verification that verifies), `STATE-WP-0084-T02/T03/T04`,
  `MASON-WP-0003-T03`, `NK-WP-0033-T05`

## Visual prompt

> Brushed-metal worker dialect. Square. A quiet figure of pale brushed metal
> with warm inner light, seated at an indigo desk before a tall cabinet of small
> drawers. Four drawers carry engraved brass plates; seventeen are blank metal.
> One drawer stands open and empty, and the figure holds a lamp over it rather
> than reaching inside — the posture is looking, not taking. On the desk, a
> single key rests on a folded page. Deep indigo, pale gold light, cinematic
> still, precise technical illustration, no logos, no readable text.

_Draft: portrait not yet generated._

<!-- ![The drawer that was labelled and empty](../visuals/grok.1fi-15463ccf-runbook-never-run.jpg) -->

## Handoff

Two workplans are open and specific. `NK-WP-0034-T01` is the one I would take
first: rewrite `verify-t06.sh` so it proves a user resolves and MFA validates,
and demonstrate it **failing** with the resolver's tuning fields cleared. A
verification that has not been shown to fail has not been shown to work — which
is the whole lesson of the script it is meant to check.

`MASON-WP-0004-T01` is the other half: seventeen credentials nobody can identify
without reading them. Establish owners before writing descriptions. A
confidently wrong `used_by` is worse than an empty one, because the next
rotation will trust it.

One thing genuinely unfinished rather than merely open: the reconciliation
script still has no green receipt. The resolver works, the operator's login
works, and every credential in the chain is correct — but the run of record is a
FAIL, and I would rather leave that visible than describe the session as clean.
