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 02 of 13DAY-0

One company. Many systems. No forced collapse.

Metrolane is one enterprise, but its operational systems do not share one source schema.

CRM remains CRM.

ERP remains ERP.

Documents remain Documents.

Each system keeps its own IDs, terminology, status values and source-native structure.

Understand

The same business thing can appear several times

Suppose Metrolane deals with one customer.

CRM may have:

AccountACC-2026-900001

ERP may have:

CustomerCUST-2026-000002

Those can refer to the same enterprise organization.

But they are still different source records owned by different systems.

The source system keeps its own language

A source model may contain concepts such as:

CRMAccountOpportunityLead
ERPCustomerSales OrderInvoice
HRWorkerEmployment
DocumentsDocumentVersionFolder / Space

Metrolane does not rename all of those records into one universal source schema.

Instead, it preserves them and builds shared enterprise semantics above them.

See it in Metrolane

Kestrel

Kestrel Auto Retail currently appears through three source records:

CRM AccountACC-2026-900001Kestrel Auto Retail Private Limited
CRM AccountACC-2026-900002Kestrel Auto Retail
ERP CustomerCUST-2026-000002Kestrel Auto Retail Private Limited

The enterprise layer resolves them to

Organization · Kestrel Auto RetailORG-000012
Important distinction

Source ID and canonical ID are different identities

  • ACC-2026-900001 is a CRM source key.
  • CUST-2026-000002 is an ERP source key.
  • ORG-000012 is a canonical enterprise identity.

They are not interchangeable.

The canonical identity does not overwrite or replace the source identities.

Why preserve source quirks?

Because source-specific meaning matters.

A CRM field can mean:billing country
while a canonical field might eventually mean:legal domicile

Those are not automatically the same concept.

If Metrolane copied a source value into canonical data simply because the names looked similar, it could create a clean-looking but semantically false enterprise view.

See it in Metrolane

Source-native context

Open:

ACC-2026-900001

The visitor can see:

  • CRM Account
  • source-native status
  • source-native account type
  • source-native billing country
  • same-system CRM relationships
  • cross-system link
  • canonical resolution
Go deeper
Four identity layers to keep straight

A useful mental model is:

  1. 1. Source record identityCRM Account ACC-2026-900001
  2. 2. Operational linkCRM Account → ERP Customer
  3. 3. Canonical identityORG-000012
  4. 4. Canonical relationshipsrelationships between shared enterprise entities/objects

These layers may connect, but they mean different things.

Chapter takeaway

  • Metrolane is one company, not one source schema.
  • Each operational system keeps its own identity and semantics.
  • Canonical identity sits above source identity rather than replacing it.
  • This separation is what makes cross-system reasoning trustworthy.