StableUser
Connect → Govern → Understand → Decide → Act
The canonical Blocchi operating loop and why every surface uses it.
Blocchi is designed around one operating loop rather than separate analytics, AI and automation products with different data models.
| Step | Contract |
|---|---|
| Connect | Acquire data through governed source and dataset boundaries. |
| Govern | Resolve canonical identity, semantics, quality, provenance, access and readiness. |
| Understand | Produce metrics, findings, events and evidence-backed context. |
| Decide | Support human or agent reasoning without widening data scope. |
| Act | Execute only through registered, policy-aware and auditable action paths. |
Why this matters
A metric queried through REST, an answer produced through MCP and a recommendation shown in the UI should not become three different truths. They should resolve through the same governed application services and the same actor scope.
Likewise, an agent proposing a CRM change should not gain a separate mutation path. It should use the same registered action, policy, approval and evidence model as a first-party workflow.
Last updated on