Kovent documentation¶
This site is the browsable source of truth for Kovent — doctrine, engines, return
specifications, and runbooks. Everything lives in the repository under docs/ and is published
from here.
Kovent is an online compliance monitoring and regulatory reporting platform. Licensed firms file returns through it; the supervisor tracks obligations, validates submissions, computes prudential indicators, scores risk, and runs enforcement from the same record.
Start here¶
| I want to… | Read |
|---|---|
| See the engine map | Platform overview |
| Understand why Kovent exists | Manifesto |
| See the architectural laws | Architecture doctrine |
| Know what we build first | Roadmap |
| Read a return specification | Specifications |
| Follow a return end to end | Submission lifecycle |
| Understand the UI rules | Design language |
| Look up a term | Glossary |
| Run these docs locally | ./scripts/docs.sh serve |
Engines¶
Return Studio
Configuration — templates, fields, rules, calendars, scoring. The no-code layer.
Registry
Licensed entities, licences, officers, mandates.
Cadence
Obligations, due dates, reminders, late flags, penalty triggers.
Strata
Versioned submissions. Append-only, amendment lineage.
Assay
Validation and computation. DMN owned by the regulator.
Bench
Supervisory review — triage, checklists, queries, outcomes.
Prism
Risk scoring that decomposes into drivers.
Docket
Cases, findings, directives, penalties, closure.
Seal
Hash-chained audit trail. Legally defensible by construction.
Projections
Read models for dashboards, heatmaps, and export packs.
How this site is organised¶
We follow Diátaxis inside an engine-first structure:
- Platform — the engine map, the stack, and what we build first
- Doctrine — locked principles (why), including the design language
- Engines — one page per engine: purpose, scope, data owned, status
- Specifications — the return catalogue and per-return contracts
- Decisions — architecture decision records
- How-to — runbooks
- Reference — glossary
Status¶
Kovent is at design stage. The design system and the supervision prototype are built; no runtime exists yet. Every page states its own status, and nothing here claims to be proven that is not. See the roadmap for what is real and what is next.
Edit and publish¶
Docs are markdown in git. Change a file, open a pull request, merge to main — Cloudflare Pages
rebuilds automatically. See Publish docs.