System Overview
How the layers of Govula fit together at a glance — the map you keep in your head.
Govula is a layered system. Each layer has one job and a narrow contract with the layer above and below it. Holding this map in your head makes everything else easier to place.
The layers
- Surface. Operator-facing UI: the actions feed, the proof viewer, the control center.
- Decision. Where a human takes a governed action — authority checks, capability gates, AI-suggested but never AI-signed.
- Execution. Adapters that turn a decision into a verifiable side-effect.
- Ledger. Three append-only logs that record what happened, hash-chained for replay.
- Tenant. Row-level-security isolation per organisation, enforced in the database, not just in code.
Where to go next
- Architecture Overview — the same map with more depth.
- System Boundaries — what the platform does and explicitly does not do.
- Execution Model — how a decision becomes an action.
- System Models — the data, authority, and accountability models.
You are here · Understand · step 1
Architecture Overviewnext step
Next in Understand: Architecture Overview.
What should I do next?
Authority Modelprimary
continues in "understand"; high glossary density (6 terms)
Ranked using IA v1 graph + intent map + glossary density (deterministic; no AI inference).