Verum Runtime/governed agent runtime
Actions you
can defend.
Ask in plain language. The runtime resolves your request to canonical tools on the lakehouse — and every invocation must clear five boundary gates before anything executes. Denials are structured, defaults carry notices, and filings wait for a person.
- ask“Produce the ORSA report for this year”
- resolveRanked candidate tools — retrieve, fuse, rerank over the canonical surface
- gateFive boundary gates, evaluated per step
- confirmFiling steps park and wait for a human approval
- actDispatched, recorded, explainable — every invocation has an audit view
how it works
Resolve. Gate. Audit.
Three moves, one direction. A request becomes a proven action — or a structured refusal that tells you exactly which gate said no.
- 01
Resolve
A plain-language question is matched against the canonical tool surface — retrieve, fuse, rerank. Each candidate declares the inputs it needs and the defaults it would apply.
- 02
Gate
Entitlements are checked under the canonical role closure; preconditions, default notices, cross-chain writes, and default coherence are enforced. A deny halts the step with a structured error.
- 03
Audit
Every invocation gets an id and an explain view: the entitlement decision, the prompts it would ask, the defaults it applied, and the prompt budget it spent.
the boundary
Five gates, every step.
No invocation reaches dispatch without clearing all five. Each gate is a pure decision over the invocation context — and each denial is metered and recorded.
Precondition
preconditionEvaluates the actionType’s declared preconditions against the bound inputs. A bound, violated predicate halts the step; absent state is reported as not-yet-verifiable, never counted as a pass.
Entitlement
entitlementCompares the tool’s required entitlements with the caller’s roles under the canonical implies-roles closure. No overlap, no invocation — and the denial is recorded.
Cross-chain read-only
cross_chain_read_onlyBlocks any write into the interface.* namespace from a non-owning chain. The primary chain owns its interface entities; reinsurance reads them, never writes them.
Default notice
default_noticeA symbolic default applied without the mandated notice halts the step. Defaults are declared and recorded — never silent.
Symbolic-default coherence
symbolic_default_coherenceEvery applied default must belong to a canonical category in the symbolic-default registry and match the field it fills. An incoherent default halts the step.
Alongside the five, chain steps flagged as approval gates park the run WAITING until a person confirms — an unanswered request times out after 15 minutes and the run halts. The runtime does not proceed on silence.
action chains
Five steps.
One human gate.
The ORSA filing chain runs actuarial valuation through regulatory submission as one governed sequence. Its last step is an approval gate: sign in and run it to watch the chain park for confirmation — the parking is the point.
- 1 · act-run-actuarial-valuationRun actuarial valuation for the ORSA base case
- 2 · act-compute-ifrs17Compute IFRS 17 contract groups for the period
- 3 · act-run-compliance-checkCheck capital adequacy and SCR coverage before filing
- 4 · act-submit-regulatory-filingSubmit the ORSA narrative and quantitative data
- 5 · act-run-compliance-checkVerify the report is acknowledged by the regulatorapproval gate
Step into the console.
Pick a seat. The console resolves live questions, gates live invocations, and runs the filing chain against the real runtime — synthetic data, honest denials.
the family