Govern the shared library. Never silently rewrite project history.
Stable identity
Concept identity survives across revisions. Each published revision is a separately addressable, immutable snapshot.
Scoped knowledge
Global Concepts are administered centrally or by their authorized owner. Project-specific data can map to them without altering their definitions.
Validated relationships
Directed parent/child edges, typed relations, root eligibility and cycle constraints are evaluated against versioned business rules.
Traceable change
Every proposed correction records rationale, source evidence, reviewers and impact on dependent Use Cases.
Separate identity, revisions, evidence and usage
This proposed logical model avoids conflating a global Concept with its current version or a project's local interpretation.
Identity
concept_id, stable URI, responsible authority, semantic domain, global/project scope.
Revision
Revision ID, state, classes/properties, rule set version, source mappings, rationale and timestamps.
References
Use Cases refer to explicit revision snapshots rather than an unqualified “latest” revision.
Create a new Concept
Example: “Heat Pump” is not represented by a reusable Concept, but appears in a manufacturer catalog or an IFC project model.
Correct an existing Concept
Example: a published “Door” Concept is missing a property mapping found in an updated classification or IFC schema source.
Versioned knowledge without forced migration
| State | Meaning | Allowed behavior |
|---|---|---|
| Draft | Editable candidate revision | Admin review and pilot tests; not a generally approved production rule. |
| In Review | Target governance state | Quality checks, source/impact review, rule validation. |
| Published | Released, immutable revision | Available to authorized Use Case composition and consumers. |
| Deprecated | Discouraged for new work | Existing pinned Use Cases continue to resolve their snapshots. |
New data sources enrich knowledge through proposals
Record at least source identifier, server identity, original URI/GlobalId, import timestamp, model/release version, mapping method, transformation version and licensing/access constraints. Resolve potential duplicates by alignment before creating new shared nodes.
A published Concept is a dependency, not a moving target
Snapshot stability
A project Use Case pins Concept revision IDs and rule-set revisions relevant to its creation.
Impact analysis
Before publishing a correction, report affected Use Cases, incompatible mappings and newly available properties.
Controlled upgrade
Propose migrations and compare old/new results. A BIM Manager accepts project changes within their permissions; global definition remains admin-controlled.
Keep authoring authority separate from project use
| Action | Administrator | BIM Manager | Standard User |
|---|---|---|---|
| Create or correct global Concept | Allowed | Not allowed | Not allowed |
| Review/publish Concept revision | Allowed | Not allowed | Not allowed |
| Register federation/source adapter | Allowed | Use approved sources | Use via references |
| Compose project Use Cases | Allowed | Allowed | Not allowed |
| Assemble reference Use Cases into project IDM | Allowed | Allowed | Allowed |
| Operate backups and global policies | Allowed | Not allowed | Not allowed |
Future: Tenant ownership, provider-managed selective disclosure and fine-grained resource permissions must be enforced across APIs, federated queries, search indexes, caches and exports. This is not part of verified 7.8.53 security enforcement.
Current pilot versus target specification
| Capability | Maturity | Evidence / limitation |
|---|---|---|
| Concept editor with revision-oriented flow | Pilot | 7.8.41 module and observed Draft/Published snapshots; complete governance workflow not yet demonstrated. |
| Stored rule reading and direct child checks | Verified pilot | 7.8.52/53 tested with “Heating Systems” → “Boilers” allowed; “Accessibility” blocked in Draft mode. |
| Published-mode production rule enforcement | Not verified | Draft pilot rules are not production approval; publication validation remains to be demonstrated. |
| REQUIRES / PRECEDES / full root and cycle validation | Planned | Not implemented by direct 7.8.53 pilot checks. |
| Impact audit and automated source change proposals | Planned | Target governance capability. |
| Federated concept authority and tenant permissions | Future architecture | Documented design only, not deployed. |
The publicly deployed documentation describes intent and evidence; it must not be used as proof that every UI control, API or validation rule is in production.