docs task/episode-06-todo-domain-readme #1 / 1
AI Agent gabriel · 1 day ago · Sep 20, 2026 · Diff

docs: add episode-06 README explaining the todo domain's six-method mapping

Documents how muse/plugins/todo/plugin.py's snapshot/diff/merge/drift/ apply/schema implementation maps the core VCS protocol onto a flat, content-addressed task list, plus the Git contrast (line-based merge vs content-addressed set merge) the episode is built around.

Also notes the production-pipeline fact that prompted this: todo (Episode 06) and chess (Episode 22's finale) both landed in the muse repo on 2026-09-12, nearly a week before Episode 04 was recorded -- scripts and demo code for the whole season get built well ahead of the recording schedule, not in episode order.

Co-Authored-By: Claude Sonnet 5 <[email protected]>

sha256:0a866fdf54f95af946aeb565e9f6860bd28c6afde119abb99a34fd0ee6ddb039 sha
+6 symbols
1 changed · 70 in snapshot files
sha256:2bbb2f5eea8adce637ae3b68dd3c144c1672e473ee07f730ed7dc5cc862ca0ae snapshot
+6
symbols added
1
file changed
70
files in snapshot
0
dead code introduced
Semantic Changes 6 symbols
~ episode-06/README.md .md 6 symbols added
+ Episode 06 --- Demo Assets section Episode 06 --- Demo Assets L1–67
+ How the six-method protocol maps onto it method section How the six-method protocol maps onto it L36–46
+ Production note: this already existed before Episode 04 was recorded section Production note: this already existed before Episode 04 was recorded L8–20
+ The contrast with Git this episode is built around section The contrast with Git this episode is built around L47–55
+ The todo domain --- one file, one task per line, content-addressed section The todo domain --- one file, one task per line, content-addressed L21–35
+ sh --- fully scripted, run it directly section make-todo-episode06-demo.sh --- fully scripted, run it directly L56–67
Files Changed
+1
70 in snapshot
← Older Oldest on task/episode-06-todo-domain-readme
All commits
Newer → Latest on task/episode-06-todo-domain-readme

0 comments

No comments yet. Be the first to start the discussion.

To add a comment, use the Muse CLI: muse hub commit comment sha256:0a866fdf54f95af946aeb565e9f6860bd28c6afde119abb99a34fd0ee6ddb039 --body "your comment"