Platform
Policy Composer turns written policy into workflow control.
Corentis is the policy-control and evidence layer for AI-assisted regulated workflows. It converts plain-English policy into allowed actions, blocked actions, review gates, escalation triggers, and evidence requirements.
The Core Platform
A reusable control layer around the workflows that matter most
Corentis is designed to become infrastructure for governed deployment, not a one-off wrapper around a single use case. Policy Composer is the entry point: it turns written standards into operational workflow logic before customer-facing outputs or internal review.
Policy Composer
Convert plain-English policy into structured control plans covering allowed actions, blocked actions, review gates, escalation logic, and evidence requirements.
Workflow inventory
Record what each AI-supported workflow does, where it is used, who owns it, and why it matters.
Testing and evaluation
Run structured checks before release, including scenario testing, failure-mode review, and control verification.
Approval workflows
Add the right review gates for sensitive steps, with named approvers, escalation logic, and recorded decisions.
Runtime monitoring
Track live activity, exception patterns, drift, overrides, and other signals that matter in operation.
Evidence generation
Export review-ready materials that support governance, assurance, audit, and procurement processes.
Control mapping
Translate policy requirements and operating rules into practical configuration around each workflow.
Illustrative Platform Surface
A product-shaped view of policy, control, review, and evidence
This is intended to make the current platform direction easier to picture as software infrastructure rather than a set of abstract governance ideas.
Policy Composer
Plain-English policy becomes a control plan
The platform can identify the relevant policy, attach workflow constraints, and define what must be reviewed or recorded.
Controls
Review and escalation logic
Attach approval conditions, escalation thresholds, direct-send blocking, and required checks around sensitive steps.
Monitoring
Advisor guidance and runtime events
Surface policy guidance, blocked actions, escalations, overrides, and notable review activity in one operational picture.
Evidence Vault
Structured evidence outputs
Prepare review packs and persisted evidence artefacts that can be reused by governance, assurance, and audit-facing teams.
Prototype event trail
Intended to show the kind of reviewable workflow state Corentis is being built to expose.
01
Relevant policy identified for the workflow
02
Structured control plan attached before advisor action
03
Evidence artefacts prepared for Evidence Vault and export
Designed To Fit Existing Systems
Controls around the tools teams already use.
Corentis is being built to connect with CRM, case-management, workflow, and evidence repositories. The goal is to apply controls, guide users, and capture evidence inside the operating model teams already rely on, rather than forcing sensitive work into a separate tool.
Platform Stage
What exists now and what the platform is designed to become
This is intended to make the product feel legible as product infrastructure without overstating maturity.
Exists now
01
Interactive V1 demo and evidence model
The current product direction includes an interactive V1 complaints-assistant demo, defined workflow controls, illustrative evidence outputs, and sector-shaped deployment examples.
Prototype focus
02
Policy-to-control logic
The present focus is on how Policy Composer, review gates, runtime visibility, and evidence exports fit together as one product.
Designed to do
03
Reusable platform work
The aim is a repeatable control layer that can support more than one workflow rather than a bespoke wrapper around a single use case.
Near-term path
04
One workflow to wider adoption
The product is intended to land with one internally approved workflow, then extend into adjacent processes with similar governance needs.
What Serious Organisations Need
- Can we see how this workflow behaved?
- Can we turn plain-English policy into workflow rules without manual rework?
- Are the right approvals in place?
- What evidence would we show if asked to justify this process?
- How do exceptions, overrides, or escalations show up during operational use?
- How do we adopt AI without creating a new layer of operational opacity?
Why The Platform Matters
AI adoption does not need to mean blind trust or total paralysis.
Too often, teams are left with two poor options: move quickly without enough control, or delay useful adoption because no one is comfortable with the risk.
Corentis is designed to make the middle path workable at platform level: policy translated into workflow controls, human accountability kept explicit, and evidence that can travel with the workflow.
Illustrative Platform Flow
What governed deployment looks like in practice
Corentis is designed to sit around a workflow rather than replace the model or system already in use. The platform adds policy-derived controls, review points, and evidence structure that make deployment easier to manage.
Step 1
A team defines the workflow and policy source
The organisation captures what the workflow is for, where AI is being used, which policy applies, and where human oversight is required.
Step 2
Policy Composer and controls are applied
The workflow is shaped with allowed actions, blocked actions, escalation conditions, and evidence requirements before operational use begins.
Step 3
Live activity is guided and monitored
Corentis guides the operator, records blocked actions, exceptions, review decisions, and runtime alerts as the workflow operates.
Step 4
Evidence is exported when needed
Teams can generate review-ready outputs for governance meetings, internal assurance, procurement, audit, or external scrutiny.
What Corentis Adds
- configuration around the workflow, not a replacement for the underlying AI system
- review gates that can be shaped by risk level or policy conditions
- clearer visibility for operations, risk, compliance, and assurance teams
- evidence that is easier to reuse across multiple stakeholders
Review snapshot
01
Policy checks attached
02
Named review gate visible
03
Evidence ready for export