Command Center
Unit 06 · Acting Without Agreement

What can we do together when we cannot agree?

Some differences will not converge — they are values, not information. This unit maps the held differences and the practices your system can act on regardless. Coordination without agreement is a legitimate outcome, not a failure.

Unit 06 · Coordination Field

Map what will not converge — and what can be coordinated anyway

On the left, name the differences that will not resolve. On the right, name concrete practices each side could back — for their own reasons. Coordination does not require shared conviction, only overlapping action.

Coordination coverage
Add held differences and coordinatable practices to see coverage.
Held differences
0
Positions that will not converge — values, identity, or fundamental interest. Log them so you stop trying to resolve them and start coordinating around them.
Coordinatable practices
0
Concrete practices — norms, infrastructure, protocols, shared language — that each side can back for their own reasons. If only one side has a reason, it is alignment, not coordination-without-agreement.
AIGenerate coordinatable practices from the differences
Unit 06 · Analysis

Is coordination actually possible here?

The field is only useful if you interrogate it. Check for premature un-resolvability, for practices that are alignment in disguise, and for differences with no bridging practice.

AIStress-test the coordination

Prompts are generated from your current case data — vision, stakeholders, held differences, coordinatable practices — and tailored to this unit's framework. Copy them into Claude, ChatGPT, or your preferred AI tool.

Unit 06 · AI & Export

Test what will hold and what will not

Choose a mode and copy the prompt. Your full coordination field is embedded automatically.

Ready-to-use prompt — your project data is included
Add held differences to generate a prompt.