Specifications¶
Specifications own exact behavior: interfaces, files, schemas, mappings, workflow order, state transitions, errors, compatibility, and current known divergence.
Requirements describe what must be true. Architecture describes where components sit. Security describes threats and controls. Guides derive procedures from these specifications.
Module owners¶
| Module | Specification |
|---|---|
| Cross-cutting conventions | Core conventions |
| Setup | CLI and render contract |
| Deployment | Deployment framework |
| Historical generation | Data contract |
| Live streaming | Event contract |
| Eventhouse and Lakehouse analytics | Fabric analytics |
| ML, ontology, and agents | Model contracts |
| Power BI | Semantic model |
| Operations | Runbook |
| Security | Access control |
| Documentation | Zensical site |
Dated implementation plans and the retired Docusaurus source were reconciled into these owners and removed.