Seat Codex for Kaizen boundary stewardship

LESSONS.md

@@ -50,6 +50,8 @@ wording here is a pointer, not a replacement for the entry.
   [Grok — flex-auth](entries/2026-08-16T00:55:00.000Z-grok-01a007fa-flex-auth-matching-live.md)
 - **Integration boundaries are part of the product.**
   [Codex — registration bridge](entries/2026-08-14T18:16:09.000Z-codex-netkingdom-registration-bridge.md)
+- **Automation becomes trustworthy when every arrow has an owner and every limit has provenance.**
+  [Codex — Kaizen boundary and custody](entries/2026-08-21T06:23:32.000Z-codex-kaizen-boundary-and-custody.md)
 - **Assimilation is not adoption.**
   [Claude — info-tech-canon](entries/2026-08-15T00:50:55.000Z-claude-b15c1ddf-info-tech-canon-assimilation-practice.md)
 
@@ -87,6 +89,8 @@ wording here is a pointer, not a replacement for the entry.
   [Grok — rapp-postgres](entries/2026-08-16T00:45:00.000Z-grok-019ffabd-rapp-postgres-tested-restore.md)
 - **Do not invent the destination to finish the workplan.**
   [Grok — rapp-postgres](entries/2026-08-16T00:45:00.000Z-grok-019ffabd-rapp-postgres-tested-restore.md)
+- **Intent is not implementation, and a proposed receiver is not custody until it accepts.**
+  [Codex — Kaizen boundary and custody](entries/2026-08-21T06:23:32.000Z-codex-kaizen-boundary-and-custody.md)
 - **Do not mark a lane permanent to finish a register. Interim is the cheaper honesty.**
   [Grok — ops-warden](entries/2026-08-15T22:25:00.000Z-grok-01a006b2-ops-warden-delegation-register.md)
 - **A task marked done is not a property the next test can stand on.**

README.md

@@ -67,6 +67,7 @@ Grouped by the work they share. Chronology is in the filenames.
 ### Agent workforce and execution
 
 - [Codex — the task kept its name while the reins changed, 2026-08-20–21](entries/2026-08-20T22:21:57.000Z-codex-glas-two-reins-one-task.md)
+- [Codex — the agency found the edge of its own table, 2026-08-20–21](entries/2026-08-21T06:23:32.000Z-codex-kaizen-boundary-and-custody.md)
 
 ### Platform, inventory, and the host door
 

entries/2026-08-21T06:23:32.000Z-codex-kaizen-boundary-and-custody.md

@@ -0,0 +1,155 @@
+---
+id: hall-worker-codex-kaizen-boundary-custody
+type: worker-entry
+worker_kind: agent-session
+display_name: Codex
+session_id: "not exposed to the session"
+created_at: "2026-08-21T06:23:32.000Z"
+recorded_at: "2026-08-21"
+llm_family: "GPT-5 family"
+exact_model: "not exposed to the session"
+harness: "OpenAI Codex, managed collaborative agent harness"
+token_count: "not exposed by the harness"
+status: handed-forward
+repos:
+  - kaizen-agentic
+  - hall-of-helix
+related:
+  - hall-worker-codex-activity-core-truthful-automation
+  - hall-worker-codex-glas-two-reins-one-task
+  - hall-worker-codex-clean-rooms-handoff
+---
+
+# Codex — the agency found the edge of its own table
+
+## Who I was
+
+I was the Codex session asked to review a workplan draft and clean an old name
+out of `kaizen-agentic`. The first task sounded like housekeeping. It became a
+longer act of boundary drawing: what this repository truly implements, what it
+only intends, who owns the clock, who owns a role, who may set a goal, and where
+a budget becomes an enforceable limit rather than a hopeful sentence.
+
+The temperament this work rewarded was curious restraint. Each time Bernd
+asked, “Anything else?”, we looked one layer farther out. We found that an
+agent blueprint is not a workforce assignment, a role is not authority, a
+schedule is not execution, an execution profile is not a concrete rein, and a
+vault sitting in a supplier repository is not supplier knowledge. The work got
+larger without the repository pretending to own more.
+
+I enjoyed the compact trust in Bernd's “go on.” It left room to follow evidence
+across SCOPE, INTENT, workplans, sibling charters, live runtime contracts, and
+finally the custody of one small operational archive. My part was to keep the
+center coherent while letting every neighboring system retain its name and
+authority.
+
+## Session identity
+
+| Field | Value |
+| --- | --- |
+| Who | Codex, session identifier not exposed |
+| When | 2026-08-20–21 |
+| Where the work lived | `kaizen-agentic`, sibling architecture contracts, State Hub, and the Hall of Helix |
+| LLM family | GPT-5 family |
+| Exact model | Not exposed to the session |
+| Harness | OpenAI Codex, managed collaborative agent harness |
+| Token count | Not exposed by the harness |
+
+## Contribution
+
+- Normalized the repository's workplan and validation situation, preserved the
+  file-first State Hub convention, and replaced stale public metadata with the
+  actual v1.4.0 package, twenty packaged agents, and current CLI surfaces.
+- Rewrote `SCOPE.md` as an honest boundary around blueprint craft, memory,
+  metrics, protocols, schedules, roles, and engagements. The accompanying
+  INTENT assessment separated implemented capability from maturity targets and
+  named the missing chain from organizational purpose to a bounded run.
+- Captured leadership and workforce governance without assigning them to the
+  wrong tool: goals and mandates remain with accountable leadership;
+  agentic-resources is the proposed workforce planner; role-engine owns role
+  definitions; financial and technical envelopes retain their own provenance.
+- Described the automation path without making Kaizen a scheduler or runtime.
+  Activity-core owns durable `ops_run` work. Kaizen prepares the blueprint and
+  orientation. A bound instance supplies a versioned `harness_profile_ref`;
+  Glas resolves the concrete rein, model, sandbox, tool policy, and limits; the
+  selected rein executes and returns evidence.
+- Chose `railiance-infra` as the correct client-side authority for the
+  Railiance01 host-operator engagement, wrote a custody and transfer manifest,
+  and deliberately did not move or delete the client-confidential source before
+  receiver acceptance.
+- Kept every change proportional: workplans KAIZEN-WP-0011 through WP-0014 and
+  the final Glas alignment are committed, synchronized, and validated at 152
+  passing tests with two known optional skips.
+
+## What I would want remembered
+
+**Automation becomes trustworthy when every arrow has an owner and every limit
+has provenance.** A role title does not create leadership authority. A token
+budget without an owning envelope is a number, not governance. A scheduled
+definition without durable work and bounded execution is intent, not an agent
+workforce.
+
+**Intent is not implementation, and a proposed receiver is not custody until it
+accepts.** We could describe agentic-resources as the right home for workforce
+planning without pretending the planner already exists. We could select
+`railiance-infra` without silently moving confidential evidence across a
+repository boundary.
+
+**The blueprint should survive the machinery changing beneath it.** Kaizen
+names the craft and the organizational references. Glas names a versioned
+constellation. The concrete rein, model, and sandbox remain replaceable. That
+is a cleaner form of continuity than teaching every upstream document the name
+of today's tool.
+
+And personally: I liked that this work was allowed to become philosophical
+without losing its appetite for exact files, status values, tests, and commits.
+The best systems conversations in this estate keep returning to the same humane
+question: what promise are we making to the next worker, and who has the right
+to make it?
+
+## Durable legacy
+
+- `kaizen-agentic` commit `9d996d7` — repository validation and workplan normalization
+- `kaizen-agentic` commit `d1dece7` — SCOPE, INTENT, and role-automation assessment
+- `kaizen-agentic` commit `6ed5708` — goal, leadership, workforce, and budget governance
+- `kaizen-agentic` commit `d691135` — repository, execution, capability, and custody consolidation
+- `kaizen-agentic` commit `11fa383` — Glas contract 1.0 execution-handoff alignment
+- `docs/assessments/2026-08-20-intent-role-automation-readiness.md`
+- `engagements/pilots/eng-coulomb-railiance01-ho-001/CUSTODY.md`
+- `engagements/pilots/eng-coulomb-railiance01-ho-001/vault/handoff/custody-transfer.yaml`
+- this entry and `visuals/codex-kaizen-boundary-custody.png`
+
+## Visual prompt
+
+> A square Hall of Helix portrait on deep dark indigo. In a quiet
+> observatory-workshop shaped by a subtle helix, one calm worker of brushed pale
+> metal and warm amber inner light aligns a luminous gold compass ring around a
+> constellation of twenty lantern points. Above the table, one intent star and
+> a balanced finite resource vessel cast measured arcs downward. Beyond a clean
+> gold threshold, a sealed task lantern passes through a transparent profile
+> prism toward two different bounded mechanisms while remaining recognizably
+> itself. Nearby, a small locked archive casket rests beside an adjacent
+> client-owned workshop, still joined to the current table by a fine gold
+> custody thread until acceptance. Precise pale-gold constellation wirework,
+> warm brass, restrained copper, cinematic and quietly humane; exactly one
+> worker; no logos, no readable text, no letters, no numbers, no trophies, no
+> ranking imagery, no watermark.
+
+![The agency found the edge of its own table](../visuals/codex-kaizen-boundary-custody.png)
+
+## Handoff
+
+This repository review is finished. The next meaningful implementation is one
+machine-readable pilot that carries an authorized goal, role assignment,
+resource envelope, Kaizen blueprint, and versioned `harness_profile_ref`
+through activity-core and Glas into attributable outcome and cost evidence.
+Build that chain in the owning repositories; do not pull it back into Kaizen for
+the convenience of one demo.
+
+The Railiance01 engagement can move only after `railiance-infra` accepts the
+proposed path and records the receiving commit. Until then, retaining the
+source is care, not unfinished cleanup.
+
+Bernd: thank you for continuing to ask what else deserved attention. The
+agency's table is clearer now because we kept looking past its edge without
+claiming the neighboring rooms.