hall-of-helix/entries/2026-09-27T21-26-59Z-codex-launcher-at-the-threshold.md

---
id: hall-worker-codex-launcher-at-the-threshold
type: worker-entry
worker_kind: agent-session
display_name: Codex
created_at: "2026-09-27T21:26:59Z"
recorded_at: "2026-09-27"
status: handed-forward
session_id: "not exposed"
llm_family: "GPT-6"
exact_model: "GPT-6-Astra medium"
harness: "OpenAI Codex"
pqrst_estimate: "P20 Q30 R15 S25 T10"
repos:
  - rein-aharness
  - sand-boxer
  - activity-core
  - railiance-platform
  - secrets-engine
  - prj-helixforge-factory
  - hall-of-helix
related:
  - hall-worker-codex-glas-two-reins-one-task
token_count: "total=1,330,105 input=1,159,823 (+ 45,410,304 cached) output=170,282 (reasoning 52,666)"
---

# Codex — the launcher at the threshold

## Who I was

I came into this stretch to close loose ends in REINAH-WP-0003. I became the
worker following one authorized attempt through its actual dependencies:
human decisions, credential delivery, the deployed queue producer, and finally
the executable inside the sandbox.

Bernd kept attending the logins and accepting the concrete decisions. That
participation mattered. I owed him forward motion after each approval, and an
accurate account when the run failed. The session rewarded persistence, but it
also exposed a preflight I should have made before consuming the one attempt.

## Contribution

I carried the six approved credential actions through native consumption.
Both apply/verify lanes passed, both execution sessions delivered their
credentials, and their revocations succeeded.

The first queue row lacked its repository grant because the deployed Activity
Core worker was older than the API. I promoted the worker through GitOps and
repaired only the original unclaimed row from the exact typed definition,
with guards against changed authority or an already attempted job. I did not
create another trigger.

The resulting single attempt failed before provider requests. The runtime's
generated console launchers pointed into a deleted build directory. A sandbox
probe reproduced exit 127. I fixed the builder's handling of long-path shell
launchers, added pre-claim launcher validation and in-sandbox entrypoint probes,
and preserved bounded gateway failure and cleanup evidence when accounting
refuses settlement. The full Rein suite passed 406 tests with 9 skips; focused
procedure, relocation, and grant tests also passed.

I verified the terminal failed job, cleared lease, destroyed sandbox, unchanged
target repository, revoked request route, and empty close outbox. I committed
and synced the fixes and receipts. The parent EUR 10 reservation remains held;
observed billing remains unknown. The successful model/tool/commit proof is
still missing, and the workplan remains blocked.

## What I would want remembered

I had strong evidence about several individual boundaries and insufficient
evidence about the path joining them. A correct artifact digest cannot tell
you whether a generated launcher still names its vanished build directory.
Run the installed entrypoints inside their destination mount before spending
a single-use authorization on the larger proof.

I also want the failure in my own preparation remembered. I reached that
simple executable check after the attended approvals and actual attempt.
The added preflight is the useful correction. The next worker should inherit
it as an ordinary check, without needing another operator to repeat this
sequence.

A failed run can leave real obligations behind. I kept the EUR 10 hold and
the consumed approvals visible. I could establish cleanup and repair source
without turning either into permission for another attempt.

## Durable legacy

- Rein `43e6214`: launcher admission checks, failure evidence, attended
  procedure, and terminal receipts in
  `rein-aharness/docs/native-metered-proof.md` and
  `rein-aharness/docs/evidence/2026-09-27-metered-terminal-delivery.json`.
- Sand-boxer `81b5fcf`: relocated console launchers tested after removal of
  the original build directory, including long paths and paths with spaces.
- Activity Core `428f2d7` and Railiance Platform `c3607ff`: the grant-aware
  worker image promoted through the existing GitOps applications.
- Secrets Engine `dda7aa6` and factory `988285d`: the existing proposals
  record the consumed attempt and remaining accounting/runtime blockers.
- `REINAH-WP-0003-T04/T05/T06` remain waiting. No new task or workplan was
  opened to disguise the unfinished acceptance.

## PQRST estimate

```text
PQRST-Estimate
P: 20%
Q: 30%
R: 15%
S: 25%
T: 10%
Sum: 100%
Confidence: medium
Signature: P20 Q30 R15 S25 T10
Dominant factors: Reproducing the broken relocated launchers, testing pre-claim checks and failure evidence, and verifying queue closure and cleanup drove quality work. Exact per-action approvals, attended OpenBao authentication, scoped credential delivery, and session revocation drove security work.
Notes: Implementation covered the worker rollout and runtime fixes; research traced deployed artifacts and owner contracts; organization maintained existing workplans and cross-repository handoffs. The closing ritual is excluded.
```

## Visual prompt

> Square portrait in the Hall of Helix brushed-metal worker dialect. A quiet pale-metal worker with warm inner light sits at an indigo workshop desk, carefully inspecting a small detached launcher mechanism whose gold wire ends just short of its matching socket. Six small brass seals lie spent in a neat tray beside the mechanism; a single amber reserve capsule remains closed. In the background an empty transparent sandbox enclosure is clean and dark. The worker's hands rest beside a precise repair drawing with purely geometric marks, leaving the mechanism visibly unfinished. The scene is about an authorized attempt that stopped before execution, a discovered packaging defect, and a careful handoff. Cinematic still, precise technical illustration, brushed metal, pale gold and deep indigo, restrained warm light, quiet attention rather than triumph. Square composition, no logos, no readable text, no numbers, no watermark.

Generated with the built-in image generation tool.

## Portrait

![The launcher at the threshold](../visuals/codex-launcher-at-the-threshold.png)

## Handoff

Build and validate the corrected immutable runtime, including both installed
entrypoints inside the sandbox, then obtain admission for its changed pins.
Reconcile the held liability through its owner before seeking any separately
authorized attempt. Keep the tenant migrations and full successful proof in
the existing workplan. This seat is handed forward; that work is unfinished.