docs: select demo-company for invited pilot onboarding
Assistant: codex Assistant-Model: gpt-6-astra Assistant-Session: 01a07ff8-19d0-7820-b4d0-1353833cb7fc
This commit is contained in:
parent
8d7e7de536
commit
2b5213d5ac
1 changed files with 10 additions and 4 deletions
|
|
@ -77,8 +77,13 @@ state_hub_task_id: "9065d5cb-2c65-561e-a237-e39da4f3b0fd"
|
|||
RAPPS-WP-0014 owns exact image/chart/host/namespace/database/Secret binding,
|
||||
persistent media plus distinct issue-facade state, isolated restore rehearsal,
|
||||
and rollback. The customer app owns live CI and immutable release evidence.
|
||||
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 user now selects a fresh `demo-company` demo tenant with `demo-user1`, etc.
|
||||
Use `tenant:trial:demo-company` under NetKingdom ADR-0013 and two ordinary demo
|
||||
accounts initially. Native tenant creation and memberships use the existing
|
||||
User Engine operator portal; this does not implement Django SSO. Hostname
|
||||
preference is pending (`demo-vergabe.coulomb.social` proposed). The concrete
|
||||
prepared binding lives at `railiance-apps/docs/vergabe-demo-company-binding.md`.
|
||||
No password or personal user list belongs 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
|
||||
|
|
@ -102,12 +107,13 @@ status: wait
|
|||
priority: high
|
||||
assignee: the-custodian
|
||||
depends_on: [VERGABE-WP-0019-T03]
|
||||
blocking_reason: "Await admitted company deployment, immutable release and demonstrated restore; company/host/data selection is pending."
|
||||
blocking_reason: "Await native demo-company tenant, admitted deployment and demonstrated restore; hostname and operator login remain pending."
|
||||
state_hub_task_id: "db807f96-f5b8-528d-bc33-75a33fbbf1e4"
|
||||
```
|
||||
|
||||
Product acceptance: Bernd Worsch and the named company contact. Verify two
|
||||
separate ordinary-user accounts can sign in, change passwords, create a tender
|
||||
separate ordinary-user accounts (`demo-user1` and `demo-user2` initially) can sign
|
||||
in, change passwords, create a tender
|
||||
and lot, collaborate on tasks, upload/download a document, record a v1 domain
|
||||
approval and submission, and report feedback. Verify anonymous access and a
|
||||
revoked user fail, health remains available, and pod replacement preserves all
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue