api-design-graphqllisted

# API Design GraphQL ## Scope Boundaries - Use when GraphQL schema boundaries, resolver contracts, and query safety must be defined. - Use proactively when GraphQL SDL/resolver diffs appear in specs, manifests, or source. - Use when clients need flexible field selection but query safety and authz boundaries are not yet explicit. - Do not use for REST-first endpoint design; use `api-design-rest`. - Do not use for storage internals; use `db-*`. ## Goal Deliver GraphQL contracts that are safe to evolve and efficient at runtime. ## Shared API Contract (Canonical) - Use `../api-design-rest/references/api-governance-contract.md` as the canonical contract. - Optional consistency checks (only if your repository enforces manifest validation): - `python3 ../api-design-rest/scripts/validate_api_contract.py --manifest <path/to/manifest.json>` - Use valid templates in `../api-design-rest/assets/`. - Use transport decision reference: - `../api-design-rest/references/transport-selection-matrix.md` - Use threshold derivation reference: - `../api-design-rest/references/threshold-derivation-framework.md` - Do not redefine API artifact ID formats, states, or approval gates. ## Implementation Templates - GraphQL SDL template: - `../api-design-rest/assets/graphql-schema-template.graphql` ## Inputs - Required queries/mutations and consumer usage patterns - Entity ownership and field-level authorization requirements - Performance budgets for depth, complexity, and resolver latency ##