docs: add State Hub reference page and restructure reference index

New page (docs/state-hub.md) covers:
- Why: the invisible state problem across repos and agents
- What: Derived Data Store, Read Model, Agent Orchestration Layer,
  Cross-Repo Observatory — and what it is NOT
- Derived Data Store principle (ADR-003): fingerprint cache, rebuild
  guarantee, force-refresh
- Repository Orchestrator: session protocol, cross-domain coordination
  via messages + capability routing, Kaizen agents
- Architecture diagram (ASCII), technology choices, data model overview
- Running the hub, design principles, related docs

reference.md: add Architecture & Design section grouping state-hub,
TPSC, GDPR maturity, SCOPE.md, capabilities, and goals docs.

Co-Authored-By: Claude Sonnet 4.6 (1M context) <noreply@anthropic.com>
This commit is contained in:
2026-03-20 02:01:58 +01:00
parent 51e95ec21a
commit 1e0ae37c89
3 changed files with 283 additions and 0 deletions

View File

@@ -41,6 +41,19 @@ convention used in the Custodian State Hub.
---
## Architecture & Design
| Topic | What it covers |
|-------|---------------|
| [State Hub](/docs/state-hub) | Why/how/what — Derived Data Store principle, orchestrator role, architecture diagram, design principles |
| [TPSC](/docs/tpsc) | Third-Party Services Catalog — tpsc.yaml format, ingest, MCP tools |
| [TPSC — GDPR Maturity](/docs/gdpr-maturity) | 7-level CNIL/IAPP scale, per-level guidance, key GDPR concepts |
| [SCOPE.md](/docs/scope) | The scope file format and how to write one |
| [Capabilities](/docs/capabilities) | Capability catalog, request routing, MCP tools |
| [Goals](/docs/goals) | Domain and repo goals, priority ordering |
---
## Meta
| Topic | What it covers |