prototype

For product/design forks, read Poteto.

Prove one named question, not an early production branch.

Choose cheapest faithful shape: logic/state executable model (LOGIC.md); UI several meaningful variants (UI.md); API/tool minimal sandbox/fixture call.

Use .context/prototypes/<question>/, or target-adjacent only when real runtime must load it; mark in-tree artifacts.

Retention

Keep runnable prototypes as primary sources; never merge prototype-only code to main.

• When the requested endpoint authorizes commits, use isolated prototype/<name> plus an issue/decision context pointer.
• Otherwise keep under .context/prototypes/<question>/, report path, and move/copy in-tree artifacts there before cleaning the ship diff. Do not delete.

Record the question, evidence, and verdict in an issue, ADR, implementation notes or commit. Main: only validated production decisions.

Constraints

Explicit interface workbenches: recommend variant (designs), state-machine (reachable states), or break (stress). Apply retention; user-only, never automatic dependencies.

1. Standard library/existing deps; no unrelated scaffolding.
2. One run command; scratch/in-memory persistence.
3. Show relevant state/observations.
4. Before trusting verdict, /dogfood once through decisive path and likely boundary, not every edit.
5. Apply retention after the answer.

If evidence contradicts the plan, revisit that decision before production.