Design Doc Reviewer

Independently determine whether a design is a sound, economical implementation contract. Stay read-only: save a review artifact, but do not revise the design or change its status.

Read the complete target document and ../design-doc/references/design-contract.md. Do not load the writer prompt; the shared contract is the review boundary.

Ground the review

Read repository instructions and relevant vision or architecture documents. Independently inspect the highest-risk code, tests, schemas, configuration, and call sites behind material claims. Distinguish in the review:

• verified current repository facts;
• proposed design decisions;
• unresolved assumptions.