Welcome to the Olly architecture review
You are reading a private build of the Olly documentation site, prepared specifically for the EY review engagement. Thank you for taking the time to read it.
Where to start
The fastest way in is the Recommended Reading Order - a curated, sequential path through the docs that takes around 1.5 hours end to end. Each entry on that page maps explicitly to one or more of the seven dimensions in the review framework, so you can see what every page is meant to evidence. The framework itself is at /ey-review/framework; the scope and NDA terms are at /ey-review/scope.
Engagement objective
Olly is building a regulated health-insurance and clinical-triage platform for the UK market. Before the platform enters its next funding and regulatory phase, we want an independent, external read on whether the architecture, the engineering patterns, and the documentation itself are mature enough to support the business model we have committed to. The objective of this engagement is not a feature audit and not a code review - it is an architectural and process critique, framed by the seven dimensions listed in the review framework.
What you are looking at
This build exposes a curated subset of the full internal documentation. You can see:
- Architecture - C4 levels 1-3, container views per capability, dynamic process flows, and the deployment landscape.
- Domain - the business ontology, the InFORM alignment, and how Olly's domain language maps to the policy-claims-care-triage capabilities.
- Process coverage - the InFORM-aligned coverage map showing which insurance value-chain processes are implemented, partially implemented, or out of scope.
- Designs - the design records (ADR-style) covering significant decisions: auth model, PII walls, event topology, ontology projection, and notifications.
Internal-only material - source code, raw schemas at column granularity, the triage algorithm internals, infrastructure topology, and partner contracts - is not included in this build. The full list of inclusions and exclusions is on the scope page.
How to navigate
We suggest the following reading order. Start with the review framework so you know what we are asking you to assess. Then read Architecture top-down (system context, then containers, then process flows) before going into Domain and Designs. The process coverage map is the best single page to answer the use-case completeness question. Each design record is self-contained, so you can dip in and out.
Confidentiality
The content of this build is confidential to Olly and EY under the NDA dated for this engagement. Every page is watermarked with the engagement date and a unique page identifier; please do not share screenshots externally. See the scope and NDA page for the full notice.
Next: review framework - the seven dimensions you will be assessing against, the severity rubric, and the deliverable specification.