The platform
Six layers between a document and a decision you can trust.
Records enter at the top as files. They leave at the bottom as answers about physical things. Everything in between exists to keep the connection between the two provable.
The stack, top to bottom
Ingest
Drawings, specifications, RFIs, submittals, revisions, purchase orders, field records.
Extraction produces structured assertions, each carrying a fingerprint of the document it came from.
Identity
Permanent asset IDs, aliases, entity resolution across revisions.
A renumbered door is the same door. Labels change; identity does not.
Temporal graph
Assets, typed relationships, events, dependencies, causality.
Facts are intervals with an opening and a closing revision, so any past state stays reconstructible.
Provenance
Source fingerprints, append-only history, verification, project root.
Every assertion carries where it came from, and the record can prove it has not been altered.
Intelligence
Reconstruction, change detection, impact traversal, staleness, decision trace.
The questions previously answered by a person reading five systems at once.
Applications
Design, coordination, procurement, installation, operations.
Each consumes the same graph. None of them owns it.
Leave here: answers about physical things, provable
Discipline generic
The model knows nothing about doors.
Assets, aliases, temporal relationships, chained events, staleness, impact traversal: every mechanism above is discipline generic. The event vocabulary is open and payloads are opaque to the kernel, so recording a switchboard requires no change to the core.
Doors and hardware went first because that is what the extraction pipeline already reads. That is a statement about where the data came from, not about what the model can carry.