plan: receive exact-release and contention sizing evidence
Assistant: codex Assistant-Model: gpt-6.1-sol Assistant-Session: 01a15374-f59f-7a31-86d2-d23b5d2ed181
This commit is contained in:
parent
3be92daf74
commit
170e9b702c
3 changed files with 63 additions and 3 deletions
12
SCOPE.md
12
SCOPE.md
|
|
@ -291,3 +291,15 @@ existing bytes remain available for offline session startup; refreshing it does
|
|||
not require a Git commit. Authored workplans and the generated WORK-RECORDS index
|
||||
retain their existing source and staged-generation contracts. No runtime or
|
||||
credential change follows from this repository hygiene policy.
|
||||
|
||||
|
||||
## Synthetic pilot sizing follow-up
|
||||
|
||||
Application-owner local evidence and configurable workloads live in
|
||||
`vergabe-teilnahme/docs/evidence/2026-10-19-synthetic-sizing/` and that repository's
|
||||
`config/synthetic-pilot*.json`. RAPPS-WP-0014-T04 owns fresh exact release/hardware
|
||||
metadata and a co-timed isolated replay/shared-contention assessment feeding
|
||||
CUST-WP-0071-T02 and RESOURCE-WP-0008-T02. Routine read-only capture/preparation is
|
||||
authorized; no benchmark writes to customer datasets or unreviewed deployment
|
||||
changes follow from the local synthetic result. The existing T03 human/recovery
|
||||
gate remains separate and unchanged.
|
||||
|
|
|
|||
|
|
@ -11,7 +11,7 @@
|
|||
| workplan | RAPPS-WP-0001 | finished | — | workplans/RAPPS-WP-0001-cnpg-backup-scheduledbackup-coverage.md |
|
||||
| workplan | RAPPS-WP-0002 | finished | — | workplans/RAPPS-WP-0002-railiance01-activity-core-backup-automation.md |
|
||||
| workplan | RAPPS-WP-0003 | finished | — | workplans/RAPPS-WP-0003-policy-nexus-production-binding.md |
|
||||
| workplan | RAPPS-WP-0014 | blocked | — | workplans/RAPPS-WP-0014-vergabe-invited-pilot.md |
|
||||
| workplan | RAPPS-WP-0014 | active | — | workplans/RAPPS-WP-0014-vergabe-invited-pilot.md |
|
||||
| workplan | RAPPS-WP-0015 | active | — | workplans/RAPPS-WP-0015-coulomb-personal-content-release.md |
|
||||
| workplan | RAPPS-WP-0016 | active | — | workplans/RAPPS-WP-0016-forgejo-netkingdom-login.md |
|
||||
| workplan | RAPPS-WP-0017 | finished | — | workplans/RAPPS-WP-0017-reuse-private-reader-release.md |
|
||||
|
|
@ -34,6 +34,7 @@
|
|||
| task | RAPPS-WP-0014-T01 | done | — | workplans/RAPPS-WP-0014-vergabe-invited-pilot.md |
|
||||
| task | RAPPS-WP-0014-T02 | done | — | workplans/RAPPS-WP-0014-vergabe-invited-pilot.md |
|
||||
| task | RAPPS-WP-0014-T03 | wait | — | workplans/RAPPS-WP-0014-vergabe-invited-pilot.md |
|
||||
| task | RAPPS-WP-0014-T04 | todo | — | workplans/RAPPS-WP-0014-vergabe-invited-pilot.md |
|
||||
| task | RAPPS-WP-0015-T01 | done | — | workplans/RAPPS-WP-0015-coulomb-personal-content-release.md |
|
||||
| task | RAPPS-WP-0015-T02 | done | — | workplans/RAPPS-WP-0015-coulomb-personal-content-release.md |
|
||||
| task | RAPPS-WP-0015-T03 | done | — | workplans/RAPPS-WP-0015-coulomb-personal-content-release.md |
|
||||
|
|
|
|||
|
|
@ -4,12 +4,12 @@ type: workplan
|
|||
title: "Deploy and recover the first invited Vergabe company pilot"
|
||||
domain: financials
|
||||
repo: railiance-apps
|
||||
status: blocked
|
||||
status: active
|
||||
flavor: implementation
|
||||
owner: the-custodian
|
||||
topic_slug: railiance
|
||||
created: "2026-09-11"
|
||||
updated: "2026-10-03"
|
||||
updated: "2026-10-19"
|
||||
related: [VERGABE-WP-0019, VERGABE-WP-0018, HFACT-WP-0001, CUST-WP-0071]
|
||||
state_hub_workstream_id: "c7fdaa7e-cab8-5d1d-86c2-f1aad7927c57"
|
||||
---
|
||||
|
|
@ -246,3 +246,50 @@ path needs Bernd Worsch's attended login. Existing tasks retain
|
|||
all remaining work; no task or workplan was opened.
|
||||
|
||||
2026-10-03: human gate routed to hub decision d06307e5-2737-461a-a2f4-a12c3b492a9a (D7: Vergabe pilot: two real users run the invited setup-to-workflow acceptance) by CUST-WP-0075; resolving that decision raises C-40 here.
|
||||
|
||||
|
||||
## Validate synthetic sizing against the exact release and shared contention
|
||||
|
||||
```task
|
||||
id: RAPPS-WP-0014-T04
|
||||
status: todo
|
||||
priority: high
|
||||
assignee: railiance-apps
|
||||
state_hub_task_id: "c53fcaa9-859c-5b37-a17b-0a4cd2fb0e26"
|
||||
```
|
||||
|
||||
Receiving task for `CUST-WP-0071-T02` and `RESOURCE-WP-0008-T02`. The founder
|
||||
selected provisional configurable synthetic sizing on 2026-10-19; it does not
|
||||
replace the separate T03 human/recovery gate. Local application-owner evidence
|
||||
is in `vergabe-teilnahme/docs/evidence/2026-10-19-synthetic-sizing/`, with tunable
|
||||
workload and runtime profiles in that repository's `config/synthetic-pilot*.json`.
|
||||
The 1000m/1Gi local container comparison is a local observation, not a finding
|
||||
about the exact deployed release or a guarantee provided by a 60m reservation.
|
||||
|
||||
Routine read-only capture and source preparation are authorized work for this
|
||||
task; they do not require another founder decision. Capture fresh exact release
|
||||
metadata (image digest, chart/source revision, Gunicorn worker count, CPU/memory
|
||||
requests and limits, node CPU model/capacity, database binding and observation
|
||||
window). Record drift against the local test image and configuration rather than
|
||||
assuming source HEAD equals the deployed image.
|
||||
|
||||
Prepare the smallest isolated synthetic-data replay on the target hardware,
|
||||
using the same named operation/phase profile and a pinned release image. Reuse
|
||||
owner deployment/database custody and admission rules. Do not write workload
|
||||
fixtures or benchmark operations to an existing customer dataset. Any deployment
|
||||
mutation remains within its existing owner-reviewed execution scope; this task
|
||||
is not a blanket production change or credential grant.
|
||||
|
||||
Acceptance output must retain a co-timed idle baseline and workload window for
|
||||
application CPU/memory/throttling, per-operation p95/errors and separate document
|
||||
transfer, plus incremental PostgreSQL/shared-service demand and node contention.
|
||||
Record competing workloads/available CPU during the window and distinguish a
|
||||
CPU request from a quota. If shared-load representativeness or isolation cannot
|
||||
be established, preserve that concrete gap rather than promote a local pass to
|
||||
production acceptance. No new general benchmark suite is requested.
|
||||
|
||||
Return pinned configuration, hardware/release provenance, raw sampled evidence,
|
||||
coverage/gaps and a bounded recommendation to `RESOURCE-WP-0008-T02` for headroom
|
||||
and allocation review and `CUST-WP-0071-T02` for sizing acceptance. T03 remains
|
||||
unchanged: operator/customer recovery and human acceptance are not inferred from
|
||||
these synthetic results.
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue