feat: add durable Core Hub absorption runtime
This commit is contained in:
parent
7e1ec03f0c
commit
8ab1d0c09a
20 changed files with 2423 additions and 15 deletions
10
README.md
10
README.md
|
|
@ -52,11 +52,15 @@ uv sync --extra runtime
|
|||
hub-core api
|
||||
hub-core mcp --api-base http://127.0.0.1:8010
|
||||
hub-core migrate head --database-url postgresql+asyncpg://...
|
||||
hub-core migration validate core-hub-export.json
|
||||
hub-core migration import core-hub-export.json --database-url postgresql+asyncpg://...
|
||||
```
|
||||
|
||||
The initial runtime exposes registry, messaging, progress-event,
|
||||
interaction-event, and projection-query ports. Its included memory backend is
|
||||
for local/conformance use and fails production readiness unless explicitly
|
||||
The runtime exposes registry, messaging, progress-event, interaction-event,
|
||||
and projection-query ports, plus the governed Core Hub `/api/v2`
|
||||
compatibility surface. Its PostgreSQL backend includes migrations, audit, and
|
||||
idempotent seven-table migration tooling. The memory backend remains for
|
||||
local/conformance use and fails production readiness unless explicitly
|
||||
enabled. See `docs/runtime.md`.
|
||||
|
||||
The reusable Tier 2/3 scaffold is documented in `docs/conformance.md` and runs
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue