LAB

ZYEL LAB / CODEX BRIDGE WORKSHOP

Keep the task.
Verify the callback.

Two device labels. One stable task identity. Inspect the board, preview a small change, apply the exact reviewed batch, then prove a repeated callback does nothing.

Project Lead and tutorial: Chason Arthur

01 / GUARDED RECONCILIATION

A small change you can inspect.

  1. Inspect
  2. Validate
  3. Preview
  4. Apply
  5. Read back

Interactive controls load when the fixture is ready. If loading does not finish, reload this page or read the tutorial.

Curated callback

The form creates work metadata, not a transcript. Unknown fields and unreviewed content are held.

Use 1–60 ASCII letters, numbers, underscores, periods, colons or hyphens, starting with a letter or number. Keep the same message for an identical retry. Use a new reviewed message for new content.

Exact prepared batch
No batch prepared.

Apply changes this fixture only. A local review receipt cannot prove deployment or whole-task completion.

Identity extract

Only these identity and guard fields from the actual prepared batch are shown. The complete JSON stays available in normal view.

Prepare a batch to inspect its identity fields.

Board authority

Board revision
—
Task version
—
Task phase
—

Stable source task
demo:bridge-workshop

Last preview or receipt

Result extract

Selected fields from the actual last result. Full JSON is available in normal view.

No result yet.
Nothing applied.

Minimal event log

Twenty in-memory event codes at most. No summary, raw input, token or conversation is logged.

[]

02 / ONE AUTHORITY, EXPLICIT PRODUCERS

The wall reads the board.

  1. 1. Authorized sourceAccessible task results, reviewed by a producer. Missing access stays a visible hold.
  2. 2. Guarded adapterValidate, immutable preview, bounded apply and exact readback.
  3. 3. Native task boardStable mapping, version checks and task authority.
  4. 4. Progress wallShows board status with separate artifact receipts and verification scope.

The configured owner system uses this pattern through an already authorized private producer route. It has no generic Codex conversation discovery API, no public task-writing callback and no automatic access to every device’s private chats.

Distinguish local Codex APIs from the generic teaching contract

03 / RECORD A REAL CHECKPOINT

Show the change. Keep the failure.

Reset affects only the synthetic fixture and discards its in-memory batch and receipts. No owner board or saved site appearance is changed. Reload clears the browser-only fixture. In local HTTP mode the companion keeps its board until an explicit reset or server restart; reloading discards the page draft and requires a new inspection.

Full result-first script
Speaker notes

Show one accepted change, then the exact repeat. Next simulate the owner edit and hold the stale batch. Say “synthetic” aloud. Keep the error and recovery visible; do not cut around the verification.

Future video: no video has been uploaded or attached. The recording guide includes a transcript-ready script and chapter plan.

Working in this page

Stable task mapping, format/privacy gates, immutable preview, task/board conflicts, exact-repeat no-op, bounded logs and synthetic evidence holds.

Local HTTP companion

The supplied Node server crosses a real loopback HTTP boundary with public dummy bearer scopes, body limits and timeouts. It remains an in-memory fixture.

Run the local project

Unproven here

Production identity, durable multi-process transactions, real Codex execution, private conversation synchronization, live deploy evidence and a future scheduled run.

Reset the synthetic workspace?

Discard this fixture’s batch, preview, receipts and event log. The real board and site preferences are untouched.