09 / DESIGN CHOICES

Choose the smallest integration
that preserves the owner’s work.

ApproachUseful propertiesTradeoff in this workflow
Curated events + existing native CLIReuses the board’s validation, locks, source mapping and guarded commits.Requires an authorized workstation and explicit evidence curation; it is not a universal chat scraper.
Existing authenticated application APICan suit an interactive owner session and avoids moving whole files.Session/CSRF and endpoint scope still apply. A cloud task does not automatically receive that session. Our producer uses the reviewed native route.
Event/webhook adapterCan reduce scheduled polling for a supported event source.Needs a real supported source and identity mapping. It cannot invent an event stream for inaccessible local task history.
Copy the whole workspace fileSimple to understand as a backup operation.Unsafe as reconciliation: an old snapshot can overwrite newer owner edits. Use bounded events and exact current guards instead.

The transferable principle is the separation of evidence, identity, conflict detection and execution. Systems Manager is our existing transport choice. The application’s data contract is what makes the update repeat-safe.

10 / TEACHING RESOURCES

Record the result first.

The source kit includes a six-scene storyboard, speaker notes and a transcript draft. Start with the synthetic simulator showing an exact-repeat no-op, then explain how the workstation and server achieve that result.

  1. Show the visible result.Apply the synthetic event, repeat the preview and point out zero additional writes.
  2. Explain the route.Follow the diagram from authorized task results to the workstation, AWS control plane, native application and private board.
  3. Expose the conflict.Select “Owner edited the task.” Show the refused update and explain how the owner’s edit survives.
  4. Inspect the matching code.Run the local Python example and tests, then point to stable identity, the event digest and version checks.
  5. Show recovery and evidence.Use the read-only original-command example; distinguish a delayed result from a safe retry. Explain that a Wall receipt does not complete a task.
  6. Finish with the resources.Show setup, readable source, compiled CSS, fixture boundaries, license and the next independent experiment.

Recording preparation, not a recorded video. The storyboard and transcript are source materials. No video, captions synchronized to a real recording, external upload or new account is claimed. Use only this synthetic page and local fixtures; do not record private board records, credentials or customer data.