proposal

# Change proposal Turn a problem or selected direction into a reviewable decision: why this change, why now, and why this approach, without requirements or implementation tasks. ## Workflow role - role_name: proposal - stage: authoring - upstream: user request, exploration, research, issue, or incident - downstream: proposal-review - summary: Author the proposal artifact recording problem, options, recommendation, scope, risks, and readiness. - must_not_claim: proposal-review approval, spec readiness, implementation readiness, verification, branch readiness, or PR readiness. ## Project-local evidence Public skills use customer-project mode by default and project-local artifacts when present, including `docs/workflows.md` for local routing or placement. Do not require RigorLoop repository-internal artifacts in customer projects; use portable defaults or block on ambiguity. ## Evidence access Default evidence: - user request - `VISION.md` when proposal fit matters - `CONSTITUTION.md` for governance, source-of-truth, workflow, or release-policy changes - related proposal only when superseding or extending it Conditional evidence: - `AGENTS.md` when present - `docs/project-map.md` when architecture or repository orientation matters - existing specs or ADRs when the proposal changes their direction - `docs/workflows.md` when artifact placement or workflow routing matters - code only when current behavior is part of the decision - exploration, research, issues, incidents,...