HOW IT WORKS
One foundation. Every product stands on it.
OZLILI is not a set of applications sharing a login. The difficult parts — the execution layer, the shared capabilities, the rules that govern both — are engineered once, underneath. A product is a path across them.
THE FOUNDATION
Four parts, each a plain idea before it is a technical one.
Products this unalike are one ecosystem only if something real sits under all of them. This is that thing — the same four parts described on the Global Home, expanded here.
Evidence
Evidence Engine
Collects the work, results and records behind a claim, checks them, and keeps them connected — so what you assert about a person or a team can be traced to what it rests on.
Decisions
Decision Runtime
Takes the evidence and the criteria and returns a recommendation with its reasoning attached, recorded when it was made rather than reconstructed afterwards.
Intelligence
Intelligence Layer
Models, agents, data and workflows run under one orchestration layer. It resolves in order: your own record first, then the rules that apply, then what has already been verified, and a model only once those run out.
Trust
Trust Architecture
Consent, access, retention and audit are properties of the platform rather than features bolted onto it, which is what makes the record stand up when someone asks how a decision was reached.
THE OPERATING MODEL
Build the foundation first. Reach for AI last.
The order the layer resolves in is the one genuinely contrarian thing OZLILI can say in 2026, and it governs every product built on top.
The foundation is the product
Execution, capabilities and governance are engineered once. Everything OZLILI ships stands on them rather than beside them.
Products are compositions
A product assembles shared capabilities into one path. It does not carry its own copy of your data, its own execution, or its own rules.
Known before generated
A question is answered from what the system already holds, and the rules that apply to it, before anything is generated for you.
Intelligence is a resource
Models sit alongside data, tools and workflows as one resource — reached for when the known path runs out, and the route there is kept.
Added, not rebuilt
A new product joins the same foundation. What you have already established carries into it instead of starting again.
WHAT STANDS ON IT
Different problems. One foundation underneath.
Each product solves a different problem for different people. What makes them one ecosystem is underneath: the same foundation, the same governance, the same account of what you have already established — and the foundation is built to carry the products that come after these.
The foundation is the point.
Every product here is built on the same foundation, so each one starts from where the last one got to — and what you set up in one carries into the next.