Bendik Aagaard LynghaugandClaude Fable 5
ad9dd1762b
develop/ holds the whole proposal flow (index = owners desk, proposal = public form, proposed = chain-gated receipt) with relative actions; review/ gains _section.yaml (one owners gate for the directory) and a [record].yaml dynamic page - /review/<chain-hash> shows a single proposal. Top-level files drop their now-derived id: and fossil route: fields. URLs /develop-proposal and /proposed become /develop/proposal and /develop/proposed (no automation references them - n8n filters checked). Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
25 lines
657 B
YAML
25 lines
657 B
YAML
name: Development proposals
|
|
qualifies: owners
|
|
description: >
|
|
Proposed changes to the questions repo, awaiting a decision.
|
|
Approval hands off to the automation that opens the pull request —
|
|
lint gates the merge, not this page.
|
|
alternatives:
|
|
- name: Proposals
|
|
description: ""
|
|
action: /develop
|
|
consequence: [Confirm]
|
|
features:
|
|
- name: ""
|
|
description: ""
|
|
resource:
|
|
source:
|
|
kind: kv
|
|
bucket: development_proposals
|
|
requires_group: owners
|
|
transitions:
|
|
- to: approved
|
|
label: Approve
|
|
- to: rejected
|
|
label: Reject
|