# Codex Bridge Workshop — result-first episode script

By Chason Arthur · Project Lead

Working title: **Build a Guarded Codex Task Bridge: Preview, Apply and Prove the Callback**

Audience: JavaScript developers who understand JSON and basic HTTP. Outcome: reconcile one synthetic task, preserve newer work and prove an identical callback is a no-op. Tested runtime and final source/capture evidence belong in the episode packet. No Codex execution, production credential, private conversation or live task write is filmed.

Production status: This is a shoot script. A filename is a planned frame until a corresponding real-browser capture manifest exists. Timings are editorial estimates, not final YouTube chapters or measured retention advice. Every screenshot is a separate clean actual-browser frame; never combine them into a collage. Preserve the untouched PNG and place annotations on separate editable layers.

Native presentation views: Workflow controls for04/08/09; Identity extract for03; Result and readback extract for01/05/06/07; Board and wall architecture for10; Reset and recording notes for12. Shot02 uses the ordinary overview;11 uses the tutorial. Enter presentation from Recording tools, choose the named view, and keep the always-visible synthetic mode and Exit control in frame. Identity/result extracts are explicitly partial views of the original current data; complete JSON stays in ordinary mode. Changing view never resets, prepares or applies a batch. Escape exits and restores focus/scroll. These are shot plans until actual final-theme frames are captured.

Before recording: run the complete core/HTTP suite; open the loopback fixture in a dedicated browser profile with no private tabs or autofill; verify LOCAL HTTP FIXTURE; increase code/output text for a reduced-size player; turn off unrelated notifications. Reset the fixture explicitly, then rehearse every hold/recovery. Reuse the exact Zyel vector logo; no redraw or extended animated intro. Keep optional branding after the result and under roughly one second as an editorial choice. Record clean speech and listen to a short test.

## 01 — Prove the outcome first

Frame: `01-result-and-repeat.png` · demo `./#workspace`

**SAY:** “One callback changes the task. The same callback arrives again, and the task does not change twice. We can also prove what happened by reading the board back. That is the small result we are building.”

**SHOW:** Prepare, Validate, Preview, Apply, Read back, then Repeat identical preview. Hold on `would_change: false`, `changed: []`, and the single version increment. Record the whole verification in the master take; quick-cut only the waiting and repetitive cursor travel.

**EXPECTED RESULT:** One committed synthetic update; repeated exact event is a no-op. This is not a real Codex run or production task update.

**PAUSE / ANNOTATE:** Two seconds on the unchanged version and no-op result. Leave the right annotation gutter clear.

## 02 — Name the boundary

Frame: `02-mode-and-boundaries.png` · demo `./#main`

**SAY:** “I’m Chason. This is a synthetic bridge. We will use a real local HTTP boundary, but no private chats, real credentials or cloud calls. The device name is a label. It does not authenticate a person.”

**SHOW:** The mode label, synthetic boundary and tutorial setup. Optional short unchanged Zyel logo sting after this clear promise, then straight back to the working page.

**EXPECTED RESULT:** The viewer sees LOCAL HTTP FIXTURE. If the mode is BROWSER FIXTURE, state that clearly and do not claim the server checks were exercised in that take.

**PAUSE / ANNOTATE:** One beat on the mode and public dummy scope note.

## 03 — Keep one task across device labels

Frame: `03-stable-source-identity.png` · demo `./#workspace`

**SAY:** “The work keeps one source-task identity. Thread and message IDs tell us where this report came from. Changing the device label should not create a second board task. We resolve the existing mapping before we propose a write.”

**SHOW:** Reset, Prepare, open exact batch. Highlight source task, thread/message and board task. Change to Demo desktop, prepare again, compare the same source/board mapping and different provenance. Do not hide the Prepare step.

**EXPECTED RESULT:** One known board task remains; device label and thread provenance change, not authority.

**PAUSE / ANNOTATE:** Hold the JSON long enough to read the four identity fields.

## 04 — Reject the wrong payload early

Frame: `04-privacy-validation-hold.png` · demo `./#workspace`

**SAY:** “A callback is not permission to send a conversation. This contract accepts short reviewed work metadata. The declaration is required, and it is still a human review responsibility. A simple pattern check cannot prove a summary is safe.”

**SHOW:** Uncheck privacy review, Prepare and Validate. Show `privacy_hold` and unchanged board revision. Re-enable the declaration and prepare a fresh valid batch.

**EXPECTED RESULT:** An explicit hold with no write. Unknown fields and oversized requests are also refused in the tests.

**PAUSE / ANNOTATE:** Keep the error and current revision together; do not quick-cut away the failed check.

## 05 — Review an immutable preview

Frame: `05-immutable-preview.png` · demo `./#workspace`

**SAY:** “Preview binds the exact batch to the board hash and versions we inspected. It shows the proposed change without making it. The hash detects a mismatch; it does not replace authorization or a human review.”

**SHOW:** Validate and Preview. Read requested/version1 to in_progress/version2. Show the current board still at version1. Briefly cut to the tutorial’s canonical digest explanation, then back to the same state.

**EXPECTED RESULT:** A plan ID exists and the board is unchanged. Editing the draft invalidates its current preview.

**PAUSE / ANNOTATE:** Hold before/after versions and current task version.

## 06 — Preserve a newer owner edit

Frame: `06-owner-edit-conflict.png` · demo `./#workspace`

**SAY:** “Now someone else edits the task. Our old preview is stale. The right response is to stop, read the newer work and prepare another reviewed change. We do not erase the owner edit to make our request pass.”

**SHOW:** Simulate a newer owner edit, then Apply the older plan. Show the conflict and preserved summary. Inspect and refresh guards. Read the newer summary before preparing a new source message and preview.

**EXPECTED RESULT:** `workspace_conflict`; no stale write. Recovery is a fresh inspection and review, not blind retry.

**PAUSE / ANNOTATE:** Leave the preserved owner summary readable beside the conflict.

## 07 — Apply and read back the actual result

Frame: `07-current-readback.png` · demo `./#workspace`

**SAY:** “Apply uses the exact reviewed plan. Then readback confirms the task and receipt. If a response is lost, a timeout cannot tell us whether the server committed. Aborting the request does not cancel the task or stop an executor. Preserve the event and inspect it before sending another write.”

**SHOW:** Use a valid fresh batch, Preview, Apply, Read back. Repeat the exact preview. Point to the event receipt, current board and minimal event log. Do not imply a log alone proves deployment.

**EXPECTED RESULT:** One commit and an exact-repeat no-op. The fixture retains only small in-memory event codes, not the summary or dummy bearer values.

**PAUSE / ANNOTATE:** Explain uncertainty as a separate state; do not fabricate a timeout screenshot if that scenario was not actually exercised.

## 08 — Let the server enforce scope

Frame: `08-reader-scope-hold.png` · demo `./#workspace`

**SAY:** “The button is not the permission boundary. A reader can inspect, but the server refuses a write. These are public dummy bearer values for the lesson, not a production login design.”

**SHOW:** Select Reader, prepare a fresh batch and Preview. Show forbidden and unchanged task state. Restore Producer for the next step.

**EXPECTED RESULT:** Server-side403 in local HTTP mode; the browser-only model simulates the equivalent hold.

**PAUSE / ANNOTATE:** Keep the actual mode label qualified in the episode packet.

## 09 — Keep completion evidence separate

Frame: `09-completion-evidence-hold.png` · demo `./#workspace`

**SAY:** “A callback can report progress. It cannot declare a deployment that never happened. This fixture has local review evidence only, so a deployment or whole-task completion claim stays held.”

**SHOW:** Choose a new message and Deployed verified or Done. Prepare and Preview. Hold on deployment_hold and the open task.

**EXPECTED RESULT:** No trusted live deployment evidence, no deployed/done change.

**PAUSE / ANNOTATE:** Separate the requested phase from authoritative current status.

## 10 — Explain board and wall authority

Frame: `10-board-and-wall.png` · demo `./#architecture`

**SAY:** “The board owns task status. The wall reads it and adds separate artifact receipts. An authorized scheduled reconciliation can inspect accessible work, but it does not gain access to every private conversation. Missing sources remain visible holds.”

**SHOW:** The four-stage architecture. Point to source, guarded adapter, native board and wall. Mention the inspected owner system as a pattern, never display its private records or infrastructure.

**EXPECTED RESULT:** Clear authority and permission boundaries. No claim that a future scheduled run already happened.

**PAUSE / ANNOTATE:** One clean diagram, no collage or private screenshot.

## 11 — Show the code and verification path

Frame: `11-tutorial-contract.png` · tutorial `./tutorial.html#step-4`

**SAY:** “The tutorial pairs each decision with code, alternatives, a pitfall and a test. The companion uses no runtime npm packages. A real service adds durable transactions, approved identity and recovery; this Map is not a production database.”

**SHOW:** The immutable preview explanation and safe copyable snippet. Cut to the verified test output only if it has been captured from this exact source; otherwise link the evidence instead of inventing a terminal frame. Keep code readable at small player size.

**EXPECTED RESULT:** Prerequisites and complete source/test commands are discoverable. Excerpts labeled conceptual are not sold as turnkey code.

**PAUSE / ANNOTATE:** Pause on the decision and its verification, not every keystroke.

## 12 — Reset, then set one exercise

Frame: `12-reset-confirmation.png` · demo `./#recording`

**SAY:** “Reset clears this synthetic workspace only. For practice, add a second task and prove a wrong mapping is held, a repeated event is harmless and a newer edit survives. Keep the test result attached to the exact source you reviewed.”

**SHOW:** Open Reset dialog; first Cancel and prove current work remains. Then reset deliberately and show revision1. Keep the actual confirmation in the full take. Finish with the tutorial and source links.

**EXPECTED RESULT:** Cancel preserves state; confirmed reset creates a clean fixture. Site appearance and real owner records are untouched.

**PAUSE / ANNOTATE:** Leave the final result visible, then end. No subscription request before the lesson delivers its promise.

## Edit and publication checklist

Quick cuts remove dead time and repeated cursor travel, not prerequisites, failures or proof. Match every PNG to its exact shot and captured/tested status in the packet. Keep separate master frames and annotation layers. Use corrected captions for Codex, JSON, idempotency and identifiers. Final chapters start00:00 and use actual edited timings, not this planning order. Include tested versions, source links, setup, reset, limitations and a transcript. No video URL exists until an actual approved upload is attached. Watch the final export completely at normal and small player sizes before publication.


Authority producer note: the inspected owner bridge now has a separately guarded native cancellation transition requiring fresh verified human-owner intent, mapped identity and current conflict guards. This exercise does not implement it and no real cancellation is filmed. Reactivation requires a separate explicit instruction; future scheduled dispatch remains unverified. Do not display private source records, infrastructure or actual owner/task/thread IDs.


Current-source development capture contract: use the accepted shared foundation and literal source-development module namespace. Record the exact code commit, shared dependency, actual browser/runtime and each frame hash. Set selectedStillApplied:false and image-free-foundation on the packet; do not label those frames final selected-still media. Each cut may start a fresh isolated synthetic fixture; state transitions shown within a cut must be actually performed and verified. Keep reset/scene boundaries visible in an edited video rather than implying an uninterrupted session. Final Library delivery/publication remains a separate gate.