API Design REST

Scope Boundaries

• Use when REST resources, URI structures, and HTTP behavior are being designed or changed.
• Use proactively when route, method, status, or schema diffs appear in specs, manifests, or source.
• Use when request-response transport options are being compared and REST is a candidate.
• Do not use for GraphQL-first schema work; use api-design-graphql.
• Do not use for storage internals; use db-*.

Goal

Deliver REST contracts that are stable, predictable, and operationally safe.