The question is typed into IntelliX on a Friday afternoon. “What’s our cash position this week?” Six words from a business owner with a payroll run landing in forty-eight hours. The answer has to be right, and it has to arrive in time, and it has to be defensible if anyone asks.
On a generic AI platform, that question goes into one model, one inference, one answer. The model will give you a confident number. It may or may not match your real books. You find out at payroll time which version was correct.
On XIntelliSync, the same question runs through four systems in composition before the answer lands. This is the six-step trace — every phase, every gate, every verified agent, every piece of evidence persisted.
The six-step trace
Tap. Decompose. Pull. Watch. Gate. Commit.
Every IntelliX answer runs these six steps. They run fast — end-to-end median under two seconds on a typical question. They run every time. Halt is the default. Commit is what the answer earns.
Step 1
The tap. One question. No template.
You type "what's our cash position this week?" into IntelliX. No prompt engineering. No form fields. No "select a report type." One natural-language question from a business owner who needs an answer before their Friday payroll run.
What it produces
The question hits the conversational runtime. Your tenant scope, your tier, your timezone (Australia/Sydney), your organisation id — all resolved before the first phase fires.
IntelliX Omega · phase orchestration begins.
Step 2
Omega decomposes. 29+ architectural layers route the question.
The question is not a single AI call. IntelliX Omega breaks it into the reasoning phases it actually needs — query intent, temporal scope, data domains required (banking, AR, AP, payroll), risk profile of the answer, trust tier of the user. Different questions take different paths through the 388+ engineered phases.
What it produces
"This week" resolves to your local financial week. "Cash position" requires fusion across bank feeds, outstanding AR, committed AP, and the upcoming payroll run. Each of those is a separate data domain with its own XAVS-verified agent.
IntelliX Omega · 29+ layers · phase decomposition routes the question correctly.
Step 3
Verified agents pull real data. No mocks. No synthesis.
Each data domain is handled by a XAVS-verified agent — the same gate we wrote Spoke #5 about. Bank balance agent reads via Basiq. AR aging agent reads your invoice ledger. AP aging agent reads your supplier ledger. Payroll preparation agent reads the next run's committed cost. Each agent is V1-certified on the ten dimensions, or it does not run on your data.
What it produces
Every agent filters by your userId and organisationId. Every read is scoped. Every return is the real state of your real books — not last week, not averaged, not hallucinated.
XAVS · four V1-certified agents deliver four datasets into the reasoning frame.
Step 4
Horizon watches every phase while it fires.
As Omega routes the question and the agents pull their data, Horizon is observing every phase in real time. Per-phase latency. Output schema conformance. Agent calibration against ground truth. Input distribution against each agent's baseline. If any phase degrades — a bank feed stalls, an agent's confidence calibration slips beyond threshold, an output schema breaks — Horizon halts the pipeline and pages for supervision instead of letting a degraded answer compose.
What it produces
Horizon sits parallel to the execution path. It does not slow the answer down. It provides the "is this phase still behaving the way XAVS verified it" signal that catches drift before it reaches your ledger.
Horizon · 388+ phases observed · drift signal green · composition continues.
Step 5
XGVS gates run before the answer commits.
Before the composed answer is rendered to you — before a number appears on your screen — the relevant compliance gates fire. Is the data privacy-compliant on display (no unredacted PII in the trace)? Does the cash-position figure respect your GST and BAS posting rules? Does the payroll projection honour current Fair Work rates? If any gate fails, the answer halts with an explanation — not a partial number, not a guess.
What it produces
For this specific question, the applicable gate set is a subset of the 356+ total gates — only those that apply to cash display, GST-compliant aggregation, and payroll-safe projection. Gates that do not apply stay silent. Gates that apply must all pass.
XGVS · applicable gates pass · answer cleared for commit.
Step 6
The answer lands. With the evidence trail.
You see one number. Underneath it — if you tap — you see the composition: which four agents contributed, which data sources they pulled from, which phases fired, which gates passed. One tap on an Enterprise tier expands the full trace. Starter sees the answer and the confidence band. Every tier sees enough to trust it, or challenge it, or export it to their accountant.
What it produces
The answer row writes to your dashboard. Every agent invocation writes to the XAVS runtime ledger. Every gate pass writes to the XGVS audit log. Nothing ephemeral. Nothing lost.
Answer delivered. Full trace persisted. Seven-year retention on the evidence.
Six steps. Four systems. One answer — or no answer with a halt reason. The composition is the same on every question. The only thing that changes is which agents get invoked, which phases run, and which gates apply.
The four systems, in their own words
Each system has one job. Together they compose one answer.
IntelliX Omega reasons. Horizon supervises. XAVS verifies. XGVS gates. The composition is what makes the answer trustworthy. Any one of them missing, and the guarantees weaken in a way you cannot recover at audit time.
The reasoning engine.
IntelliX Omega · 29+ layers · 388+ phases.
Omega does not answer your question — Omega decides what the question actually needs. It decomposes, routes, fuses across domains, and hands the composed result to the next system. One question, dozens of phases, one clean path.
The runtime supervisor.
Horizon · real-time observation.
Horizon is the reason drift does not reach your books. It watches every phase Omega runs, every agent XAVS certified, every input distribution. It halts before a degraded answer composes. Its job is to catch the slippage XAVS cannot see until the next re-verification.
The agent verifier.
XAVS · 10+ dimensions · 9 hard gates.
XAVS is the gate every agent passes before it sees your data. Ten dimensions scored at the certification threshold. Nine hard gates passed individually. Three trust tiers earned in order. If an agent cannot clear the gates, the question routes around it, or the answer halts.
The compliance ledger.
XGVS · 356+ gates · 34+ frameworks.
XGVS is the final check before commit. Every applicable compliance gate fires — privacy, tax, Fair Work, security controls — with citations to the exact clause. Halt is the default. Commit is what the answer earns. The audit log persists the trail your accountant can export.
Composition is the product. Not a premium feature.
Every IntelliX question runs through this composition, on every tier, every time. Starter gets the answer and its confidence band. Growth gets the contributing agent list and phase count. Enterprise gets the full trace. The composition does not get deeper at higher tiers — the visibility does. The trust architecture is the floor of the product, not a paywall.
This is why the depth exists. Twenty-nine layers is not a feature list. It is what it takes to decompose one natural question into the specific reasoning paths, the specific verified agents, the specific runtime observations, and the specific compliance gates that make an answer actually trustworthy on live business data. Less depth means a faster demo and a slower audit.
A generic AI gives you a confident answer. XIntelliSync gives you a defensible one — composed, verified, supervised, gated, and logged for seven years.
Key takeaways
- One customer question runs through four systems in composition — IntelliX Omega (reasoning) + Horizon (supervision) + XAVS (agent verification) + XGVS (compliance gates) — before the answer lands.
- Omega decomposes the question into the specific phases it needs. XAVS-certified agents pull real data in parallel. Horizon observes every phase for drift. XGVS fires the applicable compliance gates before commit.
- Halt is the default. The answer only composes when every system signals clear. Degraded answers do not slip through with no evidence.
- End-to-end latency stays under two seconds for typical questions — the composition is designed to be fast, not bolted on afterwards.
- Every answer writes three persistent trails: XAVS runtime ledger, XGVS audit log, answer history. Seven-year retention on every tier. Trace depth scales with tier — the work is the same for everyone.
The composition — questions answered.
Does running four systems in sequence slow the answer down?+
What happens if one of the four systems fails?+
Which tier gets to see the full trace?+
Can I audit a past answer?+
Why does Omega need 29+ layers? Is that not overkill?+
Who decides which gates apply to a given question?+
How is this different from "AI + compliance" platforms that just add a disclaimer?+
Can I see this composition on every answer?+
Keep reading
More of the Trust Stack.
Pillar page
AI Verification — the full overview
All four Trust Stack systems — Omega, Horizon, XAVS, XGVS — and how they compose into a single verification engine.
Read pillarSpoke · Agent verification
What V1 Certification Actually Requires
Ten XAVS scoring dimensions, nine hard gates, three trust tiers — what every agent earns before it sees your live data.
Read spokeSpoke · Gate evidence
How XGVS Gate Failures Show Up in Your Audit Log
Five concrete gate fires with the exact ledger row each halt writes — STP Phase 2, BAS, Fair Work, Privacy Act, Essential 8.
Read spokeSpoke · Runtime drift
Why AI Drift Compounds Silently on Live Data
How Horizon catches per-phase drift, calibration slippage, and distribution shift — before your books show it.
Read spokeAsk IntelliX anything. See the composition work.
From $97/month AUD. The four-system composition runs on every question on every tier. Depth of the view scales, the work does not. Built in Australia. Built for what’s next.