# BIM selected registration boundary

Batch: `bb9c4d9ef93ef33f4b01b4d6`

The packet reports `native-source-candidate-unregistered` for `BIM_Glue`,
`BIM_IfcElements`, `BIM_IfcExplorer`, and `BIM_IfcProperties`. Current source
already registers all four in `BIMDesktopCommandRegistry.h` (lines 32–39).
These entries reference executable scripts, not completion markers.

`BimRuntimeProbe.cpp` (lines 3526–3570) includes registered Document routes
in `bimDesktopAction` and passes the selected workflow script into the native
document execution scope. External URL routes use a separate branch.

The inspected Glue implementation in `BIMSelectedWorkflow.h` (line 5)
constructs an OCCT Part compound from selected Part features and removes the
source objects within a document transaction, consistent with desktop
`BimGlue.py` (line 33). The inspected IFC Elements branch (line 37) edits
labels, IFC roles and materials transactionally and returns document-derived
element data. These observations are source inspection, not runtime acceptance.

Remaining boundary: determine why the outer pipeline reports these existing
registrations as missing, using its current incremental build/sync/route
receipts. No evidence from this inspection justifies duplicate registration
or marker insertion. IFC Explorer and IFC Properties behavior, downstream
serialization, and mounted Web workflows are not established as complete by
this inspection and must not be inferred from registration alone.

No application code was changed. No tests, builds, browser validation,
benchmarks, business acceptance, or historical reconciliation were run.
Further source inspection requires a subsequent authorized source window;
the four supplemental windows for this turn were consumed.