What AI does: Summarises, explains, retrieves, drafts understanding.
Human role: Human interprets.
Example: Summarise account risk factors
Platform map
Four systems + Value Ledger + integrations boundary.
Ops loopDATA → LEARN
STAGE · DATA
Connect systems of record. Owner and output are named in How it works.
Intelligence System — annotated teaching instrument. Any metric chips are ILLUSTRATIVE EXAMPLE — not a Xevrion customer result.
Loop on the platform
DATA connects systems of record. UNDERSTAND normalizes entities and owners. FIND surfaces opportunity and risk. DECIDE compares scenarios. ACT executes with approval or policy. VERIFY confirms landing. MEASURE records causal value. LEARN sharpens the next cycle.
Architecture (honest)
PRODUCT CAPABILITY Marketing hosts (parent, ops, portal) are separate from authenticated API runtime. Data planes connect to your systems of record; write-back requires scopes you approve.
EVIDENCE_PENDING: Deep infrastructure diagrams beyond this high-level summary — interim: examine Security, AI, Integrations, and Docs.
Parentxevrion.co.ukBrand landing
Opsops.xevrionMarketing · Buy Ops
Portalportal.opsChooser
APIapi.xevrionRuntime · auth
FE · SitesParent · Ops · Portal
FE · ConsolesAPI console · customer
BE · PaymentsMonzo · standing order
BE · CoreOwners · queues · audit
Shared core — owners · queues · definitions · settlement
AI on the platform
What AI does: Proposes actions with reasons and confidence.
Human role: Human chooses.
Example: Recommend next best opportunity focus
What AI does: Prepares an action; executes only after approval.
Human role: Human approves or rejects.
Example: Queue CRM update; send only when approved
What AI does: Executes narrowly within explicit customer-configured policy.
Human role: Human defines policy; monitors.
Example: Auto-assign task if rules match
Autonomy is a dial, not a surprise. AI assists and recommends. It acts with your approval — or within policy you set. Humans remain accountable for outcomes.
Security boundary
Edge TLS
Cloudflare Workers · host separation · encrypted in transit
Host boundaries
Parent · Ops marketing · Portal · API — virgin separation
Auth plane
Portal/API authentication — marketing host is not the runtime
Settlement honesty
Monzo setup · standing order · portal open ≠ payment confirmed
Claims discipline
No fake ISO/SOC theatre · labelled ILLUSTRATIVE examples only
Trust Architecture — restrained near-monochrome layers. What we operate — not badge spam.
Is Xevrion a CRM replacement?
No. CRM remains system of record. Ops connects, focuses, decides, acts with control, verifies, and measures.
Do I need all four systems?
No. Start where the pain is; expand on the same loop and ledger.
Where do my systems of record stay?
With you. Integrations respect scopes; write-back behaviour is documented.