pelizzai-prototype

Testing a design hypothesis with throwaway code requires a strict lifecycle of hypothesis definition, time-boxed implementation, and mandatory cleanup or absorption. This approach ensures experimental code resolves material uncertainties without persisting in production environments.

A software spike for feasibility validation is a throwaway code experiment designed to answer specific technical or integration questions. It operates under a falsifiable question contract to prove whether a proposed design works before committing to production development.

Setting up a time-boxed prototyping experiment involves defining a falsifiable question, establishing a strict timebox, and determining a clear destination for the resulting code. You must secure explicit approval to ensure the experiment safely tests integration feasibility.

You should use throwaway prototyping instead of building production code when you face material uncertainties in software design and integration. It prevents over-engineering by providing a structured, safe way to answer specific technical questions before committing to a final implementation.

To ensure experimental code does not end up in production, the prototyping process enforces safety guardrails requiring explicit user approval and a clear destination for the code. The code must either be deleted or formally absorbed after answering the falsifiable question.