Context
ISO 19650 is a family of standards covering 'information management using building information modelling'. Many organisations sign up to '19650 compliance' without a clear picture of what they're committing to. The 19650-1 (concepts and principles) and 19650-2 (delivery phase) parts have specific, structural requirements about CDE behaviour that go well beyond labelling files.
ISO 19650 is process-led. It tells you how to manage information, not which tool to buy.
Explanation
At a minimum, ISO 19650 compliance for a CDE means three structural properties:
Information containers
Every information element is a named, versioned, persistent unit. Each has metadata: status, suitability, revision, originator. The container is the atomic accounting unit; not the file, not the folder.
Suitability status workflow
Containers move through Work in Progress (only the originating task team can edit), Shared (visible to the project team for coordination but not finalised), Published (formally approved and baselined) and Archived (retained for the record). Movement between states is workflow-driven and recorded.
Single source of approval
Only the CDE can grant a container its formal status. Email approvals, side-channel sign-offs, decisions captured in meeting notes: none of these count. If it isn't in the CDE with the right status, it isn't approved.
Weaver enforces these structurally. You cannot bypass the workflow because there is no parallel system to bypass it through. Audit trails fall out for free; ISO 19650 progress reports are queries against the underlying knowledge graph. Compliance becomes a property of the data model, not a process for people to remember to follow.