Governance
Constans operates inside
existing work.
No migration. No process change. No new system to manage.
Entry point
Most governance failures happen quietly.
Two teams settle the same question different ways. A practice drifts from policy one small call at a time. The same conclusion gets reinvented in four corners of the org and nobody connects the dots. By the time these reach a customer call, a regulator's question, or a board paper, they've already cost something.
Constans watches for the patterns that matter - conflict, policy drift, convergence, coverage gaps, risk accumulation, and emerging patterns - and raises them while they're still a correction, not a crisis.
Governance
Hard constraints ensure reliability.
Approved canon is the only authoritative source. When the system draws on a proposed but not-yet-confirmed decision, it says so. Nothing presents as authority that has not been confirmed by a human.
Every response records what informed it. Every confirmation records who confirmed it. Every change is tracked. Nothing is overwritten silently.
Decisions are defensible because they are traceable.
Beneath the surface
Knowledge accumulates from the work itself.
For Constans to surface patterns across decisions, it needs to know what your org has already decided. That knowledge accumulates as a side effect of the questions people ask - not from an import.
A question is asked. If validated knowledge exists, the system answers. If not, it cannot answer. It escalates.
The system identifies what is missing and asks the right person. The question arrives with context. The expert responds within their normal work.
The answer is reviewed, validated, and incorporated. It cannot be surfaced until it is confirmed. The answer is delivered back to the original question.
The gap is eliminated. That question will never require escalation again.
The lifecycle
From signal to governed answer.
Every answer the system gives is the end of this sequence. Nothing skips a step. Confirmation is structural, not optional.
01
Signals
Raw input from chat, email, documents, MCP.
02
Events
Structured and contextualised.
03
Proposed decisions
AI-formulated, pending review.
04
Human confirmation
A named expert validates or rejects.
05
Canon
Versioned, traceable, authoritative.
06
Governed AI reasoning
Answers grounded only in confirmed canon, with provenance.
In practice
What governed reasoning looks like.
The artifacts below are illustrative. The shape is real: canon entries, decision records, and provenance trails exist in the system in this form.
Canon entry
CN-2418 · v3
- Topic
- Engagement scope - regulated financial services
- Effective
- All fixed-fee engagements within FCA-regulated scope
- Sources
- D-1217 · EN-742
- Confirmed by
- Senior partner, Reg-Tech practice
- Version
- Current · superseded v2 on 2026-05-12
Decision record
D-1217
- Question
- Should fixed-fee engagements be accepted in newly regulated sectors?
- Proposed by
- Constans (drawn from CN-1108, CN-2102)
- Confirmed by
- Managing partner · 2026-04-04
- Dissents
- 2 recorded - see audit trail
- Status
- Active · 14 downstream decisions reference this
Provenance trail
for system answer A-9402
- Answer
- Yes, with scope conditions noted in CN-2418.
- Drawn from
- CN-1108 (v2) · CN-2418 (v3) · D-1217
- Confirmations
- 4 expert confirmations over 18 months
- Last reviewed
- 2026-05-22 by Reg-Tech practice lead
Adoption
It scales through use, not rollout.
Constans starts with one team. Expansion is not forced. As gaps are eliminated, knowledge becomes available across the organisation. What is resolved in one place is accessible everywhere.
Repeated work disappears. Inconsistency between teams is reduced. Decisions become more consistent over time because they draw from the same governed source.
Residency
Where your data lives is a property of the product.
Your data is isolated at the infrastructure level, not just by the application code that sits above it. For region-locked deployments, the database itself prevents your data from crossing the boundary you set. The constraint is structural - there is no setting an operator can flip to override it.
Compliance is what the architecture does, not what an audit hopes to find.
Constans
Multi-tenant cloud, hosted by us. Each tenant's data is isolated at the infrastructure level.
Constans Regional
Hosted by us. Your data is held in the jurisdiction you choose.
Constans Edge
The data plane runs in your own cloud. Constans doesn't keep a copy. The platform interacts with it through a narrow, audited surface.
Encryption in transit and at rest, full export, and full deletion apply across all three. Regional and Edge deployments are available for regulated rollouts by arrangement.
Operational guarantees
Infrastructure-level assurances.
Data isolation
Each tenant's data is isolated at the infrastructure level. Nothing crosses a boundary it wasn't given. Constans Regional and Constans Edge are fully supported.
In the tools you already use
Use the web app, Slack, or any MCP-compatible AI agent. Email-based ingestion from Microsoft 365 or Google Workspace is opt-in, scoped by queries you control, and revocable at any time.
Configuration control
Constans supports organisation-level configuration, including provider selection and governance rules.
Data export
All data can be exported at any time. Full deletion is supported on request.
Get Started
Introduce Constans into your organisation.
Reduce repeated work. Improve consistency. Ensure decisions hold over time.