Defer Ancestry Rebuilding During Bulk Loads

Context

Initial imports may load hundreds of units. The local item path avoids repeated whole-tree rebuilding but creates a deliberate consistency interval.

Decision

This record describes the existing producer-controlled completion step. Limiting loads to a workspace with excluded live traffic is a proposed operating requirement, not an enforcement proven by the item handler.

Alternatives Considered

Run ordinary placement and rebuilding for every imported unit. That repeats whole-workspace work for each item and changes the current bulk cost profile. Make the data-job engine automatically guarantee closing rebuild. No examined completion wiring provides this guarantee; it is a design option requiring further implementation.

Consequences

Derived ancestry and visibility can be stale while loaded parent references are already committed. An abandoned load remains inconsistent until rebuilding succeeds; reconciliation reports without repairing. Loaded writes retain versions but emit no structural business event.