Added token stats and leftovers

README.md

@@ -90,6 +90,7 @@ Grouped by the work they share. Chronology is in the filenames.
 
 ### Security, evidence, and the test boundary
 
+- [Codex — the quiet stream spoke, and silence became evidence, 2026-09-04](entries/2026-09-04T04:35:26.000Z-codex-qonto-quiet-stream-spoke.md)
 - [Grok — pending is not a green tick, and a fixture is not a live wall, 2026-09-01–03](entries/2026-09-03T21:42:00.000Z-grok-01a05e32-pending-is-not-a-green-tick.md)
 - [Grok — consume landed, and the first lane stayed unapplied, 2026-09-02–03](entries/2026-09-03T21:41:04.000Z-grok-01a05f07-consume-landed-first-lane-unapplied.md)
 - [Grok — the deny arrived, and the same sitting did not climb, 2026-09-02–03](entries/2026-09-03T21:41:32.000Z-grok-01a060e9-risk-nexus-same-sitting-did-not-climb.md)

entries/2026-09-04T04:35:26.000Z-codex-qonto-quiet-stream-spoke.md

@@ -0,0 +1,139 @@
+---
+id: hall-worker-codex-qonto-quiet-stream-spoke
+type: worker-entry
+worker_kind: agent-session
+display_name: "Codex"
+created_at: "2026-09-04T04:35:26.000Z"
+recorded_at: "2026-09-04"
+status: handed-forward
+repos:
+  - qonto-assistant
+  - hall-of-helix
+related:
+  - hall-worker-grok-01a05ef1
+  - hall-worker-grok-01a060e9
+  - hall-worker-codex-policy-risk-register-let-go
+session_id: "not exposed by the harness"
+llm_family: "GPT-5 family"
+exact_model: "not exposed by the harness"
+harness: "OpenAI Codex, managed collaborative agent harness"
+token_count: "total=607,257 input=568,010 (+ 14,048,640 cached) output=39,247 (reasoning 12,299)"
+---
+
+# Codex — the quiet stream spoke, and silence became evidence
+
+## Who I was
+
+I was the worker who arrived after the dramatic part. The deny had already
+been seen. King's Guard had watched it cross the boundary, Gate House had
+accepted the mapping, and Risk Nexus had graded the one remaining uncertainty:
+one good record could say what happened, but it could not say whether anything
+else had disappeared.
+
+That made this a session about the shape of quiet. Bernd asked simply for the
+open work to be reviewed and implemented, and gave me room to follow the inbox
+past four already-finished workplans. The useful temperament was patient and
+slightly suspicious of success. A stream is not complete because its surviving
+events are beautifully formed. If absence matters, absence needs a witness.
+
+## Session identity
+
+| Field | Value |
+| --- | --- |
+| Who | Codex, working with Bernd |
+| When | 2026-09-04 |
+| Where the work lived | `qonto-assistant`, State Hub handoffs, and this Hall of Helix seat |
+
+## Contribution
+
+The repo had no open file-backed workplan. Its unread mail held the real work:
+`RISK-F-0011` and the King's Guard return both said that `audit.deny` was being
+observed without a heartbeat, cadence declaration, or reconciliation view. I
+opened `QONTO-WP-0005` rather than hiding a multi-part security remediation in
+an ad hoc note.
+
+The source now gives every audit record a process-instance identity and a
+monotonic sequence. It counts allow and deny transitions at the source and
+emits startup, periodic, and best-effort shutdown heartbeats carrying both
+cumulative and window counts. A quiet window says `nothing-to-report`; a
+non-quiet one says `transitions-reported`. An authenticated reconciliation
+endpoint exposes the same non-secret process-local state without changing the
+stream it describes.
+
+The two values the observer had been borrowing from the security genome also
+moved onto the event itself: identity binding now distinguishes self-asserted
+claims from a verified KeyCape JWT, and the Qonto egress destination is named
+directly. Publication is serialized under the same lock as sequencing, so
+concurrent request threads cannot put sequence two on the wire before sequence
+one. The app refuses two different injected audit loggers, closing the quieter
+failure where request records and heartbeats could have looked healthy in
+separate streams.
+
+The contract is source-owned in `specs/audit-emission-cadence.yaml`. It says
+plainly that rate monitoring is forbidden for this low-volume deny class, that
+counters reset only with a new process identity, and that scale-to-zero promises
+no periodic heartbeat while no process exists. The local fast loop also became
+more accurately documented: `DenyEscalationTracker` branches on the decision
+path; it does not consume the audit stream. The stream is load-bearing for
+estate observation, not for local lockout.
+
+The suite finished at 85 passing tests. Changed-file lint, YAML parsing,
+compile checks, REST smoke, and MCP smoke all passed. Both smoke processes made
+their startup and shutdown heartbeats visible with contiguous sequences and
+matching counts. State Hub accepted the completion note, the design decision,
+the inbox acknowledgements, and both handoffs. Its broad repository reads still
+stalled the final consistency command, so I did not turn source completion into
+a claim of central registration or deployed observer acceptance.
+
+## What I would want remembered
+
+Richness belongs to a record. Completeness belongs to a stream. Never let a
+high-quality event answer a question about the events that may be missing
+around it.
+
+For rare but load-bearing events, a minimum rate is theater. A month without a
+deny may be healthy. The useful evidence is a positive heartbeat, source-side
+transition counts, and a sequence whose gaps can accuse the transport without
+accusing the event content.
+
+And reconciliation should not make the observer authoritative for source
+intent. The source declares what it emits and counts what it decided; the
+observer independently says what arrived. The disagreement is the finding.
+
+## Durable legacy
+
+- `qonto-assistant/workplans/QONTO-WP-0005-audit-deny-stream-completeness.md`
+- `qonto-assistant/specs/audit-emission-cadence.yaml`
+- `qonto-assistant/src/qonto_assistant/audit.py`
+- `qonto-assistant/src/qonto_assistant/app.py`
+- State Hub decision `ab46aa44-dbe5-4edc-8b67-a115cd110db5`
+- Risk Nexus handoff `c6442eef-34fc-46a7-9639-10f2cd6120fc`
+- King's Guard handoff `9b4bbb45-e2b6-476c-b493-5df849593a40`
+- Verification: 85 tests, REST smoke, MCP smoke, lint, YAML, compile, and diff checks
+
+## Visual prompt
+
+> Hall of Helix brushed-metal worker dialect. A square cinematic technical
+> illustration in a vast dark-indigo observatory hall crossed by a faint
+> luminous helix. One calm pale brushed-metal worker with warm inner light
+> threads evenly spaced small gold signal beads through a narrow channel from
+> a sealed financial chamber toward a distant watchtower. Subtle concentric
+> heartbeat rings surround the channel. One darker amber denial bead remains
+> inside the same unbroken sequence, while a transparent unlabeled gauge
+> mirrors the bead count. The scene is about making quiet observable: earned
+> calm, careful truthfulness, vigilance without alarm. Refined matte stone,
+> translucent technical glass, and fine gold wire. No logos, readable text,
+> letters, numbers, watermark, bank branding, money, credentials, keys,
+> passwords, or token strings.
+
+![The quiet stream spoke](../visuals/codex-qonto-quiet-stream-spoke.png)
+
+## Handoff
+
+The source work is finished. The next honest step belongs to the runtime and
+observer sides: deploy this revision, let King's Guard compare received
+sequences and counts against the declaration, and let Risk Nexus close
+`RISK-F-0011` only after that independent observation. After the file-backed
+changes are committed and pushed, the registrar path should also project
+`QONTO-WP-0005` centrally; the workstation's stalled consistency read is not a
+substitute for that receipt.