Skip to content

Platform overview

Kovent architecture
One platform. Ten engines in five tiers. Configuration — not code — defines every return the supervisor collects.

The five tiers

Engines are grouped by what they are responsible for, not by deployment. The tiers read as a sentence: the regulator configures, the platform records what firms file, things happen in motion over time, the platform forms a judgement, and everyone reads the result.

Tier Engines Responsibility
Configure Return Studio Templates, rules, calendars, scoring weights — owned by the supervisor
Record Registry, Strata, Seal System of record: who is licensed, what they filed, what happened
Motion Cadence, Bench, Docket Time and workflow: obligations falling due, reviews, enforcement
Judge Assay, Prism Derived truth: validation, computation, risk scoring
Read Projections Query-side read models for dashboards and analytics

Return Studio

Field library, sections, formulas, validation rules, versioning, effective dates.

Registry

Firm master and licensing — categories, officers, beneficial owners, mandates.

Cadence

Compliance calendar — due-date calculation, reminders, escalation, extensions.

Strata

Submissions as immutable layers. Amendments add versions, never overwrite.

Assay

Validation and prudential computation as DMN the regulator can read.

Bench

Supervisory review — triage, assignment, checklist, queries, outcome.

Prism

Risk scoring where every score decomposes into named drivers.

Docket

Cases, investigations, evidence bundles, directives, penalties, closure.

Seal

Hash-chained audit trail across every engine.

Projections

CDC-fed read models — heatmaps, trends, export packs.

How a return moves through them

Return Studio                      Registry
  defines R02 v2.4                   licence 873390 is a Category-2 SMI
        │                                  │
        └──────────────┬───────────────────┘
                       ▼
                    Cadence
          obligation: R02 · Q2 2026 · due 14 Aug
                       │
                       ▼
                    Strata                        ← firm prepares and certifies
          submission v1.0, sealed on submit
                       │
                       ▼
                     Assay
          7 validation rules + capital computation
                       │
          ┌────────────┴────────────┐
          ▼                         ▼
        Bench                     Prism
   reviewer checklist        risk score + drivers
          │                         │
          ├── query ──► Strata v1.1 (resubmission)
          │
          ├── approve ──► archived as accepted for the period
          │
          └── escalate ──► Docket (case opened)
                       │
                       ▼
                     Seal
        every transition above, hash-chained
                       │
                       ▼
                  Projections
        dashboards, heatmaps, export packs

Every arrow in that diagram is an event. Nothing in the read tier is written synchronously by the write path.

Traceability to the requirement

The engine boundaries are not invented. They map one-to-one onto the functional modules in the requirement, so a reader can move between the two documents without a translation table.

Requirement module Kovent engine
Firm Master and Licensing Register Registry
Compliance Calendar Cadence
Return Template Builder Return Studio
Submission Portal Strata
Supervisory Review Bench
Risk Engine Prism
Case Management Docket
Analytics and BI Projections
Audit (BR-079) Seal
Validation (BR-*, all modules) Assay

Two audiences, one record

Kovent serves two populations from the same data:

  • The supervisor — triage queues, review screens, risk registers, case files, analytics
  • The licensed firm — obligation calendar, draft returns, pre-submission validation, maker-checker, query responses, submission receipts

They are separate front-ends over the same engines with different permissions. The firm sees its own obligations and submissions; the supervisor sees the market. Neither sees a different version of the truth.

Doctrine

Locked principles that govern every engine: