Patching
When a dependency needs to move, Patching builds the fix, tests it against your project, and applies it, with a human sign-off exactly where you want one. Nothing rots because nobody had time.
The gate
Some patches should just happen. Some should wait for a human eye. You draw that line per project, and Patching respects it: below the line it flows, at the line it waits for your sign-off, always on the record.
The gate is yours. The chore is not.
Built and tested first
A patch is never applied raw: it is built for your project and tested against it before it goes anywhere near production.
Your gate, your rules
Routine updates flow through; the ones you define as sensitive wait for a human sign-off. The line is yours to draw, per project.
No silent drift
Every patch, every decision, every gate on the operations record. What changed and who approved it is never a research project.
A 20-minute demo: watch a project ship, break, and get fixed, on the record.