coulomb/state-hub
2
0
Fork 0
generated from coulomb/repo-seed
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

docs: clarify state hub intent

Browse Source
This commit is contained in:
Bernd Worsch
2026-05-17 21:37:02 +02:00
parent d2e7e206bc
commit 80ff5e6128
3 changed files with 125 additions and 14 deletions
Download Patch File Download Diff File Expand all files Collapse all files

19
README.md
View File

@@ -11,16 +11,17 @@ the former embedded implementation at:
/home/worsch/the-custodian/state-hub
```
## Current Extraction State
## Extraction State
The repo is being prepared by `CUST-WP-0043 - State Hub Repo Extraction`.
The extraction workplan `CUST-WP-0043 - State Hub Repo Extraction` is complete.
During the extraction window:
Current state:
- The implementation has been imported here with subtree history.
- `CUST-WP-0042` has been re-homed into this repository.
- The old embedded tree in `the-custodian` should remain only as a pointer once
the verification gate passes.
- The old embedded tree in `the-custodian` remains only as a pointer.
- This repository is authoritative for State Hub code, docs, tests, dashboard,
migrations, scripts, policies, and State Hub-local workplans.
## Workplans
@@ -30,10 +31,10 @@ New State Hub-local workplans should use the prefix:
SHUB-WP-0001
```
Legacy Custodian-hosted State Hub plans, such as `CUST-WP-0042`, may be carried
over with their existing State Hub IDs or bridged by a new `SHUB-WP-*`
continuation plan. Do not create duplicate workstreams manually; write the
workplan file first, then run consistency sync after this repo is registered.
Legacy Custodian-hosted State Hub plans, such as `CUST-WP-0042`, may retain
their existing IDs when that preserves State Hub workstream/task continuity.
Do not create duplicate workstreams manually; write the workplan file first,
then run consistency sync.
---