diff --git a/workplans/VERGABE-WP-0019-invited-company-pilot.md b/workplans/VERGABE-WP-0019-invited-company-pilot.md
index 3fbd9a6..c178a34 100644
--- a/workplans/VERGABE-WP-0019-invited-company-pilot.md
+++ b/workplans/VERGABE-WP-0019-invited-company-pilot.md
@@ -9,7 +9,7 @@ owner: the-custodian
 topic_slug: vergabe-teilnahme
 created: "2026-09-11"
 updated: "2026-09-11"
-related: [VERGABE-WP-0018, RAPPS-WP-0014, HFACT-WP-0001]
+related: [VERGABE-WP-0018, RAPPS-WP-0014, HFACT-WP-0001, CUST-WP-0071]
 state_hub_workstream_id: "85b5f304-d497-5570-bebf-3a3669ef6a7d"
 ---
 
@@ -81,6 +81,14 @@ Obtain the exact company, user count, hostname and empty-vs-existing data choice
 from the user; no password or user list is required in public work records.
 The historical vergabe_db is not disposable and must not be overwritten.
 
+The user subsequently accepts a 60m application CPU request for one tenant with
+very few users as a prototype of HelixForge app delivery and Railiance/NetKingdom
+onboarding. RAPPS-WP-0014 owns the explicit pilot override; this is an accepted
+low-allocation experiment, not measured production sizing. CUST-WP-0071 is
+registered for later metrics-based sizing and a final weekly allocation-review
+setup. That follow-up does not block this deployment. CPU limits, memory,
+protected access and company/data isolation remain governed by the pilot packet.
+
 On 2026-09-11 the checked Railiance cluster contains neither the historical
 vergabe-teilnahme namespace nor any Deployment whose name/image contains
 vergabe/teilnahme. Treat the old runbook as historical intent, not a live return.