How do you build a synthetic enterprise that behaves like a real one?
Metrolane is more than a set of sample records.
It is a synthetic company built across independent business systems, with its own customers, employees, products, orders, documents, integrations, enterprise identities, history and intentional inconsistencies.
This Guide explains how those pieces fit together — from source systems and canonical data, through documents and retrieval, to Day-0, business time, simulation, EKA and future enterprise agents.
Learn with the Guide
Follow the architecture step by step. Open real Metrolane examples without leaving the lesson.
Inspect with the Explorer
Browse the frozen Day-0 enterprise freely. Move between systems, canonical records, documents, scenarios and data journeys.
The Journey
- 01–03Build the companyDAY-0
Start with one company operating through many independent systems.
See why business actions, IDs and cross-system handoffs remain source-native.
- 04–05Turn data into enterprise knowledgeDAY-0
Follow source data through extraction, mapping, entity resolution and lineage.
Then add documents, knowledge and governed retrieval.
- 06–07Freeze it and prove itDAY-0
Understand Day-0 and why provenance, access, validation and reproducibility matter.
- 08–10Make the enterprise movePHASE 10
Create a runtime estate, give it its own business clock, and let real business processes progress through time.
- 11–12Put AI on topEKA V1.1 DIRECTION
See how EKA can reason over structured enterprise facts and retrieved knowledge — and how future agents could eventually act through controlled enterprise interfaces.
- 13See the whole systemALL LAYERS
Bring the architecture together in one view.
Status legend
- DAY-0
- Part of the frozen, inspectable reference enterprise.
- PHASE 10
- Runtime architecture for making Metrolane progress through simulated business time.
- FUTURE DIRECTION
- Planned direction whose detailed implementation contract is not yet frozen.
- EKA V1.1 DIRECTION
- EKA is an established V1.1 product direction built on the existing Day-0 enterprise and retrieval foundations. Its final orchestration/tool contract is still a separate design activity.
You do not need to understand the database schema to understand Metrolane.
Start with the business idea. Open the real examples when you want to see what it looks like inside the enterprise.