Data & Event Platform — later capabilities¶
Target
This page describes intended behaviour or structure. No implementation is claimed unless a section is explicitly marked Current implementation or Evidence.
No later-stage services.
| Capability | Owner when built | Taken up when |
|---|---|---|
| Analytics warehouse profile (usage, cost, BI projections) | BC-42 with Observability and FinOps | overview projections outgrow the operations store |
| Graph store profile (relationships, temporal facts, provenance) | BC-42 with Knowledge (BC-39) | repository intelligence needs a federated graph query beyond SQL |
| CloudEvents as an optional carriage profile over the port | BC-42 | a partner or A2A integration needs it (ADR-0012 note, technology radar) |
| Residency migration orders (tracked move between regions) | BC-42 | a tenant changes region after data exists |
| Consumer-driven contract tests generated from the registry | BC-42 with DevOps/GitOps | the release pipeline consumes the registry |
| Multi-region placement with per-tenant failover | BC-42 with Runtime Cloud | beyond the pilot class (D30 is single region) |
| Hold-your-own-key per tenant | BC-42 with the Secret Broker | an edition requires it (D34) |