Load structure and configuration in bulk
What It Does
Bulk declarations reuse record services while deferring repeated ancestry rebuilds. Units load in dependency order, and the producer must run one closing rebuild and reconciliation. Configuration items keep ordinary save validation rather than bypassing it.
The Flow
When Something Fails
Each failed item leaves its own transaction unapplied, but earlier successful items remain. The deferred ancestry can affect descendant reads and officer visibility until rebuilding succeeds. No local completion hook guarantees the rebuild, and the end-to-end data-job submission path is not established by these item handlers.
Open Design Questions
Architecture should decide whether a closing rebuild belongs in guaranteed job completion and how live traffic is excluded during loading. Additional bulk verbs and equivalent placement validation require product direction.