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

Close Vergabe binding and record remaining recovery blockers
All checks were successful
CI Smoke / host-smoke (push) Successful in 0s
Details
CI Smoke / container-smoke (push) Successful in 3s
Details

Browse source 
Assistant: codex
Assistant-Model: gpt-6-astra
Assistant-Session: 01a0e3b3-11fe-7ba0-a4a3-92331aab0ba1
This commit is contained in:
tegwick 2026-09-27 18:34:05 +02:00
parent 1839c0ba42
commit cfbc95e11d
6 changed files with 136 additions and 36 deletions
Download patch file Download diff file Expand all files Collapse all files

36
workplans/RAPPS-WP-0014-vergabe-invited-pilot.md
View file

@ -4,12 +4,12 @@ type: workplan
title: "Deploy and recover the first invited Vergabe company pilot"
domain: financials
repo: railiance-apps
status: active
status: blocked
flavor: implementation
owner: the-custodian
topic_slug: railiance
created: "2026-09-11"
updated: "2026-09-25"
updated: "2026-09-27"
related: [VERGABE-WP-0019, VERGABE-WP-0018, HFACT-WP-0001, CUST-WP-0071]
state_hub_workstream_id: "c7fdaa7e-cab8-5d1d-86c2-f1aad7927c57"
---
@ -38,9 +38,9 @@ values template prepare the deployment; no live resources were changed.
```task
id: RAPPS-WP-0014-T02
status: progress
status: done
needs_human: false
intervention_note: "DNS, TLS and application placement are verified. Product SSO/welcome and pilot/recovery acceptance remain in the existing owner tasks."
intervention_note: "Binding complete: revision 3, immutable image, DNS/TLS, database custody and both PVCs verified. Recipient acceptance remains VERGABE-WP-0019-T04/T06; recovery remains T03."
priority: high
assignee: the-custodian
state_hub_task_id: "b00958c8-1401-5ebf-bc22-c0252618d897"
@ -181,15 +181,25 @@ confirmation are now requested from the operator; no user credential was used
by the agent. Recovery and two-user acceptance remain their existing tasks.
Evidence: railiance-apps/docs/evidence/2026-09-12-demo-company-sso-live.md.
2026-09-27 closeout: T02 is done. Read-only verification confirms release
revision 3, chart 0.2.1 and the recorded `a26444f5…` image, Ready 1/1,
60m/256Mi requests, both Bound claims, Ready TLS and HTTP 200 health. The
September 24 founder sign-in resolves the former issuer-login wait. Exact
binding is complete; the invited recipient journey and two-user acceptance
remain VERGABE-WP-0019-T04/T06, and recovery remains T03. See
`docs/evidence/2026-09-27-vergabe-binding-review.md`.
## Demonstrate restart, isolated restore, rollback and operating ownership
```task
id: RAPPS-WP-0014-T03
status: progress
status: wait
needs_human: true
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."
priority: high
assignee: the-custodian
depends_on: [RAPPS-WP-0014-T02]
blocking_reason: "Database restore and app restart are proved. Two-user collaboration and a document round-trip are still open."
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."
state_hub_task_id: "dd069c6d-fcc1-5bac-b233-976f2f0d5cd1"
```
@ -218,3 +228,17 @@ The app pod was recreated and `/demo-company/health/` returned 200. The age
file stayed on the workstation; the Nextcloud upload was not run. Two-user
collaboration and a document round-trip remain. Evidence:
`docs/evidence/2026-09-25-vergabe-demo-company-restore.md`.
2026-09-27 loose-end review: T03 now waits and this workplan is blocked.
The September 25 database-only drill and empty file claims do not satisfy the
three-store recovery contract. Complete the populated synthetic workflow with
Bernd Worsch and the company contact, obtain a matched off-host recovery point
through railiance-platform, restore into an isolated database and separate
claims, verify both users and document checksums, and record schema-compatible
rollback plus named incident/support ownership. Credential routing confirms
`railiance-backup-offsite-lane` belongs to railiance-platform; a resolvable route
alone is not an authenticated upload or a backup receipt. The safe auth check
confirmed OpenBao unsealed but no valid caller token, so the workstation upload
path needs Bernd Worsch's attended login. Existing tasks retain
all remaining work; no task or workplan was opened.