A water utility needs hotfix branches for broken sensor parsers that do not block ongoing feature work. Which branching practice fits?

A water utility that needs urgent sensor-parser fixes without blocking ongoing feature work should document branch naming that separates hotfix streams from feature branches so emergency corrections can land on their own path. Clear naming and branching policy lets on-call engineers open hotfix/* (or equivalent) streams, review them quickly, and merge without forcing every feature branch to pause or rebase into a single chaotic mainline. Documenting branch naming that branches hotfix streams from feature branches so urgent sensor fixes reuse tested code without blocking features fails because branching from feature branches couples the emergency repair to unstable in-progress code rather than tested code, removes the isolation a hotfix requires, and risks delaying the urgent fix with feature defects. Documenting branch naming that routes hotfix streams through release branches so urgent sensor fixes validate alongside scheduled parser builds fails because release branches are meant to stabilize scheduled builds, so routing emergencies through them delays urgent response until the release is ready and obscures which change fixed the sensor defect. Documenting branch naming that forwards hotfix streams into feature branches so urgent sensor fixes progress together without blocking features fails because forwarding into feature branches merges the emergency repair into unstable ongoing work, removes the isolation a hotfix requires, and risks delaying the urgent fix until feature work completes. Exam caveat: DP-750 expects practical branching that supports operational municipal data engineering, including hotfix isolation, not process absolutism. Operational check: publish the branch naming standard, verify urgent sensor parser fixes do not branch from feature branches to reuse tested code in the hotfix stream, and confirm a recent sensor hotfix used the documented hotfix stream without blocking active feature branches.