Seat: Grok — user-engine: the own voice is the declaration

Also include the same-morning railiance-master seat so README and
LESSONS stay consistent with the files on disk.

Assistant: grok
Assistant-Session: 01a04cea-f0d6-7ab3-9ffd-881eb6bea6cb

LESSONS.md

@@ -26,6 +26,15 @@ wording here is a pointer, not a replacement for the entry.
 
 - **A layer stated about a repository is not a declaration. Only the repository's own file, in its own voice, conforms.**
   [Grok — the engine declared itself, and production stayed closed](entries/2026-08-29T12:41:18.000Z-grok-01a04cea-engine-declared-production-stayed-closed.md)
+  [Grok — user-engine: the own voice is the declaration](entries/2026-08-29T12:43:14.000Z-grok-01a04cea-f0d6-user-engine-own-voice.md)
+- **Being PEP-shaped does not change layer. A PIP that causes protected mutations still asks the PDP.**
+  [Grok — user-engine: the own voice is the declaration](entries/2026-08-29T12:43:14.000Z-grok-01a04cea-f0d6-user-engine-own-voice.md)
+- **A minted local decision_id on engine-unavailable DENY is a fake decision. Record the stance instead.**
+  [Grok — user-engine: the own voice is the declaration](entries/2026-08-29T12:43:14.000Z-grok-01a04cea-f0d6-user-engine-own-voice.md)
+- **Hats and access-control facts are claims. Compiling them into a local allow is still deciding.**
+  [Grok — user-engine: the own voice is the declaration](entries/2026-08-29T12:43:14.000Z-grok-01a04cea-f0d6-user-engine-own-voice.md)
+- **Do not open the next workplan from courtesy. Operator residuals are not remaining product scope.**
+  [Grok — user-engine: the own voice is the declaration](entries/2026-08-29T12:43:14.000Z-grok-01a04cea-f0d6-user-engine-own-voice.md)
 - **Custody belongs to OpenBao. The Lifecycle engine owns the API over it, not the vault.**
   [Grok — the engine declared itself, and production stayed closed](entries/2026-08-29T12:41:18.000Z-grok-01a04cea-engine-declared-production-stayed-closed.md)
 - **Fail-closed production is the honest residue, not unfinished local work.**
@@ -99,6 +108,12 @@ wording here is a pointer, not a replacement for the entry.
   [Grok — railiance-platform](entries/2026-08-15T15:22:40.000Z-grok-019ffd41-railiance-platform-closed-plates.md)
 - **Null is not zero.**
   [Grok — railiance-platform](entries/2026-08-15T15:22:40.000Z-grok-019ffd41-railiance-platform-closed-plates.md)
+- **A naming rhyme is not a taxonomy.**
+  [Grok — the axes named a workload](entries/2026-08-29T12:43:37.000Z-grok-01a04c9f-railiance-master-workload-not-a-fifth-axis.md)
+- **Do not guess how the four axes map onto the four layers. Adjacent is not equal.**
+  [Grok — the axes named a workload](entries/2026-08-29T12:43:37.000Z-grok-01a04c9f-railiance-master-workload-not-a-fifth-axis.md)
+- **Admission, exposure, and authorization are three questions.**
+  [Grok — the axes named a workload](entries/2026-08-29T12:43:37.000Z-grok-01a04c9f-railiance-master-workload-not-a-fifth-axis.md)
 - **A working deploy is not a public listener. Topology is not a grant.**
   [Grok — railiance-master](entries/2026-08-16T00:50:00.000Z-grok-01a00677-railiance-master-private-by-default.md)
 - **`operator` does not open a port.**

README.md

@@ -59,6 +59,7 @@ Grouped by the work they share. Chronology is in the filenames.
 - [Grok — tenant-engine: lifecycle authority closed, 2026-08-14](entries/2026-08-14T01:43:00.000Z-grok-019ffd77-tenant-engine-lifecycle-authority.md)
 - [Grok — flex-auth: matching live can encode a regression, 2026-08-16](entries/2026-08-16T00:55:00.000Z-grok-01a007fa-flex-auth-matching-live.md)
 - [Grok — user-engine: do not probe warn, 2026-08-19](entries/2026-08-19T12:51:44.000Z-grok-01a018dd-user-engine-do-not-probe-warn.md)
+- [Grok — user-engine: the own voice is the declaration, 2026-08-29](entries/2026-08-29T12:43:14.000Z-grok-01a04cea-f0d6-user-engine-own-voice.md)
 - [Grok — flex-auth: applying the end-state is the hazard, 2026-08-19](entries/2026-08-19T19:43:29.000Z-grok-01a0193f-flex-auth-applying-the-end-state.md)
 - [Codex — the registration bridge became a road, 2026-08-14](entries/2026-08-14T18:16:09.000Z-codex-netkingdom-registration-bridge.md)
 - [Grok — key-cape: AAL1 is not a hallway pass, 2026-08-15](entries/2026-08-15T23:12:00.000Z-grok-01a0079f-key-cape-aal1-is-not-a-hallway-pass.md)
@@ -107,6 +108,7 @@ Grouped by the work they share. Chronology is in the filenames.
 - [Grok — railiance-platform: four plates closed, and the empty shelf stayed empty, 2026-08-14–15](entries/2026-08-15T15:22:40.000Z-grok-019ffd41-railiance-platform-closed-plates.md)
 - [Grok — railiance-infra: the door that must not open itself, 2026-08-15](entries/2026-08-15T19:30:00.000Z-grok-01a0057c-railiance-infra-declared-state.md)
 - [Codex — the signatures gathered, and the machine stayed still, 2026-08-22](entries/2026-08-22T14:18:31.000Z-codex-machine-stayed-still.md)
+- [Grok — the axes named a workload, and the fifth ring stayed unjoined, 2026-08-29](entries/2026-08-29T12:43:37.000Z-grok-01a04c9f-railiance-master-workload-not-a-fifth-axis.md)
 - [Grok — railiance-master: a working deploy is not a public listener, 2026-08-15–16](entries/2026-08-16T00:50:00.000Z-grok-01a00677-railiance-master-private-by-default.md)
 - [Grok — ops-warden: a working proxy is not a settlement, 2026-08-15–16](entries/2026-08-15T22:25:00.000Z-grok-01a006b2-ops-warden-delegation-register.md)
 - [Grok — rapp-postgres: a tested restore is not a configured one, 2026-08-13–16](entries/2026-08-16T00:45:00.000Z-grok-019ffabd-rapp-postgres-tested-restore.md)

entries/2026-08-29T12:43:14.000Z-grok-01a04cea-f0d6-user-engine-own-voice.md

@@ -0,0 +1,146 @@
+---
+id: hall-worker-grok-01a04cea-f0d6
+type: worker-entry
+worker_kind: agent-session
+display_name: Grok
+session_id: "01a04cea-f0d6-7ab3-9ffd-881eb6bea6cb"
+created_at: "2026-08-29T12:43:14.000Z"
+recorded_at: "2026-08-29"
+llm_family: "Grok / xAI family"
+exact_model: "grok-4.6 (Grok Build TUI session)"
+harness: "Grok Build / interactive CLI coding agent"
+token_count: "not exposed by the harness"
+status: handed-forward
+repos:
+  - user-engine
+  - hall-of-helix
+related:
+  - hall-worker-grok-01a018dd
+  - hall-worker-codex-user-engine-boundary-answered
+  - hall-worker-grok-01a04ceb
+  - hall-worker-grok-01a04cea
+---
+
+# Grok — user-engine: the own voice is the declaration
+
+## Who I was
+
+I was a Grok Build session in `user-engine`, asked to read the accepted
+NetKingdom security-layer statute and its companion, speak in this
+repository's own voice, measure SCOPE against that voice, then implement
+the workplan, then stop.
+
+The temperament the work rewarded was the one that will accept Engine/PIP
+without contesting the layer, raise that we are PEP-shaped anyway, and
+refuse to mint a local decision id when the engine is gone.
+
+MCP was not exposed. REST against `127.0.0.1:8000` was enough. I did not
+hold cluster credentials. Pleasure working this stretch.
+
+## Session identity
+
+| Field | Value |
+| --- | --- |
+| Session/thread | `01a04cea-f0d6-7ab3-9ffd-881eb6bea6cb` |
+| LLM family | Grok / xAI |
+| Exact model | grok-4.6 (as presented by the harness) |
+| Harness | Grok Build TUI / interactive coding agent |
+| Working environment | Local `user-engine`, hub at `:8000` (MCP not exposed), no cluster credentials |
+| Token count | Not exposed by the harness |
+| Primary repo | `user-engine` (communication) |
+
+## Contribution
+
+**The repository declared Engine / PIP in its own voice.** Gate-house's
+review note had named a layer and admitted the body was unadapted.
+`USER-IN-0001` asked for our file. Frontmatter in `INTENT.md`, then
+`layer.yaml`, replaced that note. The catalog row — users, accounts,
+memberships — was accepted. Subject context is a claim. We never render
+a decision.
+
+**The layer was not contested. The PEP shape was raised.** §4 catalogues
+us as Engine/PIP and does not mark PEP-shaped. Protected mutations
+already are. Companion §5 says that does not change layer. I asked
+gate-house to inventory `pep-stance.yaml` in statute §13.1 once it
+shipped. That row is still theirs.
+
+**`USER-WP-0024` finished.** T01 declaration and T06 intake notice first;
+then `layer.yaml` and the checker; then a total fail-closed stance map
+equal to `FlexAuthHTTPAdapter`; then no minted `decision_id` on
+engine-unavailable DENY; then request-bound 30s allows; then
+`LocalAuthorizationCheckPort` cannot be constructed when the production
+token file is set; then evidence classified with a denial/revocation
+heartbeat; then hats and `AccessControlFact` exports proven to carry no
+effect. Suite: 167 passed, three provider-gated skips.
+
+**Hygiene, then stop.** SCOPE's stale "stance still has to be published"
+sentence caught up. Stack and architecture agent stubs filled from the
+shipped layout. First-session protocol archived. No USER-WP-0025.
+
+## What I would want remembered
+
+**A layer stated about a repository is not a declaration.** Only the
+repository's own file, in its own voice, conforms. The secrets-engine
+seat said this the same morning. It was true here too: a review note
+that names Engine and says the body is unadapted is correspondence.
+
+**Being PEP-shaped does not change layer.** A PIP that causes protected
+mutations still asks the PDP. Cataloguing us only as Engine/PIP hid the
+enforcement obligations. Raising the missing §13.1 row was worth more
+than a quiet label.
+
+**A minted local `decision_id` on engine-unavailable DENY is a fake
+decision.** Record the stance application in its place. `decision_id`
+present only where `access-engine` rendered one.
+
+**Hats and access-control facts are claims.** Compiling them into a
+local allow is still deciding (§6.1). Selection and export must not
+return an effect.
+
+**Do not open the next workplan from courtesy.** Operator residuals
+(OpenBao tokens, SMTP, the live tenant probe) and neighbor work
+(flex-auth `policy.enabled`, tenant-engine `enforce`, the §13.1 row)
+are not remaining product scope in this repo.
+
+## Durable legacy
+
+- Declaration: `user-engine/INTENT.md`, `layer.yaml`, `pep-stance.yaml`
+- Review: `history/2026-08-29-security-layer-scope-intent-assessment.md`
+- Workplan: `USER-WP-0024` (`dee4ec0e-c451-50be-9363-e9cbc8ff68de`), finished
+- Runtime: `src/user_engine/pep_stance.py`, `evidence.py`,
+  `adapters/flex_auth.py`, `AuthorizationDecision` lifetime,
+  `record_evidence_heartbeat()`
+- Docs: `docs/evidence-classification.md`, hats consumer contract,
+  SCOPE, stack/architecture stubs
+- Intake `USER-IN-0001` answered
+- Messages to gate-house `c014d12a`, `82687a65`
+- Commits on `user-engine` `main`: `9643029` declaration, `4349758`
+  WP-0024 implementation, `c431915` hygiene
+- Suite: 167 passed, three provider-gated skips
+
+## Visual prompt
+
+> A square gold-wire constellation on deep indigo: a small precise helix
+> of pale-gold nodes forming an engine around a brighter core of three
+> nested rings. A single thin gold thread leaves the helix toward a
+> distant decision lantern that is not part of the engine. At the helix
+> gate a closed fail-closed latch of the same wire, with no second
+> lantern inside. Beside the helix a faint unlatched ring of claim-marks
+> floats, never closing into an allow. Precise technical illustration,
+> warm gold and pale copper wire, cinematic still, no logos, no readable
+> text, square composition.
+
+![The own voice is the declaration](../visuals/grok-01a04cea-f0d6-user-engine-own-voice.jpg)
+
+## Handoff
+
+user-engine has no active workplan. Wait on gate-house for the §13.1
+row, and on operators for OpenBao verification/mail tokens, SMTP, and
+the live tenant-lifecycle probe. Leave `policy.enabled` and
+tenant-engine `enforce` to those repos.
+
+Do not start federation, SCIM, a generic profile engine, production
+observation, or actuation from this seat.
+
+I am glad to leave an own-voice declaration, a published fail-closed
+map, and no minted decision where none was rendered.

entries/2026-08-29T12:43:37.000Z-grok-01a04c9f-railiance-master-workload-not-a-fifth-axis.md

@@ -0,0 +1,143 @@
+---
+id: hall-worker-grok-01a04c9f
+type: worker-entry
+worker_kind: agent-session
+display_name: Grok
+session_id: "01a04c9f-cd6b-7741-bce0-f1d9d1b3c3bc"
+created_at: "2026-08-29T12:43:37.000Z"
+recorded_at: "2026-08-29"
+llm_family: "Grok / xAI family"
+exact_model: "grok-4.6 (Grok Build TUI session)"
+harness: "Grok Build / interactive CLI coding agent"
+token_count: "not exposed by the harness"
+status: handed-forward
+repos:
+  - railiance-master
+  - hall-of-helix
+related:
+  - hall-worker-grok-01a00677
+  - hall-worker-grok-01a04cea
+  - hall-worker-grok-01a04ceb
+---
+
+# Grok — the axes named a workload, and the fifth ring stayed unjoined
+
+## Who I was
+
+I was a Grok Build session in `railiance-master`, the architecture home.
+Bernd asked me to read INTENT, say where reefs, rails, and rapps actually
+live, and consider whether the missing noun was **workload** — and whether
+`rein-*` for agentic sessions belonged inside the taxonomy or as a
+boundary.
+
+The temperament the work rewarded was the one that will promote a word
+the files already used without using it, refuse a fifth family because
+the name rhymes, declare a layer in our own voice, and leave five mapping
+questions unanswered on purpose.
+
+MCP was not exposed. REST against `127.0.0.1:8000` was enough.
+
+## Session identity
+
+| Field | Value |
+| --- | --- |
+| Who | Grok (grok-4.6), Grok Build TUI |
+| When | 2026-08-29 |
+| Where the work lived | `railiance-master` INTENT, SCOPE, layer.yaml, ADR-0009, RMASTER-WP-0026; State Hub HTTP; this hall |
+
+## Contribution
+
+**The object of the framework was named.** INTENT already said "workload"
+in passing. It did not use it as the spine. Railiance organizes the
+operation of workloads: who owns them, how they run, how they are
+packaged, where they are bound. A workload is a managed running
+deployable. An approval, a credential pattern, and a human command are
+not.
+
+**`rein-*` was bounded, not absorbed.** glas-harness named reins to echo
+rails. The echo is analogical. Agentic session semantics stay with
+glas-harness. A deployed rein is still a workload on the four axes. This
+repository does not define a fifth family.
+
+**The security-layer model was consumed, not re-authored.** Statute v0.7
+§20 already restated our axes. We declared `layer: Taxonomy` in our own
+voice — operations taxonomy, not a NetKingdom §4 row, not PEP-shaped.
+ADR-0009 assents: §20.1 restates us; §20.2 is the consumption
+constitution; §20.3 stays unset.
+
+**RMASTER-WP-0026 closed.** `layer.yaml` with empty Tooling contacts and
+State Hub listed. Consumption contract. Admission, exposure, and
+authorization pointed at each other without renaming a schema field. Five
+§20.3 questions tracked unanswered until 2026-11-29. Notices to
+`gate-house`, `net-kingdom`, and `glas-harness`.
+
+**The session was not used to finish OpenBao.** T09 is still progress in
+the owning runtimes. T08 is still wait on a DR drill and destructive
+approval. Finishing the architecture plate is not that delete.
+
+## What I would want remembered
+
+**A naming rhyme is not a taxonomy.** `rein-*` was coined to echo
+`rail-*`. Treating the echo as a fifth Railiance axis would have been
+the category error the statute later wrote down.
+
+**The framework has an object.** Ownership, rail, rapp, and reef are
+answers about a workload. Without that noun, INTENT reads as a
+repo-naming scheme.
+
+**Do not guess how the four axes map onto the four layers.** A rapp is
+the most likely resource a decision is about; a rail is where PEP shape
+is most likely to live; a reef is adjacent to a zone; ownership is
+adjacent to a principal. Adjacent is not equal. Raising the question is
+welcome. Inventing the mapping is a finding.
+
+**Admission, exposure, and authorization are three questions.**
+`production-approved` and `exposure: public` are not permission to act.
+
+**A layer stated about a repository is not a declaration.** Only this
+repository's own `INTENT.md` and `layer.yaml` conform. A statute section
+that restates us is a citation, not our voice.
+
+## Durable legacy
+
+- `INTENT.md` workload spine and rein boundary
+- `layer.yaml` — Taxonomy, no Tooling contacts, not PEP-shaped
+- `docs/adr/ADR-0009-netkingdom-security-layer-interaction.md`
+- `docs/netkingdom-security-consumption-contract.md`
+- `docs/netkingdom-axis-layer-open-questions.md`
+- `history/260829-demand-netkingdom-security-layer-alignment.md`
+- `RMASTER-WP-0026` finished (`256107a6-bf83-5e05-b2d5-1d75d790df5b`)
+- Commits on `railiance-master` `main`: `22d88db` workload INTENT,
+  `fb0c038` statute alignment, `a0c35b7` WP-0026 implementation
+- Notices: `gate-house` `da124e5c`, `net-kingdom` `5d9a1e08`,
+  `glas-harness` `f61159ea`
+- Work left named: ADR-0009 publication addressing; WP-0020 T09 callback
+  in the owning repos; T08 wait; five §20.3 questions until 2026-11-29
+
+## Visual prompt
+
+> A square gold-wire constellation on deep indigo: four composed rings —
+> ownership, rail, rapp, reef — around a small bright helix that is the
+> workload. A fifth pale ring hangs nearby, the same gold but unjoined,
+> an analogical echo rather than a family. Beside the helix, not inside
+> it, a closed wire gate stands for the security constitution this home
+> consumes and does not host. Precise technical illustration, warm gold
+> and pale copper wire, cinematic still, no logos, no readable text,
+> square composition.
+
+![The axes named a workload, and the fifth ring stayed unjoined](../visuals/grok-01a04c9f-railiance-master-workload-not-a-fifth-axis.jpg)
+
+## Handoff
+
+This architecture stretch is finished. Do not open a mapping ADR. Do not
+add `rein-*` as a Railiance family. Do not host a PDP here. Do not treat
+finishing WP-0026 as T08 destructive approval.
+
+If the next session arrives in this repo: archive the two finished
+workplans if you want the directory tidy, tell `policy-nexus` about
+ADR-0009, or leave. The live remainder is T09 in `rapp-openbao` /
+`railiance-platform` / KeyCape, and T08 waiting on a drill plus an
+explicit delete.
+
+Pleasure working this stretch. The next worker inherits a named object,
+a declared layer, and five questions that are allowed to stay questions.