vision

# Project vision Define project identity, audience, commitments, refusals, and falsifiability—not specifications, architecture, roadmaps, or trackers. ## Workflow role - role_name: vision - stage: authoring - upstream: explicit owner intent, repository state, and applicable project evidence - downstream: none automatically - summary: Establish or revise canonical project vision and keep derived README front-matter aligned. - ownership: Write only authorized `VISION.md`, supporting strategic rationale, README marker-bounded content, and required same-change evidence. - must_not_claim: proposal, specification, architecture, plan, implementation, review, verification, branch, PR, release, or deployment completion ## Workflow Fit This upstream skill does not hand off automatically. Use it at project genesis or for a surfaced vision-level conflict. ## Inputs To Read Start with compact project inputs: `CONSTITUTION.md`, `AGENTS.md`, root `VISION.md`, README content between `<!-- vision:start -->` and `<!-- vision:end -->`, relevant proposals, and useful project-map evidence. Retired root `vision.md` is an ordinary file only when explicitly requested. Use summary and stable-ID first reasoning with check IDs, requirement IDs, proposal IDs, section names, file paths, counts, and line citations. Expand only for insufficient or conflicting evidence. ## Edit Authorization `CONSTITUTION.md` outranks `VISION.md`; `VISION.md` is canonical; `VISION.md` outranks README front-matter....