coulomb/the-custodian
2
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

CUST-WP-0025-T16 progress + CUST-WP-0051: Core Hub staging deployed with full smoke evidence

Browse Source 
Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
This commit is contained in:
codex
2026-07-02 16:40:37 +02:00
parent 916808eac2
commit 67ef857460
2 changed files with 24 additions and 1 deletions
Download Patch File Download Diff File Expand all files Collapse all files

14
workplans/CUST-WP-0025-fos-hub-bootstrap.md
View File

@@ -475,7 +475,7 @@ rather than becoming the first implementation path.
```task ```task
id: CUST-WP-0025-T16 id: CUST-WP-0025-T16
status: wait status: progress
priority: high priority: high
state_hub_task_id: "702849c5-b253-4ede-afa7-0ab4f81e49a5" state_hub_task_id: "702849c5-b253-4ede-afa7-0ab4f81e49a5"
``` ```
@@ -498,6 +498,18 @@ path, and activity-core widget mapping are available. This task can close or
supersede `CUST-WP-0047-T05` and `CUST-WP-0049-T06` only after deployed Core supersede `CUST-WP-0047-T05` and `CUST-WP-0049-T06` only after deployed Core
Hub evidence exists or an explicit supersede decision is recorded. Hub evidence exists or an explicit supersede decision is recorded.
Progress 2026-07-02: the first evidence bullet is met. Core Hub staging is
deployed on CoulombCore (operator-approved: namespace `core-hub-staging`,
image `gitea.coulomb.social/coulomb/core-hub:3ed8531`, dedicated apps-pg
database, migrate job complete). The deployed smoke ran in-cluster with the
operator token confined to the namespace: run `20260702143544-6c8f18`,
`ok=true`, 10/10 API checks plus the full ops-hub bootstrap sequence (hub
`6798723a`, activated manifest, API consumer prefix `ch_N0ZhsXIbD`, widget,
interaction event `21d09f99`, hub registry containment true). Remaining T16
evidence: the deployed activity-core Core Hub sink smoke (runtime token +
widget mapping), then the supersede decision for `CUST-WP-0047-T05` /
`CUST-WP-0049-T06` becomes decidable on evidence.
### T17 — Core Hub, dev-hub, and cutover decision coupling ### T17 — Core Hub, dev-hub, and cutover decision coupling
```task ```task

11
workplans/CUST-WP-0051-infrastructure-stabilization-metaplan.md
View File

@@ -677,6 +677,17 @@ Progress 2026-06-27 Core Hub operator UI first screens:
`T17` cutover decision coupling; both still require staging/runtime custody or `T17` cutover decision coupling; both still require staging/runtime custody or
migration evidence. migration evidence.
Progress 2026-07-02 Core Hub staging deployed:
- The T07 Core Hub replacement lane got its first deployed proof: staging on
CoulombCore with the full smoke evidence chain (see `CUST-WP-0025-T16`
progress and `CORE-WP-0004-T03`, now done). Two defects fixed en route:
missing `psycopg2-binary` in the runtime image and the apps-pg
NetworkPolicy label requirement (`railiance.io/postgres-client=apps-pg`).
- Remaining Core Hub gates: activity-core sink smoke against staging
(runtime token + widget mapping), staging import (`CORE-WP-0005-T02`),
dual-run/cutover readiness, and Haskell retirement approval.
## Task: Create The Stable Pickup Checkpoint ## Task: Create The Stable Pickup Checkpoint
```task ```task