ATLAS · REALITY SERIES · 03
One purchase. Seven digital copies.
A fuel purchase happens once in the real world. Digitally, the same event can reappear as a receipt, bank transaction, card statement, accounting entry, expense record, vehicle cost and tax evidence.
ONE REAL EVENT
The software copies are not the purchase.
Imagine an illustrative €87.34 fuel purchase. The car is filled once. Money changes hands once. Yet the digital traces can be distributed across several systems.
Receipt
Evidence of the purchase.
Bank transaction
Evidence of the payment.
Card statement
Another payment projection.
Accounting entry
Financial projection.
Expense record
Employee or trip projection.
Vehicle cost
Fleet projection.
Tax evidence
Compliance projection.
Seven digital objects can therefore point back to one real-world event.
THE HIDDEN WORK
Today, people and integration logic reconstruct that relationship.
Someone matches the receipt to the payment, assigns the accounting meaning, links the trip or vehicle, checks tax relevance and resolves exceptions. The difficult part is not reading seven fields. It is recognizing that different records refer to the same event and deciding what each record means.
THE REALITY-LAYER VIEW
Start with the event. Derive the views.
ATLAS models the real-world event as the shared reference point: identity, time, participants, amount, source, evidence, relationships, uncertainty and authority stay connected. Accounting, fleet, tax, AI and human interfaces can then receive purpose-specific projections.
Accounting projection
What must be booked, with source and evidence.
Fleet projection
Fuel cost and vehicle context.
Tax projection
Only the facts and evidence relevant to tax treatment.
Human projection
What happened, what is known and what still needs a decision.
THE IMPORTANT DISTINCTION
Evidence is not the same thing as reality.
The receipt can be evidence. The bank transaction can be evidence. Neither has to become the sole owner of the event. If sources disagree, the disagreement remains visible instead of being silently flattened into a convenient copy.
THE SAME PATTERN IS EVERYWHERE
A purchase is only the smallest example.
- One customer appears under different identifiers in CRM, ERP, support and banking.
- One delivery appears as order state, shipment state, email, tracking event and invoice context.
- One building appears as CAD, BIM, cost plan, maintenance record, sensor state and permit documentation.
- One project change appears in a drawing, task system, email thread, schedule and cost forecast.
THE VALUE
Less reconciliation. More reusable context.
If different projections remain connected to the same underlying event, software and AI can work with context that does not have to be rebuilt from scratch every time. The measurable business effect still depends on the actual process, baseline and qualified implementation.
BOUNDARY
One reality does not mean one unrestricted database.
Visibility, privacy, source authority and change authority remain separate. A tax projection does not automatically gain access to everything the fleet projection knows, and a display projection does not gain authority to modify the underlying state.
REALITY SERIES
From the human interface to the duplicated event.
The previous article showed the human translating between systems. This article shows what that human is often translating: several software records that refer to one real-world thing or event.