ZYEL LAB / RECORDING PACKET
Show the callback.
Keep the proof.
By Chason Arthur · Project Lead
Teach one result: one synthetic task update, a harmless repeat and a preserved newer edit. The full original script contains SAY / SHOW / EXPECTED RESULT / PAUSE for each numbered shot.
Capture status: filenames below are planned until an accepted episode packet supplies matching actual-browser frames and hashes. A development packet must identify its exact code/shared foundation and state selectedStillApplied:false. Image-free development frames are not final selected-still media. No YouTube video or future upload is claimed. Never use a generated screenshot or collage.
Prepare a clean take
Use the loopback companion for the HTTP lesson. Confirm the visible mode, run the tests, reset the synthetic state and rehearse the holds. Use a dedicated window with no credentials, private chats or customer data. Set readable text before recording; leave the optional presentation gutter free for annotations.
Show the working result first. Put any short unchanged Zyel logo sting after the result. Keep speech clear and narration tied to the control by name. Quick cuts remove waits and repetitive typing while preserving setup, error and readback steps.
Use a native view for each shot
Presentation keeps the synthetic mode and Exit control visible. Choose Workflow for shots04/08/09, Identity extract for03, Result/readback extract for01/05/06/07, Architecture for10 and Reset for12. Shot02 stays in the ordinary overview;11 uses the tutorial. Extracts are selected fields from actual current data, never a recreated success state. Switching views preserves the exact fixture, batch, result and log; Escape exits with focus/scroll restored.
Numbered shot plan
- 01 — One change, then no-op ·
01-result-and-repeat.png - 02 — Name the fixture boundary ·
02-mode-and-boundaries.png - 03 — One task across device labels ·
03-stable-source-identity.png - 04 — Hold unreviewed metadata ·
04-privacy-validation-hold.png - 05 — Review before writing ·
05-immutable-preview.png - 06 — Preserve newer work ·
06-owner-edit-conflict.png - 07 — Confirm the committed result ·
07-current-readback.png - 08 — Server scope beats the button ·
08-reader-scope-hold.png - 09 — Keep completion evidence honest ·
09-completion-evidence-hold.png - 10 — Board authority and wall receipts ·
10-board-and-wall.png - 11 — Connect implementation to explanation ·
11-tutorial-contract.png - 12 — Reset safely and set an exercise ·
12-reset-confirmation.png
Before, after and failure
| Checkpoint | Before | Expected after |
|---|---|---|
| Apply | Known task/version | One reviewed change, one new version |
| Exact repeat | Committed source event | No change; original receipt |
| Owner conflict | Older prepared guards | Held; newer summary preserved |
| Reset Cancel | Current synthetic work | Same work retained |
Future video and transcript
No upload, OAuth or external tracking is part of this project. The script is transcript-ready source text; correct captions against actual narration and final timings. Attach a reviewed future video URL with an accessible transcript only after a real video exists. The page works fully without an embed.
Suggested chapter order follows the numbered shots. Replace planning order with actual edit timestamps. Never claim that a screenshot of a successful state proves every preceding interaction.
Production references
OBS: make a test recording · YouTube: captions · YouTube: chapters. Recommendations about quick cuts and a short logo sting are editorial choices to test, not guaranteed retention outcomes.