Mission
Make the model obvious.
Understand Kitchen’s model for project storage, sync, solo work, and collaboration — well enough to use it, without importing git or cloud-IDE assumptions.
If you still think in clone, commit, and pull request, we have not done the job. If you save in your editor and expect history to already exist, we have.
You can do this when you can
- Explain storage (rows + versions), sync (live), work (mirror + any editor), and collaboration (three modes) in plain language
- Trace a solo save: editor → mirror → versions.insert → peer mirror
- Trace a pair session: Collab agent → relay → checkpoint → version
- Distinguish live sync from live collab without hesitation
- Use the product’s words: User, Org, Project, Owner, Manager, Version, Mirror
Three modes of work
Solo sync is the default. Fork + merge when two people save without pairing. Live pair is later.
Solo live sync
You alone, saving normally
Save → version insert → mirror on other devices
Async concurrent
Two people save without pairing
Two version heads → fork → Pierre Merge
Live collab
Pair programming
Collab agent + relay → checkpoint → version
How we teach it
- Learn the model before the schema. Vision first, then the running app.
- Voice and chat stay outside Kitchen. Kitchen syncs file bytes.
- Web is review. Editing happens on disk through the Mirror.
Start with the vision, then the product.