New Proposal (Stakeholders)
Create a proposal directory under proposals/ and submit it for review.
Checklist
This is intentionally manual: copy templates, answer the Q/A, and submit for review.
Focus: list the affected obligations/controls and state the expected impact on PASS/FAIL/UNDETERMINED.
- Create folder
proposals/SCP-YYYY-NNN-slug/ - Copy the appropriate template files (
proposal.yamlandevidence_refs.yaml) - Fill required fields:
scp_id,proposer,affected_controls,claim - submit as an SCP package (outside of this repo)
Q/A Session (your inputs)
- Q: What is the
scp_id? A: PickSCP-YYYY-NNN-slug. - Q: Who is the proposer? A: Fill
proposer. - Q: Which obligations/controls are affected? A: Fill
affected_controls. - Q: What is your claim? A: Fill
claimwith a single testable sentence. - Q: How does this change PASS/FAIL/UNDETERMINED? A: Fill
expected_impact. - Q: What evidence supports this? A: Add items to
evidence_refs.yamlusing bundle paths when possible.
Copy/Paste Package (output)
Use this as your starting point. The source-of-truth repo templates live under docs/dao/templates/.
Folder tree
proposals/
SCP-YYYY-NNN-<slug>/
proposal.yaml
evidence_refs.yaml
proposal.yaml
schema_version: "1.0"
# Required
scp_id: "SCP-YYYY-NNN-<slug>"
proposer:
name: "<name>"
organization: "<org>"
contact: "<email or handle>"
affected_controls:
- "<obligation/control reference>"
claim: |
<One clear sentence: what should change?>
# Stakeholder-specific: call out expected PASS/FAIL/UNDETERMINED impact.
expected_impact:
pass_fail_undetermined: "UNDETERMINED" # PASS | FAIL | UNDETERMINED
rationale: |
<Why this changes the outcome and under which conditions>
acceptance_criteria:
- "<Objective, testable criterion>"
bundle_paths_reviewed:
- "site/index.html"
- "regulation/links.html"
notes: |
<Optional: additional context>
evidence_refs.yaml
schema_version: "1.0"
# Required
scp_id: "SCP-YYYY-NNN-<slug>"
evidence:
- id: "E1"
kind: "bundle_path" # bundle_path | repo_path | external
ref: "<e.g. site/dao_stakeholders/index.html>"
sha256: "" # Optional: use when you are referencing a specific file version
note: "<Why this evidence matters>"
Related Views
- DAO (Developers)
- Task view — what “done” means
- Agentic view — roles, deterministic run contract, inspection invariants
- Digital twin view — change triggers and rerun rules