Asking every time is not collaboration
Good context collaboration is not helplessness. The model should continue through reversible, scoped work. It should stop at authority boundaries, destructive actions, unclear source-of-truth conflicts, and publish gates. Asking for permission to read a file is theater; asking before pushing to main is professionalism.
Design the gate before the task
For quest remakes, the gate is now clear: complete content, validate, create local commit; the human owns final push. That rule prevents accidental publish while keeping momentum. Sessions without pre-designed gates oscillate between asking too much and not asking enough.
Reversibility and blast radius
The two axes that determine whether to ask: reversibility (can it be undone?) and blast radius (who else is affected?). Reversible + local = continue. Irreversible + shared = ask. Use the matrix; do not trust gut feel under pressure.