Record confirmed two-account Vergabe sign-in with OTP
All checks were successful
CI Smoke / host-smoke (push) Successful in 0s
CI Smoke / container-smoke (push) Successful in 2s

Assistant: codex
Assistant-Model: gpt-6.1-sol
Assistant-Session: 01a1abf1-7e95-7141-87c9-ee78332bf790
This commit is contained in:
tegwick 2026-11-05 16:45:03 +01:00
parent 2d5be35c89
commit e747e3397e
4 changed files with 61 additions and 5 deletions

View file

@ -0,0 +1,35 @@
{
"schema": "railiance.vergabe-pilot-user-return.v1",
"reported_on": "2026-11-05",
"workplan": "RAPPS-WP-0014",
"task": "RAPPS-WP-0014-T03",
"related_product_tasks": [
"VERGABE-WP-0019-T04",
"VERGABE-WP-0019-T06"
],
"evidence_source": "User confirmation in the active conversation",
"evidence_kind": "user_reported",
"company": "demo-company",
"product_url": "https://vergabe-teilnahme.coulomb.social/demo-company",
"account_count_reported": 2,
"both_accounts_can_sign_in": true,
"reported_authentication": [
"username",
"password",
"otp"
],
"personal_account_identifiers_recorded": false,
"credentials_or_tokens_recorded": false,
"runtime_mutations_by_agent": false,
"remaining_evidence": [
"Shared tender, lot and task changes visible across the two sessions",
"Document upload and byte-identical download by both accounts",
"Persisted local issue linked to the task",
"Domain approval and demo submission recording",
"Anonymous document refusal and owner-run inactive-session denial",
"Populated workflow survival through pod replacement",
"Coherent PostgreSQL, media and issue-state off-host recovery point",
"Isolated restored workflow and compatible rollback",
"Backup cadence, retention, recovery objectives and operating ownership"
]
}

View file

@ -1,7 +1,9 @@
# Demo-company pilot walkthrough
Prepared 2026-11-05 for RAPPS-WP-0014-T03 and VERGABE-WP-0019-T04/T06.
The steps below are pending user execution; preparing them records no acceptance.
The user confirmed both demo-company accounts can sign in with username/password
and OTP on 2026-11-05; see the [sign-in receipt](evidence/2026-11-05-vergabe-two-user-signin.json).
The collaborative workflow and recovery steps below remain pending execution.
## Sign in separately
@ -83,7 +85,8 @@ and [deployment binding](vergabe-demo-company-binding.md). Its receipt must cove
Existing database-only backup/restore targets default to historical `vergabe_db`
and omit both file stores. They cannot establish this three-store recovery claim.
The human sign-in/workflow response is pending; the attended restart, off-host
Two-account sign-in is user-confirmed; the shared workflow remains pending.
The attended restart, off-host
capture, isolated restore and rollback action has not been prepared or executed.
Logged-in account deactivation remains a separate owner-run access-control check
from the pilot contract. No account is disabled as part of these walkthrough steps.

View file

@ -1,6 +1,6 @@
# Vergabe demo-company deployment binding
Updated 2026-09-27 under RAPPS-WP-0014 and VERGABE-WP-0019.
Updated 2026-11-05 under RAPPS-WP-0014 and VERGABE-WP-0019.
Release binding is complete (RAPPS-WP-0014-T02). Recovery and invited-recipient acceptance remain open.
| Item | Current binding |
@ -18,11 +18,19 @@ Release binding is complete (RAPPS-WP-0014-T02). Recovery and invited-recipient
| Database / role | Fresh vergabe_demo_company / vergabe_demo_company, databases/apps-pg |
| Runtime custody | vergabe-demo-company/vergabe-demo-env; platform helper receipt in RPF-WP-0039 |
| Media / issue state | Separate Bound local-path PVCs, 5Gi / 1Gi; UID/GID/fsGroup 999 |
| Authentication | NetKingdom company welcome and OIDC deployed; founder sign-in recorded September 24. Fresh recipient journey and two-user acceptance remain open |
| Authentication | Two existing demo-company accounts can sign in with password and OTP, user-confirmed November 5. Shared workflow and full recipient acceptance remain open |
| Remaining handoffs | VERGABE-WP-0019-T06 welcome/SSO; RAPPS-WP-0014-T03 recovery; VERGABE-WP-0019-T04 pilot acceptance |
## Current SSO rollout
2026-11-05 user return: both existing demo-company accounts can sign in to the
product with username/password and OTP. This supersedes the earlier pending
second-account sign-in state. The [sign-in receipt](evidence/2026-11-05-vergabe-two-user-signin.json)
omits personal identifiers and credentials. Shared task/document/local-issue and
recovery acceptance remain open. Live release and claim metadata below retain
their dated evidence; November 5 preflight could not refresh Deployment/PVC
status with the current agent identity.
2026-09-12 attended rollout executed after explicit operator approval. KeyCape
and password setup are Ready on the prepared digests; exact public client
registration was CAS-applied (config resourceVersion 60123977) with unrelated

View file

@ -196,7 +196,7 @@ id: RAPPS-WP-0014-T03
status: wait
needs_human: true
decision_id: d06307e5-2737-461a-a2f4-a12c3b492a9a
intervention_note: "Bernd Worsch and the company contact must complete two-user/document acceptance; railiance-platform owns offsite access and storage backup delivery. Then complete the coherent isolated restore and rollback receipt under this task."
intervention_note: "Both demo-company accounts can sign in with password and OTP (user-confirmed 2026-11-05). Next complete shared tender/task/document/local-issue acceptance, then the coherent off-host recovery, isolated restore, rollback and operating ownership evidence. railiance-platform owns storage/custody delivery."
priority: high
assignee: the-custodian
blocking_reason: "Await populated two-user/document workflow, coherent PostgreSQL/media/issue-state off-host recovery point, isolated restored workflow, rollback evidence and support ownership. September 25 proves database restore and restart only."
@ -260,6 +260,16 @@ 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.
2026-11-05 sign-in return: the user confirms two existing demo-company accounts
can both sign in at the selected product URL with username/password and OTP.
Receipt: `docs/evidence/2026-11-05-vergabe-two-user-signin.json`; personal account
identifiers and credentials are omitted. Two-account sign-in is now confirmed
by the user. Shared tender/lot/task edits, document round-trip, local issue,
populated restart/recovery, rollback and operating ownership remain unproved.
Requested the shared task-edit result next. The broader decision
`d06307e5-2737-461a-a2f4-a12c3b492a9a` and T03 remain open/wait; sign-in alone
does not resolve the full workflow/recovery gate.
## Validate synthetic sizing against the exact release and shared contention