Prepare Vergabe two-user acceptance and record recovery gaps

Assistant: codex
Assistant-Model: gpt-6.1-sol
Assistant-Session: 01a1abf1-7e95-7141-87c9-ee78332bf790

workplans/RAPPS-WP-0014-vergabe-invited-pilot.md

@@ -9,7 +9,7 @@ flavor: implementation
 owner: the-custodian
 topic_slug: railiance
 created: "2026-09-11"
-updated: "2026-10-21"
+updated: "2026-11-05"
 related: [VERGABE-WP-0019, VERGABE-WP-0018, HFACT-WP-0001, CUST-WP-0071]
 state_hub_workstream_id: "c7fdaa7e-cab8-5d1d-86c2-f1aad7927c57"
 ---
@@ -247,6 +247,19 @@ all remaining work; no task or workplan was opened.
 
 2026-10-03: human gate routed to hub decision d06307e5-2737-461a-a2f4-a12c3b492a9a (D7: Vergabe pilot: two real users run the invited setup-to-workflow acceptance) by CUST-WP-0075; resolving that decision raises C-40 here.
 
+2026-11-05 continuation: read-only preflight confirms the recorded Railiance01
+cluster UID, public health and NetKingdom welcome gating. Node, Deployment and
+PVC reads are forbidden to the current agent identity; no fresh native release
+or claim readiness is asserted. Receipt:
+`docs/evidence/2026-11-05-vergabe-pilot-preflight.json`. Prepared
+`docs/vergabe-demo-company-acceptance.md` with the two-user tender/lot/task,
+PDF round-trip, local issue and domain approval/submission-recording walkthrough,
+plus the remaining recovery/rollback evidence contract. A synthetic 803-byte PDF
+and its SHA256 are supplied. Requested the users' separate sign-in results;
+no response, workflow acceptance, account change or runtime mutation is inferred.
+The offsite route still names railiance-platform; resolving that route is not
+an authenticated upload. T03 remains wait for the existing human/recovery gate.
+
 
 ## Validate synthetic sizing against the exact release and shared contention