Skip to content

Rehearse Claude READ and bind its worker launch profile - #311

Merged
sushiHex merged 4 commits into
mainfrom
fix/40-read-session-rehearsal
Oct 27, 2026
Merged

sushiHex merged 4 commits into
mainfrom
fix/40-read-session-rehearsal

Conversation

@sushiHex

@sushiHex sushiHex commented Oct 26, 2026 •

Copy link
Copy Markdown
Owner

Make the bounded Claude READ procedure runnable through versioned one-phase operator tooling, and rehearse its actual generated commands and produced receipts without credentials. Private bindings remain external; the operator-tool content revision and installed controller commit are distinct inputs.

The real accepting rehearsal exposed a pre-existing production assembly bug: the vendor-free READ worker uses Claude's launch policy, but its physical probe selected the generic workload label from vendor presence. A closed, revision-bound launch-profile selection now states the correct worker policy independently of vendor identity. The probe still requires one exact enforcing label and all existing containment predicates. No policy, protocol, mount, credential or egress authority is widened.

Risk tier: consequential. Portable tests exercise actual CLI/package/receipt behavior and profile accepting/refusing cases. The required foundation step executes the full generated chain with a real installed test controller/store/lane and a compiled harmless peer; actual outputs feed subsequent steps, including withdrawal after a post-activation refusal. Failed phases retain bounded diagnostics before cleanup. The other physical lanes and full verification remain required. Final-head results are recorded in this PR before merge.

Review: connector review completed without findings on initial operator implementation d07e6ac. The hosted fixture corrections and the newly exposed controller-profile boundary receive narrow independent review; that original review is not represented as covering the later source change.

Limits: SSH/SCP are local process-boundary doubles; drift is a measured test-scoped double. This does not qualify a vendor or enable a production provider. The controller source correction requires a newly reviewed installation pin and fresh qualification before the separately authorized live attempt; the old controller approval is not silently reused. Frozen plans remain unchanged.

Refs #40

@sushiHex
sushiHex marked this pull request as ready for review October 26, 2026 22:22
@chatgpt-codex-connector

chatgpt-codex-connector Bot commented Oct 26, 2026 •

Copy link
Copy Markdown

Codex Review Summary

This comment shows the latest Codex review activity on this pull request.

Review Status Commit Review trigger
📝 Code Review ✅ Completed 2026-10-26T22:24:20.615231Z d07e6ac Draft marked ready
ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

  • Open a pull request for review
  • Mark a draft as ready
  • Comment "@codex review" or "@codex security review".

Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings.

@sushiHex

Copy link
Copy Markdown
Owner Author

Initial head d07e6ac: full verify/mutation gate and runner qualification passed;
lifecycle, combined and mediation physical lanes passed. Foundation reached
the new rehearsal and failed at its real D2 judge during fixture provisioning,
before any generated READ phase. Run:
https://github.com/sushiHex/constructicon/actions/runs/40411888474.

Source audit identified a concrete missing fixture precondition: the exact
ubuntu24/20261012.334 runner image's configure-system.sh makes /opt mode0777,
while the unchanged D2 judge requires root-only writable ancestors. The old
command wrapper omitted judge stdout, so the precise old failing conjunct is
not represented as a measured fact.

The narrow CI-only correction validates /opt ownership/canonical identity,
records its original mode, secures it for the genuine installers, and restores
it after cleanup. Failure diagnostics will retain bounded stdout as well as
stderr. The real judge remains unchanged. Another hosted run must establish
the actual outcome; no Linux chain success is claimed yet.

Connector review completed on d07e6ac with no findings. No repeat broad review
is requested for the unchanged operator code; the fixture delta receives a
focused independent check. The private VM remains parked and no model ran.

Separate the closed physical launch profile from vendor presence, retain strict probe predicates, and cover the actual assembly and refusals. Record the exposed production mismatch and fresh controller requirement.

Agent: codex:constructicon-wave
@sushiHex

Copy link
Copy Markdown
Owner Author

At head 0c0acc0, the actual generated-chain rehearsal has exposed and corrected a pre-existing production READ assembly mismatch. The prior run measured a contradictory containment probe before dispatch, with zero callbacks; it did not retain separate native/worker label observations. Source tracing showed that the vendor-free API worker used Claude's policy but selected the generic expected profile. Existing physical-provider tests injected a different generic worker.

The correction is a closed, revision-bound launch-profile selection independent of vendor identity. The worker remains vendor-free and networkless; physical probes still require one exact selected label and every existing containment predicate. No policy permissions, mounts, credentials, egress or protocol are changed. The READ materialization branch does not need Git execution in the bootstrap profile; the WRITE branch is outside this correction.

Focused API/recipe/read-worker/host-session tests and strict typing passed. All six new distinct profile mutants were killed by assertion failures, and inventory target/collection checks passed. Terra independently reviewed the profile boundary and compatibility delta with no confirmed blocker. This narrow review supplements the connector's initial d07e6ac review; that earlier review is not claimed to cover the new controller code.

The full verification/qualification/physical gates must now pass on 0c0acc0, including the actual generated accepting READ chain and abort withdrawal. No private-host retry occurred. Because controller source and identity changed, the old private controller candidate is invalidated; a newly reviewed exact installation and fresh qualification are required before a live attempt.

@sushiHex sushiHex changed the title Version and rehearse the actual Claude READ operator chain Rehearse Claude READ and bind its worker launch profile Oct 27, 2026
@sushiHex

Copy link
Copy Markdown
Owner Author

Final head 0c0acc0 is green. Full verification and mutation CI passed:
https://github.com/sushiHex/constructicon/actions/runs/40423295719
Runner qualification passed:
https://github.com/sushiHex/constructicon/actions/runs/40423295718
All four physical containment lanes passed:
https://github.com/sushiHex/constructicon/actions/runs/40423295892

The required generated-chain step executed both cases: the accepting path completed the actual fixed READ and generation-bound withdrawal; the injected post-activation refusal also completed generation-bound withdrawal. These are credential-free fake-vendor observations, not a private-host or subscription READ claim. No frozen plan bytes changed.

The final conversation/review/inline check found no unaddressed finding. Initial connector review and the recorded narrow independent fixture/profile reviews cover the delivered changes. Squash merging under the owner's authorization.

For later Windows execution, preparation must use a byte-exact Git source image for local qualification-source hashing; CRLF-translated working copies are not identical to the installed LF controller source. The comparison stays strict. The old private candidate remains invalidated; no private installation or model attempt has occurred in this work.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant