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/applied.yaml

@@ -1,5 +1,3 @@
-id: /applied
-route: ^/applied
 followup: true
 name: What happens now that you've applied?
 description: >

questions/develop/index.yaml

@@ -1,5 +1,3 @@
-id: /develop
-route: ^/develop
 name: Development proposals
 qualifies: owners
 description: >

questions/develop/proposal.yaml

@@ -1,5 +1,6 @@
-id: /develop-proposal
-route: ^/develop-proposal
+# Nested for the flow, but a public entry point - without this it
+# would infer followup and drop out of the nav.
+followup: false
 name: How can this website improve?
 description: >
   This site is built on the same question architecture you're using
@@ -13,7 +14,7 @@ alternatives:
       a page under questions/, or aggregates.yaml — verbatim, so it
       has to be complete, valid YAML for that file, not a diff.
       Nothing outside those files is in scope.
-    action: /proposed
+    action: proposed
     consequence: [Propose it]
     record_as: development_proposals
     encouragements:

questions/develop/proposed.yaml

@@ -1,6 +1,6 @@
-id: /proposed
-route: ^/proposed
-followup: true
+# 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

questions/index.yaml

@@ -1,4 +1,3 @@
-id: /
 name: What are you here for?
 description: >
   Strategies that address problems — applied in software.

questions/project.yaml

@@ -1,5 +1,3 @@
-id: /project
-route: ^/project
 followup: true
 name: So, what happens now?
 description: >

questions/review/[record].yaml

@@ -0,0 +1,20 @@
+# Dynamic page: /review/<chain-hash> shows one development proposal,
+# addressed by its record key. The {record} placeholder receives the
+# URL segment; the section's qualifies (plus the resource's own
+# requires_group) keeps it owner-only.
+name: One proposal
+description: >
+  A single development proposal, addressed by its record key — link or
+  paste a chain hash from the desk.
+alternatives:
+  - name: Record
+    description: ""
+    features:
+      - name: ""
+        description: ""
+        resource:
+          source:
+            kind: kv
+            bucket: development_proposals
+          key: "{record}"
+          requires_group: owners

questions/review/_section.yaml

@@ -0,0 +1,3 @@
+# Everything under /review is the owners' area - one gate for the
+# whole directory instead of a qualifies flag per file.
+qualifies: owners

questions/review/index.yaml

@@ -1,7 +1,4 @@
-id: /review
-route: ^/review
 name: The review desk
-qualifies: owners
 description: >
   Sign in as an organizational owner to see what's come in.
 alternatives:

questions/subscribed.yaml

@@ -1,5 +1,3 @@
-id: /subscribed
-route: ^/subscribed
 followup: true
 name: What should you expect?
 description: >