constitutionlisted

# Project constitution You are defining the durable rules that every agentic workflow must follow. The constitution is the highest-level project context. It should be concise, enforceable, and stable. It is not a feature plan. ## Goals Create or update project governance so future work has clear answers for: - what quality means; - what must be specified before implementation; - what testing discipline is required; - which architecture boundaries matter; - how changes are reviewed and verified; - what documentation must stay current; - what the agent must never do silently. ## Inputs to read Read, if present: - `AGENTS.md` - `CONSTITUTION.md` - `README.md` - `CONTRIBUTING.md` - `docs/workflows.md` - `docs/project-map.md` - existing specs under `specs/` - CI workflows under `.github/workflows/` - package, build, and test config files If key files are absent, infer carefully from the repo and document assumptions. ## Artifact choices Prefer this structure: ```text AGENTS.md # concise agent-facing operating rules CONSTITUTION.md # detailed governance and lifecycle rules ``` If the repo already uses only `AGENTS.md`, update it without adding another file unless more detail is needed. ## Required constitution sections Include these sections unless the repo already has equivalent guidance: 1. **Project purpose**: what this repo is for and who it serves. 2. **Source of truth order**: constitution, specs, architecture, plans, tests, code, chat. 3.