README: the proposal loop as it now runs (draft PR on submission)
Lint and reload / lint (push) Successful in 3s
Lint and reload / reload (push) Successful in 0s

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
This commit is contained in:
Bendik Aagaard Lynghaug
2026-08-25 22:52:57 +02:00
co-authored by Claude Fable 5
parent 17112452b8
commit 717c8ee365
+12 -7
View File
@@ -133,13 +133,18 @@ entirely in this repo, in this order:
and its workflow must be updated in lockstep.
5. **Change the system through itself.** `/develop/proposal` takes a
proposed replacement for any content file (`questions/*.yaml` or
`aggregates.yaml` — nothing else is in scope) — from a person, or
eventually a locally-run model, through the same public form. An
owner approves it on `/develop`; approval triggers the automation
that branches, commits, opens a PR, and merges only when the same
lint that gates every human push passes. Nothing merges on
autopilot.
proposed replacement for any content file (the `questions/` tree,
`aggregates.yaml`, or `site.yaml` — nothing else is in scope) —
from a person, or eventually a locally-run model, through the same
public form. The submission itself becomes a branch and a draft
pull request at once (n8n "Portal: proposal received"), so lint
reports on it immediately and the submitter gets one
acknowledgement mail if they left an address. An owner approves it
on `/develop`; approval un-drafts the PR and merges it once the
same lint that gates every human push passes ("Portal: commit
approved development proposal"). Nothing merges on autopilot. The
alternative is `disabled: true` while this loop is being finished —
announced, not yet open.
## Voice