Breadboarding

Breadboarding maps what a user can do and how the system produces the result. The canonical output is the four tables below. Mermaid is optional and must be derived from the tables; it never overrides them.

Read references/extended-guide.md for whiteboard translation, subplaces, chunking, Mermaid styling, slicing diagrams, and full worked examples. The schema and validation rules in this entrypoint are authoritative.

Choose the mode

• Map an existing system: start from a user or caller workflow, then inspect the repository. Every code affordance and wire must have evidence in code.
• Design from shaped parts: start from the required outcome and mechanisms. Add only affordances needed to make those mechanisms concrete.
• Mixed: preserve evidenced existing behavior and label proposed affordances in Notes, while showing both in one end-to-end breadboard.