gormes-prototype-spike

A disposable prototype is a throwaway code experiment used to evaluate UI, TUI, protocol, or state-machine design variants quickly before committing to a production implementation.

Create your throwaway prototype under a clearly named scratch path such as tmp/ or artifacts/, run it to iterate on design decisions, and enforce a single-prototype workflow per iteration.

Yes, this approach requires no persistent state by default and uses clearly named scratch paths for artifacts, ensuring your TUI and protocol design explorations remain isolated.

The best way is using rapid, disposable prototyping that enforces a single-prototype workflow per iteration, allowing you to test multiple runtime workflow variants without persistent state overhead.

You should avoid using disposable prototypes when your design exploration requires persistent state beyond the prototype phase, as this method is strictly for quick, throwaway design evaluations.

No, you do not need persistent state to test protocol or UI design variants; the default workflow uses scratch paths for artifacts and requires no persistent state by default.