Govern every decision
your organisation makes.
Your organisation runs on decisions - made in Slack, email, and conversations, then scattered and forgotten. Constans captures them where they happen, governs them with human confirmation, and answers from them every time after.
No new system to roll out. No behaviour change required.
The problem
Decisions live everywhere.
Nowhere holds them.
"We made that call last quarter. Why are we discussing it again?"
Decisions get debated, resolved, then quietly forgotten when the people who made them move on. The same conversation comes back six months later, with no one confident enough to point at the answer.
"The person who decided that has left. Nobody remembers the reasoning."
Institutional memory walks out with key hires. Reasoning becomes lore, then myth. New people inherit the conclusion without the context that justified it.
"Our internal AI confidently answered with something we never sanctioned."
AI assistants arrive inside organisations faster than the governance to anchor them. Confidence without provenance is exposure - to customers, regulators, and auditors.
Pure automation is too risky for the decisions your organisation has to live with. So Constans is collaborative AI: the system proposes, your people confirm, and every answer your organisation gives is one a human has stood behind.
The system
A governance brain
that sits inside
your organisation. A governance brain that sits
inside your organisation.
Constans takes the governance signals your team sends it - from the web app, in Slack, by email, as document uploads, or through MCP - and turns them into a governed body of decisions. When you're ready, optional mailbox monitoring catches the decisions made in normal correspondence too. Scoped to the whole org, a department, a project, or a single team. Sentinel watches the whole picture, surfacing patterns that cross those boundaries.
Ingestion
Built around what your team sends to it.
- The Constans web app
- Slack via @constans mention or slash command
- Per-scope email addresses
- Uploaded documents and meeting notes
- AI agents and tools via MCP
Optional, when you're ready: passive monitoring of designated Workspace or M365 mailboxes.
Governance
Signals become governed knowledge.
- Signals with governance shape are distilled into proposed decisions
- The right person reviews and confirms
- Confirmed decisions become canon
- Scoped: org, department, project, or team
Reasoning
Anyone with permission can ask.
- Ask in Slack, by email, in the web app, or through your chosen AI platform
- Every answer cites its source decisions
- The AI distinguishes confirmed canon from proposed decisions, and surfaces the status of every claim
- Provenance is built in, not bolted on
Why not just a wiki?
Every tool you already have stores knowledge.
None of them govern it.
The shared wiki
It can't tell you what's still true.
Notion, Confluence, a shared drive - they hold documents, but the current decision and last year's abandoned draft sit side by side, equally confident. Knowledge goes stale silently; the space becomes a graveyard.
The AI assistant
It answers from whatever it finds.
A general chatbot or bolt-on search retrieves fast and sounds certain - but it draws on whatever it can reach, sanctioned or not, current or not, with no provenance and no human in the loop. Confidence without governance is exposure.
The people who know
It walks out of the building.
Asking the person who decided works right up until they're in a meeting, on leave, or gone. The reasoning lives in a head, not a system. When it leaves, so does the answer.
All of them hold knowledge. None of them govern it - human-confirmed truth, provenance on every answer, the gap captured when something is missing, drift caught before it costs. Once a decision has to be answered for, storing it was never the hard part.
The loop
A question is asked.
If governed knowledge exists, Constans answers immediately. If it doesn't, the system identifies the gap, routes it to the right expert, validates the answer, and remembers it for next time.
The same question is never solved twice.
Query
Question enters the system.
Answer
Answered from canon instantly.
Detect gap
Knowledge missing.
Route to expert
Sent to the right expert.
Capture and validate
Validated and added to canon.
Answer next time
Answered automatically.
Query
Question enters the system.
Answer
Answered from canon instantly.
Detect gap
Knowledge missing.
Route to expert
Sent to the right expert.
Capture and validate
Validated and added to canon.
Answer next time
Answered automatically.
Sentinel - Continuous oversight
Policy drift doesn't announce itself.
Most knowledge systems wait to be asked. Sentinel watches the body of decisions as it grows and raises its hand when something needs a human's attention, before anyone thought to look.
Conflict
When two answers can't both be right.
Two teams settle the same question different ways. Constans catches the contradiction and surfaces it to the scope that owns the call - before it reaches a customer, a regulator, or a board paper.
Drift
When practice quietly drifts from policy.
Decisions diverge from agreed policy one small call at a time, until the gap is structural. Constans flags the drift to the people accountable for the policy - while it's still a correction, not a crisis.
Convergence
When the same answer is found five times over.
The same conclusion gets reinvented in different corners of the org. Constans spots the pattern and surfaces it for promotion into shared canon - so it's decided once, for everyone.
Governance alerts arrive with evidence.
Each alert lands with a category, a confidence score, and the evidence the system used to raise it. The human accountable for the scope decides what happens next - acknowledge, propose a decision, or suppress.
Risk accumulation
Multiple small issues compounding into a structural concern at the scope above them.
Policy drift
Decisions diverging from a stated parent constraint or guardrail, one small call at a time.
Coverage gap
A required control - security review, audit, sign-off - that has not been evidenced.
Emerging pattern
A signal forming across decisions that sits below the threshold for conflict or drift, but is consistent enough to surface for early review.
Real alerts from a synthetic organisation.
Constans surfaces. The call always stays with the human who owns it.
Morning briefing
Every morning, your organisation starts from the same understanding.
Instead of discovering issues through meetings, email chains, or chance conversations, Constans summarises what changed overnight.
Each leader sees only the scope they govern: the team lead sees their team, the practice head sees the engagements beneath them, and the CEO sees the firm.
Today's briefing
Practice scope
- 3 decisions confirmed overnight
- 2 policy drift alerts to review
- 1 question promoted to canon
- 4 knowledge gaps closed
Illustrative example.
Activity
What moved yesterday.
New decisions confirmed. Canon updated. Questions answered. Knowledge gaps closed.
Signals
What needs attention.
Policy drift, risk accumulation, conflicting guidance, unanswered questions, and decisions awaiting validation.
Scope-aware
Every leader sees what they govern.
Briefings follow the same scope boundaries as the system. Nothing surfaces outside the scope it belongs to.
The signals do not wait for your stand-up. They are in the right inbox before the day begins.
Enterprise trust by design
Designed for accountable leaders.
Managing partners, practice leaders, risk and compliance, knowledge leaders, and the people responsible for deploying AI inside the organisation.
Provenance on every answer.
Every response cites the decisions it draws on. Confirmed decisions name who confirmed them. Proposed decisions are flagged in the answer.
Scope-bounded by design.
Users see only what their scope governs. Cross-scope access is explicit and audited.
Audit trail, end to end.
Every read, confirmation, and change is logged with timestamp and actor. Exportable for compliance.
Your AI. Your governance.
Anthropic, OpenAI, Gemini, or a self-hosted endpoint - your key, your provider, your terms. Constans is the governance layer; the model stays your choice.
Tenant isolation. Data stays yours.
Each tenant is isolated at the infrastructure level. Constans never trains on your content; default providers don't either. Full export and deletion on request; DPA available.
Deployment can be shaped around your organisation's governance, data, and model requirements. How residency is enforced
For consultancies and advisory partners
Your clients should not leave with a PDF.
Every engagement creates valuable organisational intelligence - decisions, rationale, risks, trade-offs, principles, and operating judgement.
Most of it is left behind in slide decks, email threads, workshop notes, and handover documents.
Constans turns engagement knowledge into a governed system your client can keep using. Projects become lasting capability.
From recommendations to operating memory.
Capture the reasoning behind the work, not just the final deliverable.
From handover to continuity.
Give clients a governed system that preserves decisions, context, and expert judgement after the engagement ends.
From project to platform relationship.
A pathway for recurring advisory, governance, and implementation work around the client's decision system.
Get Started
Start a governed pilot.
A 30-minute conversation is the right starting point. We'll walk you through the pilot engagement - six to eight weeks, fixed scope and outcomes - and whether Constans fits your governance setup.