# Implementation

Keep an accepted-decision ledger for interfaces, data boundaries, validation, and ownership choices
that could otherwise be lost during coding. Start from a failing behavioral test when practical and
complete the real path rather than adding placeholders or compatibility shims without a requirement.

When behavior changes, update the public contract, documentation, fixtures, and generated artifacts
that describe it. Keep local commands, branch policy, and release mechanics in the consumer wrapper.