gemeinwert / home

Buildings last fifty years. Software platforms don’t.

Every building creates issues, approvals, requirements, model references and handover records. Today those records are scattered across vendor platforms, email threads and project folders that disappear long before the asset reaches mid-life.

Gemeinwert is the recognizable DACH brand for BIM-CVP, the Common Value Protocol: a signed, portable record layer for openBIM coordination.

What the protocol does.

BIM-CVP does not replace authoring tools, CDEs or buildingSMART standards. It records the coordination work around them: who created an issue, which IFC element it refers to, what changed, who approved it and which requirement was checked.

BCF topics, comments and viewpoints become signed coordination events.
IFC, IDS and document payloads stay normal files and are referenced by hash.
Project identity, authorship and audit history remain portable across tools.

If BIM or Nostr is new to you.

BIM is the construction side: the building as structured data, not just a drawing. IFC names the objects, BCF carries coordination issues, IDS defines information requirements and ISO 19650 frames responsibility and approval.

Nostr is the record side: a person or tool signs a small event, publishes it to relays and lets every reader verify the author, timestamp and referenced file hash. BIM-CVP connects both worlds without changing the BIM standards.

Why it matters.

Coordination is an economic knowledge problem. Architects, engineers, contractors, operators and owners each know something different. A single platform cannot own that knowledge without creating lock-in and information asymmetry.

BIM-CVP follows the Austrian economics frame: value is contextual, discovered through exchange and tied to responsibility. If a project claim matters, it should be signed by the person or system making it.

The standards frame.

buildingSMART International stays the core reference. IFC describes the model, BCF describes coordination, IDS describes machine-checkable requirements, bSDD keeps terms stable and openCDE defines integration boundaries.

buildingSMART frame International openBIM standards and how BIM-CVP maps them to events. BCF events Detailed topic, comment, viewpoint and audit mapping. Alice, Bob, Max Worked example for signed project records and data sharing.

Current entry points.

The current tools focus on identity, project setup and key management. The BCF coordination interface will use the same protocol model.

Create identity Generate a project identity and role. Project admin Create a project and invite participants. Key management Manage keys and profiles directly. BIM-CVP protocol English developer and standards framing.