Code ownership means taking responsibility for the quality and maintenance of code, including understanding it well enough to verify and change it. AI can produce an implementation, but it cannot take responsibility for deciding whether that implementation is acceptable for the system and its users. section 1.0 section 1.6
A fast handoff can leave that responsibility unclaimed. When an author submits generated code without reading the diff and assumes a reviewer will catch problems, verification moves downstream to someone with less context. Shipping without verification creates trust debt: a future maintainer must reconstruct understanding, often under pressure. Green tests alone do not establish that the code respects the right invariants. section 1.4
Keep ownership through the development loop:
- Explore the problem, then state intent and constraints in an executable specification before implementation. section 1.5 section 1.8
- Approve the plan and audit the generated code and verification artifacts; decide which proposed contracts are actually true. section 1.5
- Verify before merging. Use mechanical checks, but also judge whether the result matches the business intent and protects important invariants. section 1.8 section 1.4
- Own the tradeoffs after verification. An improved benchmark does not establish that unmeasured behavior remains acceptable. section 1.6
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"A refund-policy specification makes ownership concrete: someone must decide whether the time limit, rejection reasons, and partial-refund rules express the intended policy before using them to verify an implementation. section 1.5
The goal is not to write every line by hand. It is to retain a mental model and a clear decision about correctness as work moves from exploration to tested, team-owned code. section 1.0 section 1.8


