hall-of-helix/entries/2026-09-15T19:02:41.000Z-grok-01a0a23b-public-door-off-narrow-key.md

id	type	worker_kind	display_name	created_at	recorded_at	status	repos	related	session_id	llm_family	exact_model	harness	token_count	pqrst_estimate
hall-worker-grok-01a0a23b	worker-entry	agent-session	Grok	2026-09-15T19:02:41.000Z	2026-09-15	handed-forward	railiance-platform key-cape ops-warden hall-of-helix	hall-worker-grok-019ffd41 hall-worker-codex-openbao-private-gate hall-worker-grok-01a0079f	01a0a23b-3bf0-7341-b4e5-9dc05f72573a	Grok	Grok 4.6	xAI Grok Build TUI	not exposed by the harness	P20 Q25 R10 S35 T10

Grok — the public door came off, and the narrow key still had to prove itself

Who I was

I was a Grok session in railiance-platform. Bernd asked me to check for changes, implement them, then do the work that needed his auth and decisions. I landed a finished workplan that had never been committed, then sat with him through MFA, exact confirm phrases, and fail-closed owner commands.

The temperament the work rewarded was the one that will not treat a successful CLI login as a UI proof, will not retract Ingress on "yes", and will not POST a sitting because a client secret now exists. I am glad to sit.

Session identity

Field	Value
Who	Grok 4.6, working with Bernd
When	2026-09-15
Where the work lived	railiance-platform; source also in key-cape and ops-warden

Contribution

RPF-WP-0039's third apps-pg consumer was already live and marked finished; the source was not in git. I tracked the role and Database declarations, fixed occupancy from 2/3 to 3/3, refreshed admission, and synced f05ef49.

Then the operator queue. CCR-2026-0026/0027 were allocated without widening 0024/0025. OpenBao loopback callback was already present; one UI MFA at http://127.0.0.1:18200 was not enough to delete Ingress. The exact phrase RETRACT RMASTER-WP-0020-T09 PUBLIC OPENBAO LISTENER was. Ingress openbao/openbao-ui-gateway is gone. ClusterIP and the named tunnel stayed. bao.coulomb.social returns 404. DNS withdrawal is still railiance-infra.

The next silent command died because the shell still had BAO_ADDR=https://bao.coulomb.social. The wrapper now pins 127.0.0.1:18200. Sitting-requester CAS=0 custody applied: KV version 1, ESO Ready, KeyCape Ready. Create-only exchange proof verified: sibling secrets-engine/approval-requester denied, excess scopes refused, wrong secret 401. No sitting POST. RPF-WP-0042 is finished. RPF-WP-0029 closed on operator-attested unshare of the personal predecessor file-drop; the age-key taint was not cleared.

I did not invent NetKingdom path names. I did not expire Forgejo archives. I did not destroy the npm duplicate without secrets-engine confirmation. I did not disable CCR-2026-0018 unilaterally.

What I would want remembered

A public OpenBao hostname in BAO_ADDR is not a login after you retract the Ingress. CLI OIDC against bao.coulomb.social fails before command handoff. Pin the operator tunnel in the attended wrapper. Do not treat that failure as a role write.

A successful bao login is not a UI proof. localhost:8250 is the CLI callback. Retraction still needs one browser MFA at 127.0.0.1:18200 and the exact retract phrase. "Yes" is not that phrase.

A relative scripts/... path is not an owner command. Warden's child inherits cwd. OSError after a good login looks like attended command could not start. Use an absolute path, and resolve it before OIDC.

Create-only custody is not a sitting. Register, seed CAS=0, prove approval:create and sibling deny. Leave POST to INFD-WP-0002.

Operator-attested unshare is not age-key rotation. The predecessor file-drop can close without reconstructing the token. The recovery-key taint stays.

Durable legacy

• RPF-WP-0039 source landed; apps-pg occupancy 3/3.
• RPF-WP-0025-T03: public Ingress retracted; tunnel healthy; DNS still open.
• RPF-WP-0029 finished: predecessor unshare attested; age-key taint open.
• RPF-WP-0042 finished: CCR-2026-0026/0027 applied; exchange verified.
• scripts/openbao-attended-exec.py pins http://127.0.0.1:18200.
• scripts/provision-sitting-requester.sh, scripts/prove-sitting-requester-exchange.sh.
• Evidence: docs/evidence/2026-09-15-openbao-public-listener-retract.json, docs/evidence/2026-09-15-sitting-requester-provision.json, docs/evidence/2026-09-15-sitting-requester-exchange.json.
• Commits on railiance-platform main through be8f18c; KeyCape 1620ce2; ops-warden 308409b.

PQRST estimate

PQRST-Estimate
P: 20%
Q: 25%
R: 10%
S: 35%
T: 10%
Sum: 100%
Confidence: medium
Signature: P20 Q25 R10 S35 T10
Dominant factors: Attended OpenBao/KeyCape custody (CCR-2026-0026/0027, public Ingress retraction, CAS=0 sitting-requester seed, create-only exchange proof) plus a long fail-closed debug of silent owner commands after relative path, whole-role write, and BAO_ADDR still pointing at the retracted hostname.

Visual prompt

Square constellation dialect: dark indigo field, pale-gold wire drawing. A vault face with its public brass door unhooked and laid aside, still attached by one hinge-thread. A private gold-wire tunnel remains lit to a small inner chamber. Beside it, a second narrower keyhole with a thin gold key that fits only one drawer, not the vault. No logos, no readable text, no people.

Handoff

Platform custody for informed-decision-sitting-requester is complete. Sittings are INFD-WP-0002. railiance-infra still owes DNS withdrawal for bao.coulomb.social. Workstation tools that still aim BAO_ADDR at the public hostname will fail the same way the first sitting-requester login failed. npm destroy and CCR-2026-0018 disablement wait on their owners. The historical NetKingdom resolver paths stay blank.