Integrate verified State Hub dispatcher into lifecycle release

Assistant: codex
Assistant-Model: gpt-6-astra
Assistant-Session: 01a10780-6d41-7952-9718-dfbc1f41236f

docs/evidence/2026-10-04-lifecycle-release/dispatcher-container.json

@@ -0,0 +1,16 @@
+{
+  "status": "passed",
+  "image_id": "sha256:410fb6b6c9fd7a7ee0b63d727fd3249fb3ae13943421d6a5ce88b7ad2520bd2f",
+  "checks": [
+    "non-root read-only worker starts without external network",
+    "explicit enqueue persists a lifecycle envelope without inventing a Hub relationship",
+    "SIGTERM stops without forced kill",
+    "restart retains the exact pending envelope; missing custody does not drop it",
+    "private queue and database modes enforced"
+  ],
+  "fixture_only": true,
+  "external_network": "none",
+  "native_identity_proven": false,
+  "envelope_sha256": "ce0b8e1c6e861fde2da584363b695932bd0c74f923d1688211cc8b3d9a2f8c2e",
+  "cleanup_complete": true
+}

docs/evidence/2026-10-04-lifecycle-release/dispatcher-scan.json

@@ -0,0 +1,9 @@
+{
+  "image": "forgejo.coulomb.social/coulomb/state-hub-memo-dispatch@sha256:410fb6b6c9fd7a7ee0b63d727fd3249fb3ae13943421d6a5ce88b7ad2520bd2f",
+  "source_commit": "4a59b23",
+  "scanner": "Trivy 0.74.0",
+  "created_at": "2026-10-04T20:38:44.831801093Z",
+  "high": 0,
+  "critical": 0,
+  "scope": "Image vulnerabilities in the scanner database at scan time; not universal security attestation."
+}

docs/evidence/2026-10-04-lifecycle-release/manifest.json

@@ -3,11 +3,12 @@
   "status": "prepared-not-deployed",
   "server_dry_run": {
     "cluster": "railiance01",
-    "objects": 25,
+    "objects": 28,
     "passed": true
   },
   "sha256": {
     "deploy/lifecycle/admission.candidate.json": "e3054aebb2338146b912121198eba0232973574b9f045710abc802e524fe43f6",
+    "deploy/lifecycle/dispatcher.candidate.json": "e64bdaabfc307caf5f65894ce7e37fd66abaaf9328fd35cfd9103e14bbf739c8",
     "deploy/lifecycle/intake-submitters.json": "58ba5ef87ecfd40bc7f0eaf2beb5e50f0c1f0e47315e79dbfa9e06411a17eba9",
     "deploy/lifecycle/lifecycle-callers.json": "0b66382a64bdf81ee75d14a70ba3b19290084922a1e0bc8a873af0f039dc7041",
     "deploy/lifecycle/policy.candidate.yaml": "850d96aa7807b0e81e28278d380543770012a006b5dc3ebb06a5a8f5fcb43c4a",
@@ -15,5 +16,12 @@
     "deploy/lifecycle/review-groups.json": "1d61d2b82230981130936651a7fc4230e06ecaa51416a8a1be2bb2eb6ec4c353",
     "deploy/lifecycle/review-policy.candidate.yaml": "1f680eb1184c4a26ae2638b7e0829e5df42237ee09550e7554a3e965edbc8674",
     "deploy/lifecycle/service.candidate.json": "bf36ecb0160bf893a60fe059a3baf27a63668e2bb7b9f17c9582d6de8e842545"
+  },
+  "dispatcher_verification": {
+    "owner_tests_passed": 28,
+    "cross_service_tests_passed": 663,
+    "cross_service_tests_skipped": 1,
+    "installed_container_checks": 5,
+    "high_critical_findings": 0
   }
 }

docs/requester-workload-owner-review.md

@@ -86,3 +86,15 @@ No repeated design decision is needed for this accepted boundary. The remaining
 human action is separate founder approval of the final concrete live packet and
 named verification/abort attendance, after these technical gaps are closed.
 No live apply, credential read, rotation, issuer mutation or deployment occurred.
+
+
+## Runtime acceptance update — 2026-10-04
+
+The private listener, CA-verified TokenReview, rotating file-backed requester,
+attribute consumer and durable State Hub dispatch are now composed and tested.
+The service image remains the scanned 2768bd1 candidate in deploy/lifecycle;
+State Hub worker is the CI-built 410fb6b candidate. This closes the source/runtime
+composition gap only. The live CCR remains proposed; its current SHA256 is
+ab4cd7c15192ebe98e17b0c40a188ae67616c63cc796d9b807adba7c39f2edb3.
+No new design decision is requested. Exact live delivery approval, attended
+OpenBao login, native custody/rotation proof and cutover acceptance remain.

docs/specs/LifecycleProductionRuntime.md

@@ -56,11 +56,16 @@ live Approval Engine object, checks its binding pin, requester informed-decision
 and human_control=true before the PDP call. Store guards recheck retained intake
 metadata at the mutation boundary. A valid-looking UUID/digest alone is not proof.
 
-State Hub forwarding currently exists as a dev fixture, not a production worker.
-The selected identity still needs projected lifecycle/intake tokens and an owner
-runtime integration. State Hub notifications/write-back require admitted receiver
-routes; `INFD_HUB_WRITEBACK` stays off in this candidate. Pending rows remain
-explicit. These are live INFD-WP-0005 dependencies, not claimed release evidence.
+State Hub now has a private explicitly queued dispatcher (STATE-WP-0096), with a
+separate standard-library-only image and PVC. It uses the selected existing
+service account and distinct projected lifecycle/intake tokens; its transport
+reads only the intake token. The Hub public API does not gain a credentialed
+forwarding route. Queueing is trusted workload execution. New review envelopes
+are data operations and do not change deployments. The exact lifecycle snapshot
+id/key is preserved without inventing a Hub relationship when serves is absent.
+Lost replies replay the same envelope; native-create uncertainty blocks the row.
+Native deployment/acceptance still remains open. Notification/write-back receiver
+admission is unchanged; INFD_HUB_WRITEBACK remains off.
 
 The image migrates schema 2 to schema 5 on open. Existing records, presentations,
 dispositions, submissions and outbox evidence must survive. Rollback to the old
@@ -76,7 +81,8 @@ must be reconciled, never retried or discarded to make rollback convenient.
   evidence remain with RPF-WP-0051.
 - FLEX-WP-0033: publish scanned policy artifact; approve exact policy/RBAC/network
   objects and native caller/subject allow/refusal tests.
-- INFD-WP-0005: production State Hub forwarding/receiver and token projections.
+- INFD-WP-0005 / STATE-WP-0096: activate and verify the prepared private State Hub
+  dispatcher and its projected tokens; retain gated resolution write-back.
 - INFD-WP-0007-T06/T07: backup/restore, exact rollout approval, native human review
   and independent audit receipts across two decisions and a revision with unchanged
   release/configuration pins. Browser packet authoring and broader binding profiles