Intention Registry Entry v1.0

Registry ID: INT-017

Title: Coordinate

Family: Relational

Status: Draft

Version: 1.0.0

Primary function: Align distinct systems, roles, resources, information, timing, and actions around a shared activity or outcome while preserving differentiated authorship, responsibility, consent, and local autonomy.

0. Canonical Definition

Coordinate is the intention to organize the timing, roles, information, resources, and actions of distinct systems so they can contribute coherently toward a shared activity or outcome without collapsing into centralized control or forced uniformity.

Coordinate allows multiple systems to act together while remaining distinguishable.

It may concern:

• teams
• relationships
• institutions
• public services
• technical systems
• restoration processes
• distributed networks
• community efforts
• emergency response
• governance
• healthcare
• symbolic compositions
• collaborative creation
• logistics
• shared infrastructure
• multi-agent systems
• cross-domain projects

Coordination does not require every system to perform the same function, hold the same information, or possess equal responsibility.

It requires that differences become organized rather than obstructive.

Coordinate becomes coherent when:

• the shared purpose is legible
• roles remain distinct
• dependencies are visible
• information reaches the systems that need it
• timing is compatible
• responsibility remains attributable
• local autonomy is preserved where possible
• no coordinating system silently becomes owner of all participation

1. Foundational Principle

Distinct systems can contribute to a shared outcome when their differences are organized without being erased.

Connection creates the pathway for relation.

Support increases available capacity.

Coordinate arranges those connected capacities into a workable pattern.

Its basic movement is:

distributed systems
→ shared purpose
→ differentiated roles
→ synchronized contribution
→ coherent collective action

Coordinate protects the distinction between:

alignment

and:

conformity

between:

shared direction

and:

centralized authorship

and between:

role differentiation

and:

hierarchical reduction

Coherent coordination does not make every system interchangeable.

It allows each system to contribute from its actual position, capacity, knowledge, and responsibility.

2. Directional Function

Starting condition

Coordinate commonly arises when:

• multiple systems share a purpose
• work is distributed
• dependencies are unclear
• duplicated effort is occurring
• timing conflicts reduce effectiveness
• roles overlap or remain unassigned
• relevant information is fragmented
• resources are available but poorly allocated
• a restoration process requires several contributors
• connected systems are acting without shared sequence
• institutional functions interfere with one another
• a public response requires distributed action
• technical services must exchange state
• collaboration exists without decision clarity
• no system can complete the task alone
• local optimization is producing collective failure
• shared activity requires synchronized boundaries

Intended direction

Coordinate seeks movement from:

fragmented action
→ organized contribution

role ambiguity
→ differentiated responsibility

timing conflict
→ workable synchronization

information silos
→ relevant information flow

resource mismatch
→ purposeful allocation

duplicated effort
→ complementary effort

local optimization
→ shared-system coherence

Coordinate does not seek:

maximum centralization

It seeks:

the minimum shared structure required for distinct systems to contribute coherently

Intended outcome region

A coherent Coordinate intention seeks an outcome region in which:

• the shared purpose is understood
• roles are sufficiently clear
• responsibilities remain attributable
• timing and dependencies are visible
• relevant information moves reliably
• resources reach appropriate functions
• duplicated or conflicting effort decreases
• local systems retain legitimate discretion
• changes can be communicated
• conflict can be escalated and resolved
• participation remains consent-valid
• coordination can end when the shared activity is complete

Protected invariants

Coordinate should preserve:

• identity
• differentiated authorship
• role clarity
• responsibility
• consent
• local knowledge
• boundary integrity
• auditability
• valid dissent
• reversibility
• meaningful exit
• the distinction between coordination and command
• the distinction between shared purpose and imposed uniformity
• the distinction between leadership and ownership

3. Active Intention Profile

aim: "Align distinct systems, roles, resources, information, timing, and actions around a shared activity or outcome."

target: "A team, relationship, institution, network, project, restoration process, public system, technical architecture, or distributed field of action."

scope: "Limited to the shared functions, dependencies, decisions, resources, and timing required for the agreed activity."

horizon: "Active until the shared objective is complete, stable coordination architecture exists, or the participating systems no longer remain compatible."

priority: "Often follows Connect, Invite, Clarify, Verify, Support, Protect, or Stabilize and may precede Restore, Integrate, Transform, Preserve, or Create."

forbidden_outcomes:
  - "centralized control"
  - "forced conformity"
  - "role erasure"
  - "responsibility diffusion"
  - "local knowledge suppression"
  - "coordination used as surveillance"
  - "permanent command authority"
  - "participation without meaningful consent"

completion_condition: "Distinct systems can contribute reliably toward the shared objective with clear roles, visible dependencies, appropriate information, and preserved authorship."

confidence_requirements: "Coordination depth should remain proportional to demonstrated interdependence, consequence, trust, and the need for shared control."

reversibility_requirements: "Coordination structures should remain adjustable, delegable, federated, reducible, or terminable as conditions and shared purposes change."

4. Admissibility

Preconditions

Coordinate is admissible when:

• multiple distinct systems are involved
• a legitimate shared purpose exists
• meaningful interdependence is present
• the systems have consented or hold valid shared duties
• differentiated roles can be identified
• coordination can improve the outcome
• the coordinating structure remains proportionate
• local systems retain relevant authorship
• information sharing can remain bounded
• responsibility can remain traceable
• exit or completion conditions can be defined

Supporting evidence

Coordinate may be supported by:

• duplicated work
• missed handoffs
• dependency conflicts
• resource shortages
• incompatible timing
• unclear decision rights
• recurring communication failure
• fragmented restoration efforts
• cross-system risk
• shared infrastructure
• distributed expertise
• public emergency
• multi-party agreement
• technical interoperability requirements
• observed collective-action failure
• repeated local optimization producing systemic harm
• inability of one system to fulfill the objective independently

Consent conditions

Consent requirements depend on the context.

Explicit consent is generally required for:

• voluntary collaboration
• private relationships
• data sharing
• community participation
• research
• technical integration
• resource pooling
• shared creative work
• public representation

Coordination may also arise from legitimate existing duties in:

• employment
• emergency response
• public administration
• healthcare
• infrastructure
• contracted work
• fiduciary relationships
• dependent-system care

Existing duty does not authorize unlimited coordination.

Systems should still know:

• what shared outcome is being pursued
• what role they hold
• what information is shared
• who can make which decisions
• how conflict is resolved
• what happens when conditions change
• when the coordinating authority ends

Boundary conditions

Coordinate must distinguish:

sharing the information required for joint action

from:

granting unrestricted visibility into each participating system

and:

assigning roles

from:

reducing systems to those roles

Coordination should preserve:

• local decision rights
• private domains
• limited information access
• role-specific authority
• dissent pathways
• appeal
• independent records
• the ability to raise conflict
• the right to leave voluntary structures
• the distinction between coordination failure and personal failure

Capacity conditions

A system enacting Coordinate should possess sufficient capacity to:

• define shared purpose
• map dependencies
• distinguish roles
• allocate resources
• communicate changes
• preserve records
• recognize local expertise
• resolve conflicts
• adapt timing
• avoid bottlenecks
• delegate authority
• detect when central coordination is no longer required
• restore authorship after emergencies

Scale conditions

Coordinate should scale according to:

• number of systems
• interdependence
• consequence of failure
• time sensitivity
• resource complexity
• information sensitivity
• geographic distribution
• power asymmetry
• system diversity
• rate of change

A small team may coordinate through direct dialogue.

A distributed technical network may require shared protocols and event schemas.

A public emergency may require temporary centralized sequencing while preserving local execution and later authority return.

As scale increases, coordination requires stronger:

• modularity
• interoperability
• documentation
• federated decision rights
• escalation paths
• observability
• redundancy
• local adaptation
• sunset conditions

Null conditions

Coordinate returns ∅ when:

• no meaningful shared purpose exists
• systems are not sufficiently compatible
• one system can act independently without affecting others
• coordination primarily serves surveillance or control
• consent or legitimate duty is absent
• the coordinating body lacks relevant standing
• forced uniformity would erase necessary local knowledge
• the same purpose can be achieved through simple communication
• roles cannot be assigned without identity override
• the shared structure exports greater harm
• immediate separation or protection is required
• the coordinating authority cannot be audited
• the shared objective has already completed
• coordination is being used to avoid assigning responsibility

5. Intention Provenance

Common sources

Coordinate may emerge from:

• shared purpose
• interdependence
• collaboration
• emergency
• restoration
• infrastructure
• project work
• public duty
• logistics
• care
• technical integration
• community organization
• governance
• distributed expertise
• mutual aid
• creation
• risk management
• resource stewardship

Legitimate provenance

Coordinate may be coherently:

• mutually authored by participating systems
• invited through collaborative agreement
• role-derived through legitimate stewardship, leadership, or public duty
• condition-derived where interdependence is unavoidable
• restoration-derived where several systems must contribute to repair
• emergency-derived where rapid sequencing is necessary
• technical-derived through shared protocol or infrastructure
• community-derived through collective action
• public-interest-derived where coordination reduces systemic harm

High-risk provenance

Coordinate becomes high-risk when driven by:

• desire for centralized control
• surveillance
• institutional expansion
• intolerance of local difference
• efficiency absolutism
• reputation management
• command preference
• ownership
• ideological conformity
• data extraction
• fear of independent action
• desire to diffuse responsibility
• monopoly
• permanent emergency logic

Capture vectors

Centralization capture

The coordinating system accumulates decisions that do not require central control.

Surveillance capture

Information sharing expands beyond the shared task.

Efficiency capture

Human, ecological, or relational values are subordinated to throughput.

Role capture

Participants become permanently identified with temporary functions.

Responsibility capture

Collective process is used to conceal individual or institutional accountability.

Platform capture

The intermediary owns the infrastructure, data, and terms of collaboration.

Emergency capture

Temporary command becomes permanent authority.

Metric capture

Coordination is optimized for measurable activity rather than the actual shared outcome.

6. Interaction Profile

Common interactions

Coordinate commonly travels through:

• planning
• scheduling
• role assignment
• delegation
• sequencing
• synchronization
• information sharing
• resource allocation
• dependency mapping
• handoff
• routing
• status updates
• escalation
• protocol definition
• consensus
• command under bounded conditions
• facilitation
• conflict resolution
• shared documentation
• orchestration

Supporting interactions

Coordinate is often supported by:

• Clarify
• Verify
• Connect
• Invite
• Witness
• Support
• Protect
• Stabilize
• Preserve
• Restore
• Integrate
• Create

High-risk interactions

Coordinate becomes high-risk when paired with:

• compulsory reporting
• total visibility
• centralized command
• biometric or behavioral monitoring
• punitive metrics
• hidden decision rules
• permanent role assignment
• resource coercion
• forced participation
• suppression of local judgment
• nontransparent automation
• unreviewable emergency power

Incompatible interactions

Coordinate is incompatible with:

• concealed purpose
• responsibility diffusion
• forced conformity
• identity erasure
• retaliation for valid dissent
• data extraction beyond task scope
• central authority without review
• permanent emergency command
• denial of local conditions
• coordination that cannot terminate
• shared action built on false consent

7. Operator Profile

Primary operators

Γ — Selection

Chooses roles, timing, resources, and action pathways within the shared field.

Alignment

Brings differentiated actions into compatible direction.

⊗ — Coupling

Connects the systems that must exchange state or resources.

Au — Auditability

Makes decisions, dependencies, handoffs, and responsibilities traceable.

K — Relational Coherence

Tracks whether the participating systems remain capable of working together.

Supporting operators

Ψ — Presence

Maintains awareness of current field conditions.

Μ — Sensemaking

Interprets distributed signals and changing needs.

Δ — Differentiation

Separates roles, responsibilities, local states, and dependencies.

Π — Boundary

Limits information, access, role authority, and shared resources.

Σ — Invariant Preservation

Protects identity, consent, purpose, local knowledge, and legitimate autonomy.

Θ — Humility

Prevents the coordinator from assuming complete knowledge.

Λ — Compatibility

Tests whether systems, timing, methods, and goals remain mutually workable.

ℛ — Restoration

Repairs failed handoffs, trust damage, overload, or coordination breakdown.

Conditional operators

Amplification

May increase urgent signals, resources, or public warnings.

Attenuation

May reduce noise, duplicated effort, competing demand, or excessive reporting.

Containment

May bound coordination during crisis or technical compromise.

Force

May be temporarily admissible under a valid high-risk gate when immediate collective action is required to prevent severe harm.

Excluded uses

Coordinate must not be implemented through operators used to:

• centralize all authorship
• erase local judgment
• collect unrelated information
• hide responsibility
• convert temporary roles into permanent identity
• enforce conformity for convenience
• preserve command after the shared need ends
• punish dissent that improves system accuracy
• make the coordinator indispensable by design

8. Expected State Effects

State-effect caution

Coordination can increase total system power.

distributed capacity
→ aligned capacity
→ increased collective effect

This amplification may be beneficial or harmful.

Coherent coordination therefore requires strong:

• purpose integrity
• boundary controls
• auditability
• responsibility attribution
• completion conditions
• scale awareness

A well-coordinated harmful system remains harmful.

Coordination quality does not establish purpose legitimacy.

9. Intention Across Time

Immediate — I₀

Immediate Coordinate aligns a present shared action.

Examples:

• assigning a task
• sequencing a handoff
• scheduling a meeting
• routing information
• aligning an emergency response
• resolving a role overlap
• directing resources to a current need

Tactical — I₁

Tactical Coordinate organizes a project, restoration process, or recurring activity.

Examples:

• project management
• care-team coordination
• multi-agency response
• supply-chain planning
• team workflow
• technical deployment
• community mutual aid
• collaborative research
• cross-functional restoration

Strategic — I₂

Strategic Coordinate creates durable shared-action architecture.

Examples:

• federated governance
• public-service systems
• distributed technical protocols
• emergency management frameworks
• interoperable healthcare
• alliance structures
• supply networks
• community institutions
• multi-agent orchestration
• cross-domain knowledge systems
• shared infrastructure
• institutional operating models

Identity-trajectory conflict

Coordinate conflicts with identity trajectory when it becomes:

• compulsive control
• inability to delegate
• identity fused with leadership
• fear of uncoordinated autonomy
• permanent monitoring
• reduction of life to plans and roles
• inability to participate without managing
• intolerance of emergent action
• responsibility accumulation
• local identity sacrificed to system efficiency

The trajectory conflict is:

Coordinate as organized contribution
⊥
Coordinate as ownership of collective action

10. Completion and Exit

Completion condition

Coordinate is complete when:

• the shared objective is achieved or stable
• roles and responsibilities are clear
• information and resources move reliably
• participants can perform without continuous intervention
• dependencies are visible
• conflict pathways exist
• local authorship remains intact
• the coordinating structure can reduce or close
• remaining coordination can be maintained through ordinary protocols

Exit condition

Active coordination should end, decentralize, or transition when:

• the shared activity is complete
• stable procedures replace active orchestration
• participants can self-coordinate
• centralized intervention adds more burden than value
• the coordinating system lacks legitimacy
• roles or purpose materially change
• consent is withdrawn from voluntary collaboration
• the remaining work belongs to Preserve, Integrate, Restore, Release, or Create

Common transition

Coordinate commonly transitions into:

Coordinate → Preserve
Coordinate → Restore
Coordinate → Integrate
Coordinate → Transform
Coordinate → Create
Coordinate → Support
Coordinate → Stabilize
Coordinate → Release
Coordinate → Connect

Recurrence condition

Coordinate may be reactivated when:

• conditions change
• handoffs fail
• new systems enter
• resources shift
• conflict returns
• timing becomes incompatible
• dependencies change
• crisis emerges
• stable protocols no longer produce the intended outcome
• distributed systems require renewed alignment

Non-completion warning

Coordinate without decentralization, sufficiency, or an exit condition becomes permanent management, surveillance, or centralized control.

11. Polarity Architecture

Coherent Form — Cooperative Alignment

The coherent form of Coordinate:

• defines shared purpose
• differentiates roles
• preserves local authorship
• distributes relevant information
• makes responsibility visible
• respects local knowledge
• supports dissent and correction
• adapts to changing conditions
• uses only necessary centralization
• ends when active coordination is no longer required

Coherent coordination creates collective capacity without collective erasure.

Deficit Form — Fragmentation or Disorganization

Too little Coordinate produces:

• duplicated effort
• missed handoffs
• conflicting actions
• resource waste
• unclear responsibility
• delayed response
• information silos
• unaddressed dependencies
• local optimization
• collective-action failure
• restoration gaps
• institutional drift

Excess Form — Overcoordination

Too much Coordinate produces:

• meeting overload
• reporting burden
• decision delay
• micromanagement
• loss of local initiative
• dependency on central approval
• excessive documentation
• reduced adaptability
• role rigidity
• surveillance
• coordination consuming more capacity than the work
• inability to act spontaneously

Shadow Inversion — Centralized Control or Forced Conformity

Coordinate inverts when shared action becomes a justification for one system to own decisions, information, timing, or identity across the whole field.

Examples:

• centralized approval for every action
• suppression of local expertise
• mandatory conformity
• command structures that cannot be questioned
• total information access
• role assignment without consent
• coordination used to monitor behavior
• treating dissent as disruption
• permanent emergency command
• forced synchronization despite incompatible conditions

Centralized control preserves the appearance of unity by removing distributed authorship.

Captured Form — Bureaucratic Orchestration

Captured Coordinate directs increasing resources toward maintaining the coordination apparatus rather than the shared outcome.

Examples:

• meetings replacing action
• reporting systems built for leadership visibility
• program offices preserving themselves after completion
• metrics optimized for procedural activity
• coordination layers multiplying without added function
• frontline systems serving administrative data needs
• decisions delayed by excessive approval chains
• institutions coordinating appearance while outcomes deteriorate

False Form — Alignment Theater

False Coordinate creates the appearance of shared action without real role clarity, resource flow, responsibility, or decision integration.

Examples:

• strategy documents without operational ownership
• recurring meetings without decisions
• shared dashboards with incompatible data
• cross-functional teams without authority
• public partnerships without resource commitments
• synchronized messaging masking conflicting incentives
• plans without dependency mapping
• consensus statements that no system implements

False Coordinate displays unity while practical fragmentation continues.

12. Failure Modes

Formation Failure

• Coordination is selected because leadership distrusts local systems.
• Shared purpose is assumed rather than established.
• efficiency is treated as the only value.
• A coordinator seeks status or control.
• Existing informal coordination is ignored.
• Diversity is treated as disorder.
• The problem is framed as coordination failure when incentives are actually incompatible.
• emergency logic is applied to ordinary conditions.

Scope Failure

• Coordination expands beyond the shared task.
• role authority reaches unrelated domains.
• temporary information access becomes permanent.
• a project office becomes a general command structure.
• one shared outcome is used to justify identity conformity.
• local systems must report all activity.
• the coordination layer absorbs resources needed for execution.

Selection Failure

• Coordinate is used when Connect has not yet been established.
• coordination begins before Clarify.
• roles are assigned before consent.
• planning replaces immediate protection.
• coordination is used where Separate is necessary.
• shared action is forced despite incompatible purposes.
• a structural resource problem is treated as communication failure.
• the system coordinates around harm rather than stopping it.

Operator Failure

• information is delayed or distorted.
• roles overlap.
• dependencies remain hidden.
• authority is not matched to responsibility.
• local feedback cannot alter plans.
• central systems become bottlenecks.
• metrics replace actual state.
• escalation pathways fail.
• auditability becomes surveillance.
• synchronization ignores local timing.

Boundary Failure

• private information is shared without necessity.
• participation becomes compulsory.
• dissent triggers retaliation.
• local autonomy is removed.
• one system speaks for all participants.
• roles become identity labels.
• temporary access persists.
• coordinating authority expands without review.
• participants cannot exit voluntary collaboration.

Completion Failure

• coordination continues after the objective is achieved.
• the coordinating body preserves itself.
• reporting never decreases.
• centralized decisions are never returned.
• roles remain frozen.
• emergency authority becomes ordinary.
• every new issue is routed through the same central structure.
• participants become unable to act independently.

Validation Failure

• meeting attendance is treated as alignment.
• shared language is treated as shared purpose.
• task completion is treated as system coherence.
• procedural compliance is treated as effective coordination.
• dashboard activity is treated as real progress.
• central visibility is treated as local capacity.
• no one measures coordination burden.
• participant authorship is ignored.
• collective success conceals exported harm.

Attribution Failure

• disagreement is treated as unwillingness to coordinate.
• local adaptation is treated as noncompliance.
• role confusion is blamed on individuals.
• missed handoffs are attributed to carelessness despite invalid system design.
• lack of reporting is treated as lack of work.
• decentralization is treated as disorder.
• resistance to surveillance is treated as opposition to shared purpose.
• coordinator effort is assumed to equal coordination value.

13. Forbidden Outcomes

Coordinate must not produce:

• centralized control
• forced conformity
• role erasure
• responsibility diffusion
• local knowledge suppression
• surveillance
• permanent command authority
• compulsory participation
• administrative overload
• coordination capture
• punitive reporting
• hidden decision rules
• identity reduced to function
• alignment theater
• efficiency purchased through exported harm

14. Declared, Operational, and Inferred Intention

Declared Signals

Declared Coordinate commonly appears through statements such as:

• “We need to align.”
• “These roles should work together.”
• “The handoffs need to be clearer.”
• “We need a shared plan.”
• “Who owns each decision?”
• “These resources should be organized around the same outcome.”
• “The timing needs to be synchronized.”
• “Each system should know what the others depend upon.”

Declared coordination language does not itself establish shared purpose or distributed authorship.

Operational Signals

Coordinate is operationally present when:

• roles are legible
• decision rights are known
• dependencies are mapped
• information reaches relevant systems
• resources follow the shared purpose
• local feedback changes plans
• handoffs complete
• conflict pathways work
• duplicated effort decreases
• responsibility remains attributable
• coordination burden remains proportionate
• central authority reduces when no longer needed

Outcome Signals

Coordinate has produced a coherent outcome when:

• shared activity becomes more reliable
• participants retain identity and authorship
• resource use improves
• delays and conflicts decrease
• local systems can adapt
• responsibility is visible
• trust increases
• the collective outcome improves
• coordinating structures do not become permanent owners
• participants can act without continuous central intervention
• system learning persists after the project ends

Common Misattributions

• Assuming agreement means coordination.
• Treating attendance as participation.
• Treating centralized control as stronger coordination.
• Assuming dissent means misalignment.
• Treating uniformity as coherence.
• Assuming more reporting creates more visibility.
• Treating local autonomy as inefficiency.
• Assuming shared tools create shared purpose.
• Treating collaboration language as distributed authority.
• Assuming a well-coordinated outcome is ethically coherent.

15. Responsibility Profile

Responsibility analysis for Coordinate should ask:

• What shared purpose justified coordination?
• Did participating systems consent or hold legitimate duties?
• Were roles clear?
• Were authority and responsibility matched?
• Was local knowledge included?
• Was information sharing proportionate?
• Were dependencies visible?
• Could participants dissent?
• Did coordination reduce or increase burden?
• Did one system accumulate control?
• Were resources allocated coherently?
• Did centralization persist after need ended?
• Were outcomes improved?
• Was harm exported?
• Did participants retain authorship?
• Could the structure terminate?
• Were coordination failures repaired?

16. Restoration Profile

Restoration Triggers

Restoration is required when:

• coordination becomes centralized control
• roles become permanent identity
• local knowledge is suppressed
• reporting becomes surveillance
• responsibility is diffused
• participation is coerced
• coordination consumes excessive capacity
• emergency authority persists
• bureaucratic orchestration replaces action
• shared systems conceal incompatible incentives
• false alignment obscures failure
• one participant captures the network

Cessation Requirements

• stop unnecessary reporting
• reduce central approval
• end compulsory participation
• suspend intrusive monitoring
• return local decision rights
• close expired command structures
• stop using alignment language to suppress dissent
• end coordination layers that add no value
• halt resource extraction by the coordinating system
• stop treating roles as total identity

Audit Requirements

The audit should determine:

• what shared purpose existed
• who designed the structure
• how roles were assigned
• which systems held decision authority
• what information was collected
• whether local feedback mattered
• who benefited from centralization
• who bore coordination burden
• whether responsibility remained visible
• whether outcomes improved
• whether command persisted after completion
• whether participants could leave
• whether hidden incentives remained incompatible
• whether the coordinating body became self-preserving

Repair Actions

Repair may require:

• decentralizing decisions
• clarifying roles
• restoring local authority
• reducing reporting
• deleting unrelated data
• reallocating resources
• repairing failed handoffs
• acknowledging responsibility
• removing redundant coordination layers
• rebuilding direct communication
• creating federated governance
• compensating for extractive burden
• closing expired emergency structures
• re-establishing shared purpose

Authorship Restoration

Authorship restoration may include:

• returning decision rights
• allowing local systems to define implementation
• restoring dissent
• enabling independent records
• ending unauthorized representation
• separating participation from identity
• restoring control over data
• allowing voluntary systems to exit
• recognizing local expertise
• returning shared outcomes to co-authorship

Completion Recovery

To restore completion:

• restate the shared objective
• remove unrelated coordination
• map roles and dependencies
• match authority to responsibility
• define the minimum necessary central function
• establish decentralization triggers
• close completed structures
• transition into Preserve, Restore, Integrate, Create, Support, or Release
• verify that participants can function without constant orchestration

Recurrence Prevention

• define shared purpose explicitly
• use federated decision structures
• preserve local discretion
• minimize data collection
• match authority to responsibility
• document dependencies
• define sunset conditions
• measure coordination burden
• protect dissent
• audit centralization incentives
• separate coordination from surveillance
• test independent operation
• ensure shared tools remain interoperable rather than captive

17. Intention Relationships

Reinforcing Intentions

INT-003 — Clarify

Clarify defines roles, scope, dependencies, and shared purpose.

INT-013 — Connect

Connect establishes the relational or technical interfaces required for coordination.

INT-014 — Invite

Invite preserves voluntary entry into collaborative structures.

INT-015 — Witness

Witness ensures local state and testimony remain visible to the coordinating field.

INT-016 — Support

Support supplies capacity needed for participants to fulfill their roles.

INT-022 — Integrate

Integrate can consolidate coordinated elements into a more durable coherent whole.

Tension Intentions

INT-008 — Refuse

Refusal may limit participation when the coordinated purpose or terms become incompatible.

INT-010 — Separate

Separation preserves distinction but may reduce shared action.

INT-011 — Release

Release ends roles, obligations, or structures that coordination may seek to maintain.

INT-019 — Transform

Transformation may require reassigning roles and disrupting existing coordination.

INT-023 — Liberate

Liberation may require dismantling captured coordination structures.

INT-024 — Create

Creation benefits from coordination but may be constrained by excessive planning or control.

Common Predecessors

• INT-002 — Question
• INT-003 — Clarify
• INT-004 — Verify
• INT-013 — Connect
• INT-014 — Invite
• INT-015 — Witness
• INT-016 — Support
• INT-021 — Stabilize

Common Successors

• INT-012 — Preserve
• INT-018 — Reconcile
• INT-019 — Transform
• INT-020 — Restore
• INT-021 — Stabilize
• INT-022 — Integrate
• INT-024 — Create
• INT-011 — Release

18. Domain Applications

Personal and Relational Systems

Coordinate may involve:

• dividing household responsibilities
• planning shared time
• coordinating care
• managing shared finances
• organizing a move
• aligning expectations
• planning a joint project
• coordinating support during difficulty

Example:

Two people share responsibility for a household.

Coherent coordination identifies what must be done, who owns which tasks, how changes are communicated, and what happens when one person’s capacity changes.

The relationship is not reduced to task management, and neither person becomes the permanent coordinator of the other.

Organizational Systems

Coordinate may support:

• project management
• cross-functional work
• operations
• staffing
• supply chains
• incident response
• governance
• product development
• knowledge transfer
• budgeting
• launches
• stakeholder alignment

Organizational Coordinate becomes captured when teams primarily serve the reporting needs of management rather than the work itself.

Governance

Coordinate supports governance through:

• interagency response
• federal and local cooperation
• emergency management
• public-service delivery
• infrastructure planning
• diplomacy
• budgeting
• public-health response
• environmental stewardship
• regional planning
• civic participation
• mutual-aid agreements

Governance coordination should preserve local knowledge, legal authority, public accountability, and sunset conditions for emergency command.

Artificial Intelligence

Coordinate in AI systems may include:

• multi-agent orchestration
• tool sequencing
• task delegation
• human approval routing
• workflow management
• context sharing
• shared memory boundaries
• dependency handling
• conflict detection
• resource scheduling
• model specialization
• result aggregation

AI Coordinate should preserve:

• human authority
• task boundaries
• source provenance
• reversible action
• per-agent permissions
• audit logs
• explicit completion
• separation between coordination and ownership

Healthcare

Coordinate may include:

• care teams
• referrals
• medication management
• discharge planning
• rehabilitation
• emergency response
• family communication
• specialist collaboration
• records exchange
• long-term care
• public-health systems

Healthcare coordination should reduce patient burden rather than require the patient to become the sole integrator of fragmented systems.

Justice

Coordinate may concern:

• courts
• counsel
• evidence handling
• victim services
• reentry support
• restorative processes
• law enforcement
• social services
• public defenders
• community systems
• institutional oversight

Justice coordination must not allow agencies to diffuse accountability across a network while collectively producing harm.

Education

Coordinate may support:

• teaching teams
• student support
• accommodations
• curriculum sequencing
• interdisciplinary projects
• school–family communication
• mentorship
• assessment timing
• resource access
• community partnerships

Educational coordination should serve learner development rather than administrative visibility alone.

Symbolic Systems

Coordinate may organize:

• symbol sequences
• compositional roles
• directional flow
• hierarchy of meaning
• visual balance
• archetypal relationships
• temporal activation
• layered interpretation
• interface states
• symbolic grammar

Symbolic coordination should preserve each symbol’s distinct function while allowing the composition to express a larger coherent meaning.

Game Systems

Coordinate may operate through:

• party roles
• companion actions
• synchronized abilities
• resource planning
• faction cooperation
• multi-stage restoration
• environmental systems
• shared objectives
• NPC scheduling
• symbolic sequences
• cooperative puzzles
• distributed world-state response

A coherent game system should allow coordination to emerge through clear roles, trust, timing, and choice rather than reducing cooperation to following a central command.

19. Compact Reference Card

INT-017 — COORDINATE

Family:
Relational

Aim:
Align distinct systems, roles, resources, information, timing, and actions around a shared activity or outcome.

Target:
A team, relationship, institution, network, project, restoration process, public system, technical architecture, or distributed field of action.

Preserves:
Identity, differentiated authorship, responsibility, consent, local knowledge, boundary integrity, valid dissent, and meaningful exit.

Common interactions:
Planning, scheduling, delegation, sequencing, information sharing, resource allocation, handoff, routing, escalation, and facilitation.

Primary operators:
Γ, Alignment, ⊗, Au, K.

Completion:
Distinct systems contribute reliably toward the shared objective with clear roles, visible dependencies, appropriate information, and preserved authorship.

Forbidden outcomes:
Centralized control, forced conformity, role erasure, responsibility diffusion, surveillance, administrative overload, and permanent command authority.

O⁺:
Cooperative alignment.

O⁻:
Centralized control or forced conformity.

Deficit:
Fragmentation or disorganization.

Excess:
Overcoordination.

Captured form:
Bureaucratic orchestration.

False form:
Alignment theater.

Canon line:
Coordinate organizes distinct contributions toward shared action without transferring ownership of the whole field to the coordinating system.

20. Canon Lockbox

• Coordinate is an intention, not an operator.
• Coordination requires a legitimate shared purpose.
• Shared purpose does not require shared identity.
• Alignment is not conformity.
• Coordination must preserve differentiated roles.
• Authority must remain matched to responsibility.
• Coordination must preserve local knowledge.
• Information sharing must remain scoped.
• Dissent can improve coordination.
• More reporting does not automatically create more coordination.
• More centralization does not automatically create more coherence.
• A coordinated harmful system remains harmful.
• Coordination must not become surveillance.
• Coordination must not erase local authorship.
• Coordination must include completion.
• Emergency coordination must return authority.
• Coordination without purpose becomes bureaucracy.
• Coordination without boundaries becomes centralized control.
• Coordination without decentralization becomes dependency.
• Temporal recurrence determines whether coordinated systems became more capable together or merely more controlled.

21. Canon Line

Coordinate organizes distinct systems, roles, resources, and actions around a shared purpose while preserving local authorship, responsibility, valid difference, and the ability of the coordinating structure to end.