Prototyping turns a vague idea into an initial working artifact through rapid, iterative exploration. AI-generated code can make this fast, but a working interface is not evidence that its implementation is maintainable, efficient, or safe to ship. section 1.3
Keep the prototype simple and plan to discard it. Its value is the knowledge it exposes: business rules, edge cases, data shapes, and checks that can guide the final implementation. Turn those discoveries into an executable specification, then implement, verify, refactor, and take ownership of the production code. section 1.5 section 1.8
A 30-day refund policy
A refund prototype can expose questions about time boundaries, money arithmetic, partial refunds, and rejection reasons. An executable specification can then check an eligible refund, an expired request, and a partial refund that exceeds the remaining balance. section 1.5
Feature: Refund policy
Rule: Time-bounded, single-order refunds
Example: Within 30 days is allowed
Given an order "O1" purchased at 2025-08-01T10:00:00Z
When a refund of 25.00 USD is requested at 2025-08-28T09:59:00Z
Then the refund is approved and remaining refundable equals 75.00 USD
Example: After 30 days is rejected
Given an order "O2" purchased at 2025-08-01T10:00:00Z
When a refund is requested at 2025-08-31T10:00:01Z
Then the request is rejected with reason "expired"
Example: Partials must not exceed the original
Given prior refunds of 90.00 USD on a 100.00 USD order
When a refund of 20.00 USD is requested
Then the request is rejected with reason "exceeds-remaining"These refund scenarios turn discovered rules into concrete, checkable behavior. section 1.5










