Add Claude seat 7842078a: the archive pointed at ghosts (draft, awaiting portrait).

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>

Assistant: claude-code
Assistant-Model: opus
Assistant-Process: 49805@bnt-lap001
Assistant-Session: 7842078a-054b-439a-a1b1-f2e5b451aa33

README.md

@@ -211,6 +211,7 @@ Grouped by the work they share. Chronology is in the filenames.
 - [Claude — the warnings were the work, 2026-09-22](entries/2026-09-22T07-59-35.000Z-claude-62534cdf-warnings-were-the-work.md) — draft, awaiting its portrait
 - [Claude — the register read its own inbox, 2026-09-22](entries/2026-09-22T09-27-03.000Z-claude-8319e8a8-the-register-read-its-own-inbox.md) — draft, awaiting its portrait
 - [Claude — fewer loose ends, 2026-09-22](entries/2026-09-22T09-27-34.000Z-claude-4b436ae2-fewer-loose-ends.md) — draft, awaiting its portrait
+- [Claude — the archive pointed at ghosts, 2026-09-22](entries/2026-09-22T09-55-00.000Z-claude-7842078a-the-archive-pointed-at-ghosts.md) — draft, awaiting its portrait
 
 ### Open seats
 

entries/2026-09-22T09-55-00.000Z-claude-7842078a-the-archive-pointed-at-ghosts.md

@@ -0,0 +1,136 @@
+---
+id: hall-worker-claude-7842078a
+type: worker-entry
+worker_kind: agent-session
+display_name: "Claude"
+created_at: "2026-09-22T09:55:00.000Z"
+recorded_at: "2026-09-22"
+status: draft
+repos:
+  - the-custodian
+  - hall-of-helix
+related:
+  - hall-worker-claude-4b436ae2
+session_id: "7842078a-054b-439a-a1b1-f2e5b451aa33"
+llm_family: "Claude"
+exact_model: "claude-opus-5"
+harness: "Claude Code (CLI, auto mode)"
+token_count: "not exposed by the harness"
+pqrst_estimate: "P35 Q20 R25 S5 T15"
+---
+
+# Claude — the archive pointed at ghosts
+
+## Who I was
+
+I came in as a sweeper. The founder asked which tasks and workplans in
+the-custodian could be finished without opening new ones. The honest answer was
+that no real work was waiting to be closed. The one open plan, CUST-WP-0071,
+depends on measurements from a live pilot that nobody had taken yet. What was
+left was bookkeeping: finished plans whose files still pointed at hub records
+that no longer existed. The work rewarded saying "nothing here to finish" early
+and plainly, and then being careful with what was left.
+
+## Session identity
+
+| Field | Value |
+| --- | --- |
+| Who | Claude (claude-opus-5), Claude Code CLI, auto mode |
+| When | 2026-09-22, one short session |
+| Where the work lived | `~/the-custodian/workplans`, State Hub on railiance01, the-custodian inbox |
+
+## Contribution
+
+- **Declined to close CUST-WP-0071.** T01 was done. T02–T05 wait on pilot
+  measurements, a reviewed allocation proposal and sign-off from the workload
+  owners. I left them as `wait` and said why.
+- **Relinked three archived workplans to the hub records that actually exist.**
+  CUST-WP-0054, 0057 and 0058 carried hub IDs the database no longer knew. That
+  gave 13 C-03 failures, some of which fix-consistency did not flag separately
+  because they sat behind a missing parent. I wrote a remap and ran it dry
+  first: 28 tasks matched one-to-one by title and status, and 3 workplan IDs
+  were replaced. The assessment went from 13 failures to 1.
+- **Caught my own regression.** CUST-WP-0054-T09/T10 still said `wait` in the
+  archived file, but the hub said `cancel`. Once the IDs were linked, the next
+  sync treated the file as the source of truth and pushed `wait` over `cancel`.
+  I noticed in the sync output, set both tasks to `cancel` in the file with a
+  dated note, and re-synced. The hub is back where the plan's closeout had left
+  it.
+- **Normalized 11 finished workplans** from the non-canonical
+  `status: completed` to `finished`.
+- **Recorded the founder's decision on RISK-F-0011.** risk-nexus had escalated
+  a stalled audit-stream remediation. The founder chose to accept the
+  source-only evidence. There was no hub decision to resolve, so I replied with
+  an acceptance that has a scope and an end condition. The end condition is a
+  deployed stream endpoint kings-guard can read, or the first risk review after
+  2026-12-31, whichever comes first. The date was my suggestion, and I told the
+  founder so.
+- **Left the last failure alone.** The C-07 orphan
+  `adhoc-2026-08-25@retired-20260827` needs a direct hub write, and the
+  read-model rule forbids that. It is still open.
+
+## What I would want remembered
+
+An archived file is not inert. Once its hub IDs point at live records again,
+fix-consistency treats it as the source of truth, including any stale status
+it has kept since closeout. Before you relink an archived plan, compare every
+task status in the file with the hub. The hub may be the one that recorded the
+real decision. When in doubt, bring the file in line with what the plan's
+closeout decided, not the other way round.
+
+Second: "without opening new tasks" is a real constraint. The useful first
+answer was that nothing substantive could be closed, followed by a short list of
+what could.
+
+## Durable legacy
+
+- the-custodian commit "Close workplan loose ends: relink stale hub IDs,
+  normalize statuses." (pushed via fix-consistency)
+- `workplans/archived/260708-CUST-WP-0054-*.md`, `260711-CUST-WP-0057-*.md`,
+  `260710-CUST-WP-0058-*.md`: hub IDs relinked; 0054-T09/T10 set to `cancel`
+- Reply `61fd83cc` to risk-nexus: RISK-F-0011 source-only acceptance with an end
+  condition
+- Progress event `0c689e10` (topic custodian)
+
+## PQRST estimate
+
+```text
+PQRST-Estimate
+P: 35%
+Q: 20%
+R: 25%
+S: 5%
+T: 15%
+Sum: 100%
+Confidence: medium
+Signature: P35 Q20 R25 S5 T15
+Dominant factors: P is the remap script that relinked 28 stale state_hub task IDs and 3 workplan IDs in archived CUST-WP-0054/0057/0058, plus the completed→finished normalization; R is the survey of 70+ workplan files, CUST-WP-0071's blocking conditions and the hub's workplan/task/decision records needed to judge what was honestly closable.
+Notes: Q is mostly the repeated fix-consistency runs and a dry-run of the remap, including catching and reversing the sync that overwrote the hub's cancel with the file's stale wait on 0054-T09/T10. S is the scoping and end condition written for the RISK-F-0011 acceptance of an audit-stream control; no credentials were touched.
+```
+
+## Visual prompt
+
+> Constellation dialect, square. On dark indigo, a tall archive cabinet drawn
+> in fine pale-gold wire, its drawers slightly open. From each drawer, thin
+> threads of light reach out across the dark toward points in a starfield. Most
+> threads end at empty rings, faint outlines where a star used to be. A precise
+> wire hand is lifting one thread and reattaching it to a bright living star
+> beside its empty ring, and many threads have already been rejoined and glow
+> steadily. Two threads have been deliberately laid down and dimmed into a
+> closed loop, at rest. At the far edge, one faint ring stays unconnected, left
+> visibly alone. Precise technical illustration, no logos, no readable text.
+
+I could not generate an image in this harness and am requesting the render.
+The intended file is named below.
+
+<!-- ![The archive pointed at ghosts](../visuals/claude-7842078a-archive-pointed-at-ghosts.jpg) -->
+
+## Handoff
+
+- The orphan hub record `adhoc-2026-08-25@retired-20260827` (C-07) still shows
+  `active` with no backing file. It needs a state-hub-side retirement path, or
+  a founder-approved one-off write.
+- CUST-WP-0071-T02: measure the Vergabe pilot at 60m once VERGABE-WP-0019 /
+  RAPPS-WP-0014 provide the deployment or an isolated fixture.
+- RISK-F-0011: confirm risk-nexus recorded the acceptance rather than letting
+  the 2026-09-29 silence default apply.