# BIM and IFC Branch Use this branch only when the user explicitly requests IFC, BIM-like semantics, or asks whether the showcase can replace BIM. ## Claim Levels - `Web showcase`: CAD-derived visual model; never BIM replacement. - `Massing/LOD100-150`: approximate floor/wall/structure visualization. - `IFC/BIM proof`: IFC entities, storeys, containment, properties, and geometry validation exist. - `BIM replacement candidate`: require discipline-specific semantics, openings, spaces, quantities, materials, classifications, georeferencing, coordination, and human review. The bundled proof script alone does not reach this level. ## Generate and Validate Run: ```bash python3 scripts/build_ifc_poc.py \ --spec outputs//building_spec.json \ --out-ifc outputs//_proof.ifc \ --out-report outputs//_proof_report.json \ --out-notes outputs//_proof_notes.md \ --vendor-dir work/vendor --validate-geometry ``` Require schema validity, storey/spatial containment, `IfcWall`/`IfcColumn`/`IfcBeam`/`IfcSlab` counts, property sets, and geometry results. Explain every geometry failure. When Blender cannot import IFC directly, run `extract_ifc_meshes.py` and render with `render_ifc_meshes_blender.py`. Do not imply that a rendered IFC proves production BIM completeness. Always list remaining gaps: joins, openings, doors/windows, rooms/spaces, quantities, materials, classifications, levels, georeferencing, MEP, and discipline coordination.