Add six illustrative decisions and the pressure note, and open DECISION-WP-0003 for the kernel proposal. Assistant: grok Assistant-Session: 01a1082a-858c-7fe2-9b5a-0b5332107eb3 |
||
|---|---|---|
| .. | ||
| DEC-EX-001-database-choice.md | ||
| DEC-EX-002-schema-ownership.md | ||
| DEC-EX-003-incident-rollback.md | ||
| DEC-EX-004-scanning-exception.md | ||
| DEC-EX-005-deploy-policy.md | ||
| DEC-EX-006-binding-policy-rule.md | ||
| README.md | ||
Examples
Illustrative fixtures for probing DecisionObjectSchemaDraft.md. They are not records of operational decisions.
File shape
One Markdown file per decision. The decision is a single YAML block. Populate only the sections the situation needs. Leave unknown fields absent. Do not add a JSON Schema.
The decision's identity id has the form DEC-EX-NNN. That id is an example identity. It is not a State Hub work-record id.
DEC-EX-001 uses the D1 shape from UnifiedDecisionObject.md: question, choice, and reason. It does not repeat the id inside the YAML, because that shape has no identity section. The other five examples use schema-draft sections only, and they carry identity.id.
Situations in DECISION-WP-0002
| Id | Situation | File |
|---|---|---|
DEC-EX-001 |
Trivial engineering choice | DEC-EX-001-database-choice.md |
DEC-EX-002 |
Architecture decision | DEC-EX-002-schema-ownership.md |
DEC-EX-003 |
Incident-response decision | DEC-EX-003-incident-rollback.md |
DEC-EX-004 |
Security exception | DEC-EX-004-scanning-exception.md |
DEC-EX-005 |
Deployment policy | DEC-EX-005-deploy-policy.md |
DEC-EX-006 |
Constitutional governance rule | DEC-EX-006-binding-policy-rule.md |
Hiring, procurement, investment, budget allocation, and public-style policy are not in this set. They stay deferred in DECISION-WP-0003 until a kernel proposal says whether more situations would show something these six did not.