FreeCADWasmDev/docs/current/bim-ifc-backend-boundary.md

BIM IFC backend boundary

Batch: dbb80dc113c531df7634151f (2026-09-11).

Remaining business IDs:

• business-format:BIM:export:.ifc
• business-format:BIM:import:.ifc

The supplied first error reports declarationOnly: true, hasFile: true, and hasOpen: true. Callable declarations do not establish a working IFC backend. No new business acceptance was run in this editing turn.

Confirmed source anchors:

• freecad-source/src/WebAssembly/FreeCADCoreProbe/BimRuntimeProbe.cpp:180 probes for an installed IfcOpenShell package. The branch at line 209 removes the inspection modules and imports the installed package when found. Adding that same preference again would not resolve this failure.
• freecad-source/src/WebAssembly/FreeCADCoreProbe/BimRuntimeProbe.cpp:3967 rejects the inspection backend before creating or modifying a document. Retain this guard until an actual backend is available.
• freecad-source/src/WebAssembly/FreeCADCoreProbe/BimRuntimeProbe.cpp:3986 calls the desktop importers.exportIFC exporter; line 4001 uses nativeifc.ifc_import for import. The earlier source-index description of the import route is outdated.
• docs/current/provided-source-index.md:45 records completed dependency checks and the specific pending local backend locations. Reuse those results; do not repeat completed searches or infer absence from blocked searches.

The next targeted lookup in this turn was rejected with SCHEDULER_SOURCE_BUDGET_REACHED. Backend source and WASM binding availability remain unresolved. Continue from the pending locations in the source index, then connect the actual compatible binding and Python package to the existing BIM target. Do not replace IFC serialization or geometry with inspection objects, fixed output, or another geometry kernel.

No runtime code, coverage declarations, or acceptance evidence changed in this turn. Build, artifact sync, and acceptance remain owned by the outer pipeline. After backend integration, isolate the existing two IFC cases before running any other invalidated cases. This note is a boundary record, not an implementation or business acceptance receipt.