Decision and Governance Records
Use generic terminology and preserve the status of every material statement: observed fact, proposal, ratified decision, rejected decision, unresolved question, measured result, estimate, or causal claim.
Workflow
- Identify the decision question, scope, affected capabilities, authority, and required decision date.
- Record current evidence, constraints, assumptions, and unresolved questions.
- Compare feasible options using explicit criteria, risks, reversibility, and downstream effects.
- Name the decision owner, consulted parties, and the evidence required for ratification.
- Record status as proposed, ratified, rejected, superseded, or unresolved; never infer status.
- Document consequences, obligations, follow-up actions, review date, and supersession path.
- Link related decisions and explain conflicts or dependency order.
Boundaries
- Do not mark a proposal ratified without evidence from the named owner.
- Do not rewrite history when a decision changes; supersede it with traceability.
- Do not use a governance record as authorization for implementation, publication, or deployment.
Output
Return Decision question, Status, Context, Options, Evidence, Owner, Consequences, Follow-up, and Review triggers.
1---2name: decision-governance-records3description: Create or review decision records that preserve context, options, evidence, ownership, status, consequences, and review triggers. Use when a proposal must be distinguished from a ratified, rejected, superseded, or unresolved decision.4license: MIT5---67# Decision and Governance Records89Use generic terminology and preserve the status of every material statement: observed fact, proposal, ratified decision, rejected decision, unresolved question, measured result, estimate, or causal claim.1011## Workflow12131. Identify the decision question, scope, affected capabilities, authority, and required decision date.142. Record current evidence, constraints, assumptions, and unresolved questions.153. Compare feasible options using explicit criteria, risks, reversibility, and downstream effects.164. Name the decision owner, consulted parties, and the evidence required for ratification.175. Record status as proposed, ratified, rejected, superseded, or unresolved; never infer status.186. Document consequences, obligations, follow-up actions, review date, and supersession path.197. Link related decisions and explain conflicts or dependency order.2021## Boundaries2223- Do not mark a proposal ratified without evidence from the named owner.24- Do not rewrite history when a decision changes; supersede it with traceability.25- Do not use a governance record as authorization for implementation, publication, or deployment.2627## Output2829Return Decision question, Status, Context, Options, Evidence, Owner, Consequences, Follow-up, and Review triggers.30
JovaniPink