Close Core Hub ops evidence contract gate

This commit is contained in:
2026-06-27 23:57:22 +02:00
parent b39f3cc6cc
commit 46e2012160
4 changed files with 38 additions and 9 deletions

View File

@@ -77,6 +77,13 @@ rewritten around this recommendation. The rewrite is enough to stop the obsolete
standalone ops-hub scaffold sequence, but not enough to declare Core Hub
production cutover complete.
2026-06-27 T14 closeout: Core Hub now has
`docs/specs/ops-evidence-contract.md`, which defines the ops evidence API
resources, event vocabulary, non-secret access metadata rules, service inventory
mapping, readiness-summary inputs, and read-model gaps. This closes the T14
definition gate while leaving deployed evidence, cutover coupling, and UI work
for T16/T17/T18.
## Remaining Gates
- Run `make deployed-smoke` or `make operator-cli CLI_ARGS="deployed-smoke ..."`

View File

@@ -100,7 +100,7 @@ Resume from `docs/daily-triage-stabilization-status.md` and
| --- | --- | --- |
| State Hub | Pragmatic railiance01 path has image, manifests, empty deploy, migrations, restored WSL2 data, row-count comparison, and healthy API through `CUST-WP-0011-T06`. | `CUST-WP-0011-T07` cutover approval, then stabilization; HA path stays deferred. |
| Inter-Hub / Core Hub | Public `https://hub.coulomb.social/api/v2/hubs` exposes `ops-hub`; `CORE-WP-0008` finished the Core Hub API smoke harness, activity-core sink, staging profile, CLI wrappers, UI backlog, and Custodian handoff. | Run deployed Core Hub smoke, staging import, activity-core sink smoke, and readiness summary; keep Haskell Inter-Hub only for migration/rollback proof. |
| ops-hub evidence | `CUST-WP-0025-T13` through `T19` now use Core Hub API/CLI/UI gates; `CUST-WP-0047` and `CUST-WP-0049` remain legacy/fallback records. | Execute `CUST-WP-0025-T14`, `T16`, `T17`, and `T18`; close legacy Inter-Hub waits only through deployed Core Hub evidence or explicit supersede decision. |
| ops-hub evidence | `CUST-WP-0025-T14` is done with the Core Hub ops evidence contract spec. `CUST-WP-0025-T13` through `T19` now use Core Hub API/CLI/UI gates; `CUST-WP-0047` and `CUST-WP-0049` remain legacy/fallback records. | Execute `CUST-WP-0025-T16`, `T17`, and `T18`; close legacy Inter-Hub waits only through deployed Core Hub evidence or explicit supersede decision. |
| issue-core | ArgoCD service is healthy on port `8765`; image `0.2.1`; ExternalSecret Ready; authenticated smoke created Gitea issue `175`. | activity-core still needs `ISSUE_CORE_API_KEY`, URL port `8765`, `ISSUE_SINK_TYPE=rest`, and a safe emission smoke. |
| Forgejo | Migration inventory/design lane is active but pre-cutover. | Production design decisions, SMTP/email recovery, package registry, Actions, backup/restore, migration drill, cutover approval. |
| artifact-store | D7.1 is done; D7.2 has an opt-in live MinIO compatibility harness and manual smoke docs. No live secret handoff is recorded. | Run D7.2 against an approved MinIO-compatible endpoint, then route D7.3 STS vending through identity/platform custody before changing credential behavior. |
@@ -108,10 +108,10 @@ Resume from `docs/daily-triage-stabilization-status.md` and
## Next-Pick List
1. Execute the rewritten `CUST-WP-0025` Core Hub gates: identity integration
(`T03`), ops evidence/read-model contract (`T14`), deployed smoke and
activity-core proof (`T16`), cutover decision coupling (`T17`), and first UI
screens (`T18`).
1. Execute the remaining rewritten `CUST-WP-0025` Core Hub gates: identity
integration (`T03`), deployed smoke and activity-core proof (`T16`), cutover
decision coupling (`T17`), and first UI screens (`T18`). T14 is complete as
the ops evidence/read-model contract definition gate.
2. Keep `CUST-WP-0047` and `CUST-WP-0049` as legacy evidence/fallback until
Core Hub deployed smoke evidence or an explicit supersede decision closes
them.