development-spec-suitelisted

# Adaptive Development Specification Suite Select the smallest evidence-backed pack; delegate content to specialists. ## Token-efficient loading Inspect evidence, then load only the triggered reference: - context/profile/overlay selection → [context-resolution.md](references/context-resolution.md) - artifact activation/ownership → [document-map.md](references/document-map.md) - requirement IDs/tasks/evidence or pack audit → [requirements-traceability.md](references/requirements-traceability.md) - geography, sector, personal data, AI, commerce, or transfers → [jurisdiction-overlays.md](references/jurisdiction-overlays.md) - suite maintenance/release status only → [implementation-tasks.md](references/implementation-tasks.md) Never load `assets/templates/*`, the source ledger, or maintenance backlog to answer a bounded planning question. Use scripts for deterministic selection and validation rather than reproducing their rules in the prompt. ## Operating contract - Treat repository code, migrations, OpenAPI, infrastructure, design tokens, runtime configuration, and executed checks as stronger implementation evidence than stale prose. - Label every statement as `Observed`, `Decision`, `Assumption`, `Proposal`, `Unknown`, or `Evidence`; never turn an assumption into a fact. - Write artifact content in English unless the repository has an explicit content-language convention. Conversation stays Indonesian; Indonesian product content uses Bahasa Indonesia, not Malay, with tec