Day-0 Guide
General enterprise visibility, with access to the enterprise's general document spaces. No HR or payroll compartment access.Viewing as Enterprise Reader
Chapter 13 of 13ALL LAYERS

One enterprise story, from source systems to AI

Metrolane can now be understood as a set of connected layers.

Each layer solves a different problem.

The value comes from keeping those boundaries explicit.

The complete mental model

HUMANS · EKA · FUTURE AGENTS

read

CANONICAL ENTERPRISE

projection

MAPPING / RESOLUTION / LINEAGE
RAW / INGESTION
CONNECTORS
SOURCE SYSTEMScommands / handlers · events · relays
Documents / Knowledge
versionsaccessapplicabilityretrieval→ EKA / grounding
Phase 10 runtime
runtime estateenterprise clockplansbusiness-time queuesuppressionreplay

Read the architecture in four questions

  1. 1. Where did the business fact originate?Look at: source systems · commands · events · operational links
  2. 2. How did it become enterprise knowledge?Look at: connectors · raw ingestion · mapping · resolution · survivorship · canonical · lineage
  3. 3. What does the company know beyond structured records?Look at: documents · versions · relationships · access · retrieval
  4. 4. How does the enterprise move and how can AI participate?Look at: runtime estate · business time · Phase 10 · EKA · future agents
See it in Metrolane

Follow one architecture path

A visitor can move through:

The identity path

CRM Account ACC-2026-900001

resolution

Canonical Organization ORG-000012

provenance

Data Journey / lineage

related enterprise context

documents / scenarios / relationships

The business-process path

CRM Opportunity OPP-2026-900001

operational handoff

ERP Sales Order SO-2026-000001

extraction / mapping

canonical enterprise visibility

Day-0

a frozendeterministicinspectablereference enterprise

This is what the current Day-0 Explorer shows.

Phase 10

a runtime copyprogressing throughsimulated business time

This is how the enterprise can evolve without mutating the frozen reference.

EKA

an LLM-driven solutionusing structured enterprise contextand governed retrieval

It is one application over Metrolane, not the definition of Metrolane itself.

Future agents

AI participantsthat may eventually actthrough controlled business interfaces

They should not receive a parallel mutation path outside enterprise rules.

Important distinction map

Before leaving the Guide, the visitor should be able to keep these pairs separate:

  • source≠canonical
  • operational link≠entity resolution
  • entity resolution≠survivorship
  • Cross-System Journey≠Data Journey
  • document exists≠document is retrieval-ready
  • Day-0≠runtime
  • business time≠technical time
  • OccurrencePlan≠ExecutionPlan
  • Semantic Search≠EKA
  • EKA≠future action-capable agent

Final takeaway

  • Metrolane begins with realistic source systems.
  • It builds shared enterprise meaning without erasing source identity.
  • It adds documents and governed retrieval.
  • It freezes a reproducible Day-0 reference.
  • Phase 10 gives that enterprise time and behavior.
  • EKA adds LLM reasoning over enterprise knowledge.
  • Future agents may eventually participate in enterprise work through the same controlled business interfaces.

Final invitation

At this point the visitor has enough context to leave the guided path and browse freely.