coulomb/railiance-apps
4
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

docs: record native user setup and product handoff requirements
All checks were successful
CI Smoke / host-smoke (push) Successful in 0s
Details
CI Smoke / container-smoke (push) Successful in 1s
Details

Browse source 
Assistant: codex
Assistant-Model: gpt-6-astra
Assistant-Session: 01a07ff8-19d0-7820-b4d0-1353833cb7fc
This commit is contained in:
tegwick 2026-09-12 01:08:33 +02:00
parent effd0a3170
commit 02c29eec53
3 changed files with 45 additions and 8 deletions
Download patch file Download diff file Expand all files Collapse all files

14
docs/vergabe-teilnahme-pilot.md
View file

@ -9,8 +9,8 @@ the historical deployment is still live.
Before native admission, record the following non-secret values in the company
binding. The user selects a fresh `demo-company` workspace; see
[its prepared binding](vergabe-demo-company-binding.md). Native tenant creation
and hostname admission are pending; example values do not create a tenant.
[its prepared binding](vergabe-demo-company-binding.md). Native tenant/user/password setup is verified; application hostname admission
and product placement remain pending.
| Binding | Required evidence |
| --- | --- |
@ -150,3 +150,13 @@ NK-WP-0036-T04. Tenant-path application source 9345a1b passes 98 tests and seven
local browser checks; image publication 44 passed with digest
sha256:cebe8ca6218cc89f903e8a69e06ac50d3812526d4119cf4da485cc173f674b68.
Live edge/data admission remains open. See the updated demo-company binding for execution status.
2026-09-12 update: directory credential reconciliation succeeded, the operator
confirmed portal login/logout and user password setup, and live records show
three demo-company memberships with one linked identity. Native provisioning
is no longer the current blocker. The product still needs DNS/TLS, fresh data
custody, placement and recovery. VERGABE-WP-0019-T06 now explicitly tracks the
requested tenant welcome and connection to the new NetKingdom identity. The
earlier manually provisioned Django account path remains an interim capability;
it does not make the directory password a product credential or implement SSO.