Command Collision
Dynamic · Working definition · Checked against project sources, 19 October 2026 · Not externally verified
Command Collision: Competing directives or necessary activities converge on one person or resource without an agreed way to handle the tradeoff.
What it looks like
The directives can come from different people, or from the same person at different times. Each can be legitimate from where its source stands, and no protocol settles between them. Familiar forms: two people who each need you now; a rule that says one thing while the situation requires another; a standing instruction that meets a changed reality; one party’s directive that contradicts another’s.
In a genuine collision, no option satisfies everyone. The person who has to decide is not necessarily failing by choosing; the situation is built so that any choice leaves something undone.
Illustrative example
Illustrative (constructed). A work meeting and a dependent’s pickup fall in the same hour. Neither can move without a cost, and nobody has said which comes first. Whichever way the call goes, someone will experience it as wrong.
What tends to help
- Name the collision and who holds decision authority, so the outcome is a decision and not a quiet default.
- Show the work: lay out the options, what each protects, what it leaves exposed, and who bears that cost.
- Look for a partial move or a new resource that changes the choice.
- Record what stays uncovered rather than presenting the decision as fully solved.
Related
Context Overflow · Referral Loop · Generative Accountability · Lexicon
Claims and sources
Claim: Command collision is conflicting directives, each legitimate from its own vantage, arriving with no protocol that resolves them.
Status: Source claim
Source: Shot-Calling Under Command Collision, section 1 (unpublished working document developed through multi-AI dialogue and reflection)
Claim: In a genuine collision no option satisfies everyone, so deciding well is different from finding a cost-free choice.
Status: Source claim
Source: Same document, introduction and section 1
Claim: Making the reasoning explicit improves the decision and makes it easier to defend later.
Status: Source claim; untested
Source: Same document, section 2
Status key: Checked = verified against a primary source. Source claim = stated in a source and not independently checked. Hypothesis = proposed and untested. Illustrative = constructed example, not a documented case.
Add an example
No documented case is recorded here yet. A composite or consented example can be added with its source, date and status. A name for a pattern does not establish what is true in a particular situation.
Development sources: Shot-Calling Under Command Collision: A Working Document (unpublished), sections 1–2; Generative Accountability (this wiki).
