Summary
- Define who may read, change, and decide.
- Separate temporary collaboration from durable memory.
- Automation can scale safely only after boundaries are clear.
Assign Responsibility First
The risk in a complex system rarely comes from one tool. It comes from overlapping responsibilities. Research, execution, review, and publishing need distinct boundaries, especially when several intelligent collaborators are involved.
The stronger the capability, the clearer the boundary must be.
Separate Temporary from Durable
A task can contain rich context without turning all of it into long-term memory. Only stable preferences, confirmed decisions, and facts that will genuinely matter later should persist.
Make Authority Inspectable
Authority should not hide inside vague defaults. Important actions need a visible target, scope, and result so a person can always understand what the system is doing.