The tree is the router: nest the develop flow, section-gate review

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>

questions/develop/proposed.yaml

@@ -0,0 +1,18 @@
+# Reached from the proposal form only - and provably so: the visitor
+# must hold a ?chain= lineage ending at an answer to proposal.yaml.
+requires_chain: proposal
+name: Proposal received
+description: >
+  It's in the queue. An owner reads every proposal in full — approved
+  ones open a real pull request, and the same checks every human
+  commit passes gate the merge.
+alternatives:
+  - name: The path from here
+    description: ""
+    features:
+      - name: A person decides
+        description: Nothing merges on autopilot — approval is a deliberate act.
+      - name: The linter has no favorites
+        description: >
+          Approved or not, your YAML faces the same validation as
+          everything else in the repo.