The asset passport
Everything known about one physical thing, in one place.
A passport is not a document viewer. It is the current answer to what an asset is, how it got there, what it depends on, and whether that account can be trusted, assembled from the events rather than stored as a summary.
Opening 2147
opening
Current state
- doorType
- WD-3
- size
- 3'-0" × 7'-0"
- fireRatingMin
- 60
- room
- Pharmacy 1120
- electrified
- true
Relationships
- Door D2147Ahas door
- Frame F-2Ehas frame
- Hardware Set H21uses hardware set
- Wall Type WT12located in wall type
- Card Reader AC-17connected to
- Electrical Powerrequires
Identity
Permanent UUID, aliases over time
History
Every event, in order, chained
Evidence
Source document and page per assertion
Approvals
Who accepted which state, and when
Dependencies
What breaks if this changes
Verification
Whether the record is intact
Why the structure does not change
A door has a fire rating and a hardware set. An air handler has an airflow and a filtration class. The kernel knows neither, because asset kinds and payload fields are open strings rather than a schema it owns.
That is why the passport looks the same across all five. The sections are properties of having a history, not properties of being a door: identity, state over time, evidence, dependencies, and whether the record verifies.