coulomb/the-custodian
4
0
Fork 0
Code Issues 1 Pull requests Projects Releases Packages Wiki Activity Actions

Block CUST-WP-0071 and CUST-WP-0073 pending cross-repo requirements
All checks were successful
CI Smoke / host-smoke (push) Successful in 0s
Details
CI Smoke / container-smoke (push) Successful in 7s
Details

Browse source 
Remaining tasks wait on GLAS-WP-0012, RAPPS-WP-0014-T03 and platform/infra/warden
owners; requirement tables added to both workplans.

Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
This commit is contained in:
codex 2026-09-28 20:25:41 +02:00
parent 807bed6bba
commit 693f7f1962
3 changed files with 49 additions and 12 deletions
Download patch file Download diff file Expand all files Collapse all files

23
workplans/CUST-WP-0071-measured-workload-sizing-and-weekly-review.md
View file

@ -4,7 +4,7 @@ type: workplan
title: "Size Railiance workloads from actual demand and establish a weekly allocation review"
domain: infotech
repo: the-custodian
status: active
status: blocked
flavor: planning
owner: the-custodian
topic_slug: custodian
@ -94,10 +94,11 @@ updated reef-railiance-k3s owner evidence.
```task
id: CUST-WP-0071-T02
status: progress
status: wait
priority: high
assignee: the-custodian
depends_on: [CUST-WP-0071-T01]
blocking_reason: "Await RAPPS-WP-0014-T03 (blocked, needs_human): populated two-user/document workflow run by Bernd and the company contact, giving representative load for p95 <= 2s / zero failures."
state_hub_task_id: "82192370-2fd7-5363-88d2-3c67889d3d68"
```
@ -122,10 +123,11 @@ pilot sample provisional. A successful smoke test alone is not sizing proof.
```task
id: CUST-WP-0071-T03
status: progress
status: wait
priority: high
assignee: the-custodian
depends_on: [CUST-WP-0071-T01, CUST-WP-0071-T02]
blocking_reason: "Await CUST-WP-0071-T02 representative sample; Forgejo/runner demand and zero-request workload review need owner input (railiance-cluster, railiance-forge, resource-control)."
state_hub_task_id: "6dc67558-eb1e-5bb6-a667-986f884dd495"
```
@ -258,3 +260,18 @@ zero-failed-operations target (document transfer excluded from that latency
threshold). The current seven-day telemetry remains provisional until the
representative workflow runs. This is an acceptance criterion, not a claim that
it has passed. Keep the run and its evidence under existing T02.
## Blocked — requirements on other repos (2026-09-28)
The bounded review is complete: T01 done, seven-day telemetry recorded, and the
provisional keep decision (60m/256Mi) is evidenced. No further step is
implementable here; workplan set to `blocked`. Requirements:
| Owner | Requirement | Gates |
|-------|-------------|-------|
| railiance-apps (RAPPS-WP-0014-T03, needs_human) | Two-user/document acceptance run on the deployed pilot with Bernd and the company contact | T02 |
| vergabe-teilnahme (VERGABE-WP-0019, blocked) | Release/tenant assumptions and fixture for the representative run | T02 |
| resource-control, railiance-cluster, railiance-forge | Owner review of Forgejo/runner demand (namespace CPU p95 1454m) and twelve zero-request workloads | T03 |
| activity-core | Durable weekly schedule (Mon 08:00 Europe/Berlin), retained report, owner receipt, missed-run handling | T05 (after T04) |
Resume when RAPPS-WP-0014-T03 records the acceptance run; T03 → T04 → T05 follow.