spk-doctrine-bulk-edit

Perform a manual pre-edit occurrence review before changing any matches. Map every occurrence to the standard classification categories, confirm the edit policy when the blast radius is unclear, then execute the narrowest safe change and verify representative cases.

Occurrence classification maps each match of a bulk edit into one of eight standard schema categories plus explicit exceptions and moves. This ensures different kinds of matches are handled according to their category rather than being changed identically.

No. Runtime enforcement is treated as a path-based review gate, not an AST-semantic classifier. Classification relies on the manual occurrence review and path-based rules rather than semantic code analysis.

Confirm the edit policy whenever the blast radius of the change is unclear. If you cannot determine how many occurrences will be affected or which categories they fall into, pause and confirm the policy before executing any modification.

Path-based enforcement cannot understand code semantics, so it may miss context-dependent occurrences that an AST-semantic classifier would catch. It works best as a review gate combined with manual occurrence review and representative case verification.