tegwick
f7f440dfff
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
45 lines
1.3 KiB
Markdown
45 lines
1.3 KiB
Markdown
# DEC-EX-005 — Production deploy rule
|
|
|
|
Situation: deployment policy.
|
|
|
|
This is the decision that adopts a reusable rule for later production deploys. `DEC-EX-004` is an exception to it. The rule text sits in one effect. There is no separate executable form.
|
|
|
|
```yaml
|
|
decision:
|
|
identity:
|
|
id: DEC-EX-005
|
|
title: Production deploy rule
|
|
namespace: decision-canon/examples
|
|
version: "1"
|
|
question:
|
|
text: What rule governs a production deploy from now on?
|
|
decision_class: policy
|
|
kind:
|
|
primary: policy
|
|
state:
|
|
lifecycle: effective
|
|
since: "2026-03-01"
|
|
commitment:
|
|
selected: Adopt the production deploy rule.
|
|
by: platform owner
|
|
at: "2026-03-01"
|
|
mode: decided
|
|
effects:
|
|
- id: e1
|
|
type: policy
|
|
target: production deploys
|
|
value: >
|
|
A production deploy names its rollback, comes from a reviewed change,
|
|
and runs only artifacts that passed malware scanning.
|
|
A deploy that cannot meet a clause needs an exception decision.
|
|
effective_when: on adoption
|
|
governance:
|
|
owner: platform owner
|
|
authority:
|
|
source: platform operating charter
|
|
scope: Production deploys of services this platform runs.
|
|
may: Set deploy rules for this platform.
|
|
metadata:
|
|
formality_level: D6
|
|
schema_version: "0.1"
|
|
```
|