docs: close core-hub absorption execution
This commit is contained in:
parent
055cf4980c
commit
f51a5819d5
3 changed files with 22 additions and 8 deletions
|
|
@ -9,7 +9,7 @@ HelixForge hubs.
|
|||
| --- | --- |
|
||||
| **hub-core** | This repo — importable package plus target primary runtime image |
|
||||
| **state-hub** | Legacy coordination host being replaced capability by capability |
|
||||
| **core-hub** | Current `/api/v2` runtime retained temporarily for absorption rollback |
|
||||
| **core-hub** | Previous `/api/v2` runtime retained temporarily as live rollback |
|
||||
|
||||
Ecosystem architecture: `/home/worsch/the-custodian/docs/hub-ecosystem-architecture.md`
|
||||
|
||||
|
|
@ -72,6 +72,11 @@ The staged Core Hub transition is defined in
|
|||
retains Core Hub as rollback until data, consumer, and stabilization gates
|
||||
close.
|
||||
|
||||
Production authority moved to hub-core on 2026-08-21. The public compatibility
|
||||
surface runs the immutable `055cf49` image while Core Hub remains deployed with
|
||||
an empty writer set through the seven-day stabilization window ending no
|
||||
earlier than 2026-08-28T20:49:50+02:00.
|
||||
|
||||
## First Slice
|
||||
|
||||
- SQLAlchemy base metadata and timestamp helpers.
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue