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

docs: start hub-core absorption foundation
Some checks failed
CI Smoke / host-smoke (push) Successful in 0s
Details
CI Smoke / pytest-smoke (push) Failing after 2s
Details

Browse source
This commit is contained in:
tegwick 2026-08-21 11:01:37 +02:00
parent 41107f42e6
commit 9285a880be
6 changed files with 32 additions and 28 deletions
Download patch file Download diff file Expand all files Collapse all files

20
workplans/CORE-WP-0010-runtime-absorption-and-archive.md
View file

@ -4,7 +4,7 @@ type: workplan
title: "Runtime absorption into hub-core and archive"
domain: infotech
repo: core-hub
status: blocked
status: active
owner: codex
topic_slug: infotech
created: "2026-08-09"
@ -57,10 +57,11 @@ the canonical joint record in `hub-core/docs/core-hub-absorption-plan.md`,
decision `12514947-6cc0-42a0-98ca-9aacc9d875b0`, and coordination message
`819d5af0-959f-4b0d-9f52-87514d99b480`.
Execution remains blocked on publishing the completed hub-core work at an
immutable source/image revision and replacing its deliberately ephemeral
in-memory backend with a production PostgreSQL boundary. Those are explicit
Slice 0 entry gates, not reasons to reopen the architecture decision.
Hub-core revision `7e1ec03` is committed and pushed with T01–T06 complete. S0
can therefore begin. It must replace the deliberately ephemeral in-memory
backend with a production PostgreSQL boundary and produce an immutable image
before any public route is eligible to move; those are implementation gates,
not reasons to reopen the architecture decision.
## Inventory runtime surfaces to absorb
@ -101,7 +102,7 @@ aligned with hub-core's accepted canonical plan; `HUB-WP-0004-T06` is done.
```task
id: CORE-WP-0010-T03
status: wait
status: progress
priority: high
state_hub_task_id: "c01ddec1-5737-4115-ac73-c402ffb5bdc5"
```
@ -109,9 +110,10 @@ state_hub_task_id: "c01ddec1-5737-4115-ac73-c402ffb5bdc5"
Migrate in slices with consumer smokes (ops-hub, activity-core) after each.
Record row counts and fixture replays per slice.
Waiting on a committed/published hub-core runtime revision, immutable image,
durable PostgreSQL backend, and candidate deployment. Start with Slice 0; do
not change public traffic.
Started 2026-08-21 after hub-core revision `7e1ec03` closed the joint planning
and publication gate. S0 now owns the durable PostgreSQL backend, legacy
auth/health compatibility, immutable image, and internal candidate deployment.
Do not change public traffic.
## Cutover production traffic