Record accepted prototype sizing and later metrics review
All checks were successful
Application acceptance / application-tests (push) Successful in 8s
CI Smoke / container-smoke (push) Successful in 1s
CI Smoke / host-smoke (push) Successful in 0s

Assistant: codex
Assistant-Model: gpt-6-astra
Assistant-Session: 01a07ff8-19d0-7820-b4d0-1353833cb7fc
This commit is contained in:
tegwick 2026-09-11 18:48:11 +02:00
parent f7a388681c
commit 8d7e7de536

View file

@ -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.