STATE-WP-0101-T01: record founder decisions 1-3 of 2026-11-01; decision 4 open

Relayed by the net-kingdom coordinator from the net-kingdom session:
pull through the dispatch worker, enforced TokenReview on the one
write-back route (auth-delegator grant founder-run), class floor moot
under GH-DEC-2026-026. Retirement disposition stays open, so T01 stays
in wait; T02/T03 proceed on decisions 1-3. Workplan set active.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

Assistant: claude-code
Assistant-Model: opus
Assistant-Process: 5502@bnt-lap001
Assistant-Session: 68b3b02f-5d0f-4e71-8421-796f62e50196

docs/decision-services-alignment-answer.md

@@ -4,8 +4,8 @@
 **Answers:** hub message 59390db6 (net-kingdom), proposal
 `net-kingdom/docs/proposals/2026-10-31-decision-services-alignment-review.md` (commit b764561),
 sections 3, 4.4, 5 (S3) and open question 6.4.
-**Status:** owner answer; design only. No API, schema or deployment change is made with this
-document. Implementation is proposed as `workplans/STATE-WP-0101-decision-evidence-links.md`.
+**Status:** owner answer; founder decisions 1-3 recorded 2026-11-01 (section 8.1), decision 4
+open. No API, schema or deployment change is made with this document. Implementation is proposed as `workplans/STATE-WP-0101-decision-evidence-links.md`.
 
 ## 1. Answer in short
 
@@ -96,8 +96,9 @@ attached. The vocabulary grows by owner change, not free form.
 | MCP `resolve_decision` | as today | gets the same 409 from the API | same |
 
 Who sets the class: the creator, at creation or later by raising it. Doctrine for which class a
-question needs comes from gate-house (S5). Until S5, the hub suggests a floor only for the existing
-financial/legal auto-escalation keywords (C1 minimum). Linking a decision to a task with
+question needs comes from gate-house (GH-DEC-2026-026, accepted 2026-11-01: C3 is reserved and is
+refused by the hub). The hub sets no keyword-based floor (section 8.1, decision 3); the existing
+financial/legal auto-escalation does not set a class. Linking a decision to a task with
 `needs_human: true` does not by itself raise the class.
 
 The existing review-contract gate keeps applying on both resolve routes.
@@ -208,6 +209,26 @@ against the cluster's service-account issuer JWKS.
 4. **Retirement disposition:** confirm the decisions capability is "keep, move to hub-core" so this
    work is not stranded.
 
+### 8.1 Founder answers (2026-11-01)
+
+Given by the founder on 2026-11-01 in the net-kingdom session and relayed by the net-kingdom
+coordinator; recorded here as relayed, not as C1 evidence.
+
+1. **Pull.** "The hub worker fetches outcomes": the existing STATE-WP-0096 dispatch worker reads
+   the outcome from informed-decision with its existing token and posts it to one new route that
+   accepts only the hub's own ServiceAccount, verified by TokenReview. informed-decision gets no
+   hub credential.
+2. **Accepted, implied by decision 1.** The pull option was presented as needing a cluster-level
+   `system:auth-delegator` grant for the API's ServiceAccount; accepting it accepts enforced token
+   checks on this one route ahead of STATE-WP-0100 phase 3. The grant itself is a founder-run live
+   step (railiance-cluster); nothing in this repository applies it.
+3. **Moot.** Gate-house doctrine GH-DEC-2026-026 (decision classes C0-C3, reliance as the C2
+   trigger, C3 reserved and not usable) was accepted by the founder the same day. The hub sets no
+   keyword-based class floor; classes are declared by the creator under that doctrine. The
+   existing financial/legal auto-escalation stays as it is and does not set a class.
+4. **Not decided; open.** The keep/move disposition of the decisions capability remains with the
+   founder. The implementation stays small and portable (section 6) so either answer is served.
+
 ## 9. Asks of other owners
 
 - **informed-decision:** an outcome read for a submitter's own memos returning the record in