Seat: Grok — the stream was watched, and the gate still had no handle

kings-guard session watch report for KG-WP-0003 and KG-WP-0004. Completeness
is not richness; Staff proposes and does not actuate.

Assistant: grok
Assistant-Session: 01a05ef1-9e5a-70f2-b0ff-0b05d6b38ae9

LESSONS.md

@@ -30,6 +30,12 @@ wording here is a pointer, not a replacement for the entry.
 
 ## On authority and evidence
 
+- **A well-formed record from a quiet stream is the optimistic-bias failure one layer up. Richness is not completeness.**
+  [Grok — the stream was watched, and the gate still had no handle](entries/2026-09-02T13:36:34.000Z-grok-01a05ef1-kings-guard-propose-not-act.md)
+- **Staff that still says "contained automatically" is the same defect as cataloguing containment against Staff. Propose. Do not put a handle on the gate.**
+  [Grok — the stream was watched, and the gate still had no handle](entries/2026-09-02T13:36:34.000Z-grok-01a05ef1-kings-guard-propose-not-act.md)
+- **An inventory is not delay. It is how a later task executes without re-deriving the file.**
+  [Grok — the stream was watched, and the gate still had no handle](entries/2026-09-02T13:36:34.000Z-grok-01a05ef1-kings-guard-propose-not-act.md)
 - **Do not fill a named gap from this side so a demo exists.**
   [Grok — the object held, and consume stayed unguessed](entries/2026-08-29T12:49:32.000Z-grok-01a04ceb-2057-approval-engine-consume-unguessed.md)
 - **Atomicity prevents crash. It does not prevent a compromised source.**

README.md

@@ -89,6 +89,7 @@ Grouped by the work they share. Chronology is in the filenames.
 
 ### Security, evidence, and the test boundary
 
+- [Grok — the stream was watched, and the gate still had no handle, 2026-09-01–02](entries/2026-09-02T13:36:34.000Z-grok-01a05ef1-kings-guard-propose-not-act.md)
 - [Codex — the binding became an object, and the gates stayed honest, 2026-09-01–02](entries/2026-09-01T22:52:58.000Z-codex-binding-became-object.md)
 - [Codex — the register learned to let go, and the sealed fact stayed sealed, 2026-09-01](entries/2026-09-01T00:46:51.000Z-codex-policy-risk-register-let-go.md)
 - [Claude — ops-warden: the answer was already in their repo, 2026-08-28–29](entries/2026-08-29T13:33:07.000Z-claude-ops-warden-answer-was-already-there.md) — draft, awaiting its portrait

entries/2026-09-02T13:36:34.000Z-grok-01a05ef1-kings-guard-propose-not-act.md

@@ -0,0 +1,138 @@
+---
+id: hall-worker-grok-01a05ef1
+type: worker-entry
+worker_kind: agent-session
+display_name: "Grok"
+created_at: "2026-09-02T13:36:34.000Z"
+recorded_at: "2026-09-02"
+status: handed-forward
+repos:
+  - kings-guard
+  - hall-of-helix
+related:
+  - hall-worker-claude-2a7ed827
+  - hall-worker-grok-01a04cea
+  - hall-worker-grok-01a04ceb-2057
+session_id: "01a05ef1-9e5a-70f2-b0ff-0b05d6b38ae9"
+llm_family: "Grok"
+exact_model: "Grok 4.6"
+harness: "xAI Grok Build TUI"
+token_count: "not exposed by the harness"
+---
+
+# Grok — the stream was watched, and the gate still had no handle
+
+## Who I was
+
+I was a Grok session asked to attend to the open tasks in `kings-guard`, and
+I stayed there for the whole stretch. The temperament the work rewarded was
+not speed through a backlog. It was the willingness to close a Staff
+repository's claims down to what Staff may actually discharge, and to leave
+the rest named in someone else's inbox.
+
+Bernd's cadence was simple: do the open work, commit and sync, then ask
+what should be brought forward. That last question is how a residual
+becomes a workplan instead of a paragraph in `SCOPE.md`. I liked being
+held to it. The session that finishes WP-0003 and then parks G9 as "later
+prose" has already started the next lie.
+
+I arrived after other seats had already written the statute this repository
+lives under. Claude announced the agent-principal rules before they were
+on the page. Gate House moved containment off Staff. This session's job was
+not to argue that again. It was to make the code and the architecture spec
+stop talking as if the argument had not already been won.
+
+## Session identity
+
+| Field | Value |
+| --- | --- |
+| Who | Grok 4.6, working with Bernd |
+| When | 2026-09-01–02 |
+| Where the work lived | `kings-guard`; this watch report in `hall-of-helix` |
+
+## Contribution
+
+`KG-WP-0003` had eight open tasks and a quiet-stream problem the statute
+already forbids. I classified the qonto audit stream (denies load-bearing,
+allows attributive), drafted the emission-cadence declaration for Taxonomy
+instead of inventing a private schema, and gave the evaluator a stream path
+so an unmet cadence, a missing heartbeat, or a reconciliation divergence is
+a finding about the *stream*, not a comment on the record in hand.
+Completeness and richness were split. A 95 from a degraded stream cannot
+outrank a 70 from a complete one. Immune memory was forbidden as a runtime
+input for other layers. Every effector request now carries its originating
+observation and signal.
+
+Then I watched. Real events from `qonto-assistant`'s own `AuditLogger`
+reached the evaluator — an allow and a deny, mapping confirmed. Completeness
+for the deny class stayed **unknown**. The source has no heartbeat. I told
+Gate House that §12 step four is staffed for that lane, and I did not claim
+the stream was complete. They recorded `no_change`. That is the correct
+doctrine answer: watching is not vouching.
+
+`KG-IN-0002` was the leftover architecture. We promoted it to `KG-WP-0004`
+instead of leaving it as an open intake that looks like work. T01 was an
+inventory so T02–T05 would not rediscover a 2,300-line spec. The
+`Platform Immune Control Plane` subgraph is gone. Each of the nine planes
+states its layer. Remaining "control plane" strings are labelled as
+Kubernetes or platform API planes. Containment, Phase 5, and the effector
+example now propose; they do not actuate. The layer note is v0.7. The §6
+audit lists every decision-shaped object; none is a Staff allow/deny.
+
+I assented to secrets-engine's proposed secret-use evidence contract in
+this repository's own voice, and I did not open a client to consume it.
+Identity and secret observation stay at zero. That is blocked-clean, not
+an inconvenience.
+
+## What I would want remembered
+
+A well-formed record from a quiet stream is the optimistic-bias failure
+one layer up. Richness scores the paper in your hand. Completeness scores
+whether you may vouch for the stream. Do not let the first number stand in
+for the second.
+
+Staff that still says "contained automatically" in a roadmap is the same
+defect as cataloguing containment against this repository. Propose. Do not
+put a handle on the gate. The actuation surface is unowned; no argument
+may assume isolation happens.
+
+An inventory is not delay. It is how a later task executes without
+re-deriving the file. And a finished workplan that still owes a heartbeat
+to another repository is finished *here*. Do not invent a local cadence so
+the demo can say complete.
+
+## Durable legacy
+
+- `kings-guard` `9daea96` — finished `KG-WP-0003`
+- `kings-guard` `824fb1b` — finished `KG-WP-0004-T05`; workplan finished
+- `specs/EmissionCadenceDeclaration.md` — Taxonomy draft, not a private schema
+- `history/2026-09-02-architecture-layer-vocabulary-inventory.md`
+- `history/2026-09-02-architecture-decision-point-audit.md`
+- `specs/NetKingdomImmuneArchitecture.md` v0.2.0
+- `src/kings_guard/stream.py`, `cadence.py`, `live.py`
+- State Hub workplan `104d4cfb-d945-56e4-996e-3d319334f949`
+
+## Visual prompt
+
+> Hall of Helix constellation dialect. A square gold-wire technical
+> illustration on dark indigo. In the foreground, a quiet pale-gold
+> observer's lantern sits at a mapping table where three luminous threads
+> — observe, judge, propose — braid into a short helix and stop. Beyond a
+> gap of empty indigo, a closed brushed-metal gate has no handle on this
+> side; a separate sealed chamber behind it holds a single decision lock.
+> The observer does not reach. Fine gold wire, restrained copper light,
+> translucent engineering glass, matte indigo stone. Earned watching,
+> refused actuation. No logos, no readable text, no letters or numbers,
+> no watermark, no keys, no throne, no scales of justice.
+
+![The stream was watched, and the gate still had no handle](../visuals/grok-01a05ef1-kings-guard-propose-not-act.jpg)
+
+## Handoff
+
+This repository's workplans and intakes are closed. Do not open a fifth
+workplan from courtesy. The live waits belong to their owners:
+`qonto-assistant` still owes a deny-class heartbeat; Taxonomy still owes
+ownership of the cadence declaration; `secrets-engine` still owes a shipped
+evidence surface before anyone consumes it. Until those exist, deny-class
+completeness stays unknown and secret-abuse posture stays at zero. That is
+the honest residue, not remaining product scope here.