Intention Registry Entry v1.0

Registry ID: INT-010

Title: Separate

Family: Boundary

Status: Draft

Version: 1.0.0

Primary function: Restore valid distinction, identity, boundary, function, or authorship where systems, roles, signals, meanings, responsibilities, or trajectories have become fused, entangled, captured, or improperly conflated.

0. Canonical Definition

Separate is the intention to restore valid distinction between systems, identities, roles, signals, responsibilities, meanings, functions, or trajectories that have become fused, entangled, captured, confused, or improperly coupled.

Separate does not necessarily end relationship.

Its purpose is to recover the distinction required for each system to be perceived, evaluated, chosen, and acted upon accurately.

Separation may concern:

• identity
• bodily boundary
• relational roles
• responsibility
• ownership
• data
• access
• technical processes
• symbolic meaning
• institutional authority
• emotional state
• signal source
• causal variables
• public and private domains
• compatible and incompatible functions
• present and historical state
• self-authored and externally imposed intention

Separate becomes coherent when it restores distinguishability without unnecessarily destroying connection, memory, responsibility, or the possibility of future compatible relation.

1. Foundational Principle

Distinct systems cannot relate coherently when their identities, boundaries, functions, or responsibilities can no longer be told apart.

Connection requires distinction.

Integration requires distinction.

Coordination requires distinction.

Responsibility requires distinction.

Even unity becomes incoherent when the parts within it lose the ability to remain themselves.

The basic movement of Separate is:

fusion or entanglement
→ differentiation
→ restored boundary
→ independent legibility
→ possible compatible relation

Separate protects against two opposite failures:

indistinction

and:

fragmentation

Too little separation produces fusion, capture, confusion, and responsibility diffusion.

Too much separation produces isolation, exclusion, loss of relation, and unnecessary fragmentation.

The aim is not distance for its own sake.

The aim is sufficient distinction for sovereign and coherent relation.

2. Directional Function

Starting condition

Separate commonly arises when:

• identities have become fused
• roles are no longer distinguishable
• one system speaks for another without standing
• responsibility is diffused across a group
• data from different sources has been merged improperly
• private and public boundaries have collapsed
• a relationship has become enmeshed or captured
• technical processes interfere with one another
• meanings have been conflated
• present state is being confused with historical state
• cause and carrier are treated as the same
• one intention is being substituted for another
• an institution and its leaders are treated as identical
• a person is reduced to a role or event
• symbolic forms are combined without preserving their distinct functions
• continued coupling prevents accurate observation or restoration

Intended direction

Separate seeks movement from:

fusion
→ distinction

entanglement
→ bounded relation

conflation
→ differentiation

shared ambiguity
→ distinct roles

identity capture
→ restored self-authorship

responsibility diffusion
→ attributable responsibility

interfering processes
→ functional partition

Separate does not seek:

maximum distance

It seeks:

the degree of distinction required for each system to remain legible, sovereign, and functionally coherent

Intended outcome region

A coherent Separate intention seeks an outcome region in which:

• identities are distinguishable
• boundaries become legible
• roles and responsibilities are attributable
• systems can act without unauthorized substitution
• signals can be traced to their sources
• harmful coupling decreases
• private and public domains are differentiated
• restoration can proceed without ongoing interference
• retained relationships become consent-valid
• each system can choose whether and how to reconnect
• distinct functions remain interoperable where appropriate
• separation does not erase relevant history or responsibility

Protected invariants

Separate should preserve:

• identity
• authorship
• consent
• provenance
• truthfulness
• responsibility
• valid relationship
• memory
• proportionality
• restoration capacity
• future compatibility
• the distinction between separation and abandonment
• the distinction between differentiation and hierarchy
• the distinction between boundary and exclusion

3. Active Intention Profile

aim: "Restore valid distinction between systems, identities, roles, signals, responsibilities, meanings, functions, or trajectories that have become improperly fused, entangled, captured, or conflated."

target: "A system pair, relationship, identity field, role structure, process, signal set, responsibility chain, data boundary, symbolic composition, or coupled function."

scope: "Limited to the dimensions of coupling or conflation that prevent accurate identity, authorship, function, responsibility, or restoration."

horizon: "Active until sufficient distinction, boundary integrity, and independent legibility are restored."

priority: "May temporarily supersede connection, integration, shared access, coordination, or continuity when those depend on invalid fusion."

forbidden_outcomes:
  - "fragmentation"
  - "abandonment"
  - "punitive exclusion"
  - "identity erasure"
  - "responsibility evasion"
  - "forced isolation"
  - "destruction of valid relationship"
  - "separation used to conceal shared history"

completion_condition: "The relevant systems, identities, roles, responsibilities, or functions become sufficiently distinct for independent authorship, accurate attribution, and consent-valid relation."

confidence_requirements: "The scope and permanence of separation must remain proportional to the degree of fusion, interference, capture, incompatibility, and restoration need."

reversibility_requirements: "Separation should preserve the possibility of safe reconnection, coordination, or integration when compatibility and consent later permit."

4. Admissibility

Preconditions

Separate is admissible when:

• meaningful conflation, fusion, entanglement, or interference exists
• distinction would improve identity, responsibility, safety, or function
• the systems or variables can be meaningfully differentiated
• continued coupling produces harm, capture, confusion, or blocked restoration
• the proposed scope is proportionate
• the actor has legitimate standing
• valid shared responsibilities will remain addressed
• separation does not require unnecessary identity erasure
• restoration or independent function becomes more possible
• a less disruptive differentiation would not be sufficient

Supporting evidence

Separate may be supported by:

• identity substitution
• unauthorized representation
• role confusion
• repeated boundary crossing
• responsibility diffusion
• technical interference
• merged data provenance
• codependency or coercive coupling
• inability to make independent decisions
• one system absorbing another’s costs
• relational patterns that prevent repair
• conflicting processes sharing an unsafe resource
• symbolic meanings being treated as identical
• legal entities being improperly conflated
• source and carrier being confused
• persistent failure caused by indistinguishable variables

Consent conditions

Consent is generally required when separation affects:

• relationships
• shared property
• family systems
• collaborative work
• communication
• access
• bodily proximity
• data ownership
• institutional roles
• shared identity
• cultural or symbolic stewardship

A system may unilaterally separate its own identity, data, access, participation, or boundaries when those fall within its legitimate authority.

Mutual consent may not be required to end an invalid or coercive coupling.

However, unilateral separation does not erase:

• shared obligations
• dependent-system needs
• contractual responsibility
• repair duties
• jointly authored history
• lawful process
• the rights of third parties

Boundary conditions

Separate must distinguish:

restoring distinction

from:

declaring one system lesser or disposable

and:

ending invalid coupling

from:

erasing all relationship and responsibility

Separation should preserve:

• dignity
• accurate attribution
• shared history
• legitimate duties
• access to remedy
• future choice
• non-retaliation
• proportionality
• the possibility of bounded communication
• the right of each system to define itself

Capacity conditions

A system enacting Separate should possess sufficient capacity to:

• identify what is conflated
• define the new boundary
• assign roles and resources
• preserve provenance
• communicate scope
• maintain essential functions
• address shared obligations
• prevent retaliatory escalation
• support dependent systems
• preserve records
• validate whether distinction improved coherence
• enable safe reconnection where appropriate

Scale conditions

Separate should scale according to:

• degree of entanglement
• number of affected systems
• criticality of shared infrastructure
• dependency
• severity of harm
• reversibility
• power asymmetry
• legal and relational obligations
• restoration capacity
• risk of fragmentation

A relational separation may involve reduced contact.

A technical separation may involve process isolation or network segmentation.

An institutional separation may involve role division, legal independence, or governance partition.

Larger-scale separation requires stronger planning for:

• continuity
• resource division
• responsibility
• data migration
• dependent systems
• public communication
• reintegration or interoperability

Null conditions

Separate returns ∅ when:

• no meaningful conflation or harmful coupling exists
• distinction is already sufficient
• separation is primarily punitive
• the actor seeks to erase responsibility
• the affected systems cannot survive the proposed division without proportionate support
• the same goal can be achieved through clarification or a narrower boundary
• the separation is discriminatory
• shared obligations are being abandoned
• identity difference is being fabricated to justify exclusion
• the process would destroy relevant evidence or history
• separation would export greater harm
• temporary stabilization should occur first
• the proposed division serves institutional capture rather than sovereignty

5. Intention Provenance

Common sources

Separate may emerge from:

• boundary recognition
• identity recovery
• role clarification
• technical architecture
• consent withdrawal
• relationship restructuring
• legal differentiation
• data governance
• conflict resolution
• system diagnosis
• restoration
• source attribution
• organizational redesign
• symbolic analysis
• deconsolidation
• capture detection
• responsibility assignment

Legitimate provenance

Separate may be coherently:

• self-authored by a system restoring its own identity
• co-authored through mutual restructuring
• role-derived where function requires independence
• condition-derived when continued coupling causes harm
• evidence-derived when conflation blocks accurate attribution
• restoration-derived where repair requires reduced interference
• rights-derived through consent, ownership, or legal standing
• technical-derived where system reliability requires partition
• governance-derived where concentrated authority must be divided

High-risk provenance

Separate becomes high-risk when driven by:

• prejudice
• punishment
• avoidance of accountability
• ideological purity
• social exclusion
• fear of difference
• institutional self-protection
• resource capture
• desire to isolate dissent
• forced segregation
• reputation management
• ownership
• refusal of shared responsibility
• desire to erase history

Capture vectors

Punitive capture

Separation becomes a method of punishment or deprivation.

Institutional capture

A system separates liabilities, affected people, or evidence while preserving centralized benefit.

Identity capture

A dominant actor decides which identities are allowed to remain connected.

Responsibility capture

Separation is used to deny shared causation or obligation.

Resource capture

One system takes shared resources while externalizing costs.

Purity capture

Difference is treated as contamination requiring exclusion.

Narrative capture

History is rewritten so the separated systems appear never to have been connected.

Technical capture

Architectural separation is claimed while hidden dependencies preserve control.

6. Interaction Profile

Common interactions

Separate commonly travels through:

• boundary creation
• partition
• disentanglement
• decoupling
• role division
• access separation
• data segmentation
• source differentiation
• withdrawal
• independent representation
• resource division
• namespace separation
• process isolation
• conflict-of-interest removal
• deconsolidation
• relational distance
• identity reaffirmation
• attribution mapping

Supporting interactions

Separate is often supported by:

• Reveal
• Clarify
• Verify
• Protect
• Refuse
• Contain
• Release
• Preserve
• Stabilize
• Restore
• Liberate
• Coordinate

High-risk interactions

Separate becomes high-risk when paired with:

• force
• expulsion
• deprivation
• public stigmatization
• compulsory relocation
• total communication ban
• destruction of shared resources
• historical erasure
• discriminatory classification
• permanent exclusion
• abandonment
• unilateral resource seizure

Incompatible interactions

Separate is incompatible with:

• identity erasure
• punitive isolation
• false differentiation
• denial of shared responsibility
• destruction of provenance
• forced segregation
• abandonment of dependents
• concealed continuing control
• destruction of valid interoperability
• separation that cannot be contested or reviewed

7. Operator Profile

Primary operators

Δ — Differentiation

Separates systems, roles, identities, variables, meanings, and causal chains.

Π — Boundary

Creates the interface through which distinct systems remain separate while potentially retaining controlled relation.

Σ — Invariant Preservation

Identifies what each system must retain through separation.

BΣ — Boundary Integrity

Tracks whether the new distinction remains coherent under pressure.

Γ — Selection

Determines which dimensions require separation and which may remain shared.

Supporting operators

Ψ — Presence

Maintains contact with actual system state rather than imagined incompatibility.

Μ — Sensemaking

Interprets entanglement, dependency, and consequence.

Au — Auditability

Preserves records, provenance, role attribution, and resource flows.

Θ — Humility

Prevents differentiation from becoming false certainty or hierarchy.

Λ — Compatibility

Determines whether any continued coupling remains valid.

ℛ — Restoration

Repairs harm caused by invalid fusion or by the separation process.

Attenuation

Reduces coupling where complete separation is unnecessary.

Conditional operators

Containment

May create temporary separation during active propagation.

Force

May be used only where an invalid coupling creates imminent severe harm and cannot otherwise be ended.

Release

May terminate bindings that no longer remain legitimate.

Coordination

May preserve required shared function after structural separation.

Excluded uses

Separate must not be implemented through operators used to:

• fabricate difference
• assign inferiority
• erase shared history
• externalize responsibility
• preserve hidden control
• destroy dependent systems
• punish identity
• seize shared resources
• eliminate all communication without necessity
• prevent future compatible relation by default

8. Expected State Effects

State-effect caution

Separation may make previously hidden differences more visible.

apparent unity
→ restored distinction
→ visible disagreement or asymmetry

This does not necessarily mean separation created the difference.

It may reveal a difference that fusion had concealed.

However, separation can create new harm when it removes:

• essential support
• shared infrastructure
• communication
• access to resources
• continuity
• legitimate responsibility
• pathways for future coordination

9. Intention Across Time

Immediate — I₀

Immediate Separate restores distinction within a present interaction.

Examples:

• distinguishing one person’s responsibility from another’s
• separating fact from interpretation
• ending unauthorized access
• isolating two interfering processes
• clarifying that one system does not speak for another
• moving out of harmful proximity

Tactical — I₁

Tactical Separate maintains independent function across a transition.

Examples:

• reducing relational contact
• dividing project roles
• separating financial accounts
• migrating data
• isolating technical environments
• establishing independent reporting
• partitioning an unstable subsystem
• distinguishing institutional and personal responsibility

Strategic — I₂

Strategic Separate creates durable differentiation architecture.

Examples:

• separation of powers
• independent oversight
• legal entity division
• modular technical systems
• data tenancy
• conflict-of-interest rules
• identity-preserving federal structures
• interoperable but independent institutions
• cultural sovereignty
• decentralized governance
• independent archives
• plural symbolic systems

Identity-trajectory conflict

Separate conflicts with identity trajectory when it becomes:

• isolation
• inability to connect
• fragmentation
• purity logic
• refusal of interdependence
• permanent exclusion
• denial of shared history
• identity built against another system
• loss of mutual responsibility
• destruction of viable coordination

The trajectory conflict is:

Separate as restored distinction
⊥
Separate as destruction of relation

10. Completion and Exit

Completion condition

Separate is complete when:

• relevant identities, systems, roles, or functions are distinguishable
• new boundaries are operational
• responsibilities are attributable
• unauthorized substitution ends
• harmful interference declines
• necessary resources are allocated
• valid shared obligations remain visible
• independent authorship is restored
• future relation can be chosen rather than presumed

Exit condition

Active separation should end or transition when:

• sufficient distinction is stable
• the systems can function independently
• ongoing enforcement is no longer necessary
• a safe level of coordination becomes possible
• restoration has reduced the original interference
• the remaining issue belongs to Release, Preserve, Coordinate, Reconcile, or Integrate
• the separation begins producing greater fragmentation than protection

Common transition

Separate commonly transitions into:

Separate → Stabilize
Separate → Restore
Separate → Preserve
Separate → Release
Separate → Coordinate
Separate → Support
Separate → Reconcile
Separate → Integrate
Separate → Connect
Separate → Liberate

Recurrence condition

Separate may be reactivated when:

• fusion returns
• boundaries are ignored
• roles become conflated
• hidden dependencies reappear
• one system resumes speaking for another
• interference resumes
• resource or data boundaries collapse
• identity capture returns
• responsibility becomes diffused again

Non-completion warning

Separate without restoration, responsibility, or future choice becomes fragmentation, abandonment, segregation, or permanent exclusion.

11. Polarity Architecture

Coherent form — Restored Distinction

The coherent form of Separate:

• restores identity
• makes roles legible
• preserves responsibility
• reduces harmful coupling
• maintains dignity
• protects authorship
• preserves relevant history
• supports independent function
• allows future compatible relation
• remains proportionate

Coherent separation makes relation selectable again.

Deficit form — Fusion

Too little Separate produces:

• identity loss
• enmeshment
• responsibility diffusion
• data contamination
• role confusion
• capture
• inability to refuse
• hidden dependency
• merged provenance
• relational exhaustion
• technical interference
• one system speaking for another

Excess form — Fragmentation

Too much Separate produces:

• isolation
• excessive partition
• duplicated systems
• communication failure
• loss of shared purpose
• resource inefficiency
• inability to coordinate
• denial of interdependence
• social exclusion
• disconnected knowledge
• inability to integrate
• brittle boundaries

Shadow inversion — Fragmentation or Exclusion

Separate inverts when distinction becomes destruction of relation, forced exclusion, or denial of shared humanity, responsibility, or access.

Examples:

• segregation
• discriminatory exclusion
• permanent blacklisting
• abandoning vulnerable systems
• treating difference as danger
• severing all communication
• removing people from shared institutions without due process
• destroying common resources
• isolating dissent
• denying historical connection

Captured form — Responsibility Partitioning

Captured Separate divides systems in ways that preserve benefit while displacing cost or accountability.

Examples:

• creating subsidiaries to isolate liability
• outsourcing harmful labor
• separating public brand from operational misconduct
• dividing data ownership while retaining hidden access
• isolating affected communities from decision-making
• assigning failure to one department while incentives remain systemic
• separating leadership from consequences
• splitting technical systems while preserving a centralized control layer

False form — Cosmetic Independence

False Separate creates the appearance of autonomy while hidden control, dependency, or access remains.

Examples:

• nominally independent oversight controlled by the institution
• separate accounts with shared credentials
• legal independence without resource independence
• opt-out systems that still collect data
• organizational spin-offs under the same command
• relational distance with continued surveillance
• cultural autonomy without decision rights
• technical sandboxing with unrestricted backend access

False Separate displays boundaries without restoring authorship.

12. Failure Modes

Formation failure

• Difference is exaggerated into incompatibility.
• Separation is selected from prejudice.
• A relationship problem is treated as total identity conflict.
• The actor seeks escape from responsibility.
• Purity replaces boundary integrity.
• A dominant system defines another as contaminating.
• Temporary tension is interpreted as permanent fusion.
• Technical convenience determines social separation.

Scope failure

• One conflated role triggers total exclusion.
• Temporary distance becomes permanent severance.
• Separation expands beyond the harmful coupling.
• Shared resources are divided unfairly.
• Dependents are ignored.
• Data separation destroys legitimate interoperability.
• One system retains benefit while assigning costs elsewhere.

Selection failure

• Separate is used when Clarify would suffice.
• Separation replaces Reconcile before compatibility is tested.
• A root cause is left intact.
• Isolation replaces Support.
• Separation is chosen before immediate containment or stabilization.
• A valid interdependence is mislabeled as capture.
• The system separates actors while leaving harmful incentives shared.

Operator failure

• Boundaries remain porous.
• Provenance is lost.
• Resource allocation is incomplete.
• Force exceeds necessity.
• Auditability is removed.
• communication is severed unnecessarily.
• roles are separated without decision rights.
• hidden access pathways remain.
• separation destroys critical shared function.

Boundary failure

• Identity is assigned from outside.
• One system is expelled without process.
• Shared property is seized.
• dependents are abandoned.
• historical ties are erased.
• future reconnection is prohibited automatically.
• the separated system lacks remedy or representation.
• difference becomes hierarchy.

Completion failure

• Separation remains an active conflict rather than stable distinction.
• Boundaries require constant escalation.
• independent function is never established.
• hidden control persists.
• the systems cannot transition into coordination or release.
• separation becomes permanent identity.
• no review determines whether continued distance remains necessary.

Validation failure

• Physical distance is treated as restored sovereignty.
• Legal independence is treated as operational independence.
• separate systems still share hidden access.
• roles are renamed without changing authority.
• apparent calm is treated as resolved entanglement.
• resource dependence is ignored.
• responsibility diffusion continues under new labels.
• no one checks whether identity and authorship improved.

Attribution failure

• Desire for separation is treated as hostility.
• Continued connection is treated as proof of fusion.
• independent identity is treated as rejection.
• relational distance is assumed to mean lack of care.
• failure after separation is attributed entirely to the separated system.
• technical coupling is mistaken for relational consent.
• shared history is treated as current obligation.
• difference is assumed to imply incompatibility.

13. Forbidden Outcomes

Separate must not produce:

• fragmentation
• abandonment
• punitive exclusion
• segregation
• identity erasure
• responsibility evasion
• resource deprivation
• destruction of shared history
• forced isolation
• concealed continuing control
• discriminatory partition
• loss of essential support
• cosmetic independence
• destruction of valid interoperability
• permanent hostility

14. Declared, Operational, and Inferred Intention

Declared signals

Declared Separate commonly appears through statements such as:

• “These systems need to be distinguished.”
• “This role is not mine.”
• “We need independent boundaries.”
• “These responsibilities are being conflated.”
• “This process should be isolated.”
• “One system should not speak for the other.”
• “We need distance before restoration can continue.”
• “Shared access should be divided.”

Declared separation language does not itself prove that independence has been restored.

Operational signals

Separate is operationally present when:

• decision rights become distinct
• access is genuinely partitioned
• roles are attributable
• data provenance is preserved
• one system can no longer override another
• resources support independent function
• hidden dependencies become visible
• boundary violations decrease
• shared obligations remain documented
• future relation becomes consent-based
• the systems can represent themselves
• cosmetic separation is tested for operational truth

Outcome signals

Separate has produced a coherent outcome when:

• identities become more legible
• authorship increases
• harmful interference declines
• responsibility becomes attributable
• independent function improves
• boundary integrity stabilizes
• shared history remains accurate
• legitimate duties are fulfilled
• future connection is chosen rather than compelled
• restoration can proceed without ongoing fusion
• hidden control decreases

Common misattributions

• Treating separation as hatred.
• Assuming distance means total rejection.
• Treating independence as lack of cooperation.
• Assuming legal partition proves operational autonomy.
• Treating all interdependence as fusion.
• Assuming shared history requires continued coupling.
• Treating boundary restoration as punishment.
• Assuming separate identities cannot share purpose.
• Treating physical proximity as proof of connection.
• Assuming cosmetic independence restores sovereignty.

15. Responsibility Profile

Responsibility analysis for Separate should ask:

• What was improperly fused or conflated?
• Was separation necessary?
• Who had standing to initiate it?
• Were identities and roles accurately distinguished?
• Were shared obligations preserved?
• Were dependents protected?
• Were resources divided fairly?
• Was provenance maintained?
• Did hidden control continue?
• Was the process discriminatory?
• Did separation reduce harm?
• Did it create avoidable fragmentation?
• Was future coordination preserved where appropriate?
• Was responsibility clarified or evaded?
• Were harms caused by separation repaired?
• Did the separated systems gain meaningful authorship?
• Was completion recognized?

16. Restoration Profile

Restoration triggers

Restoration is required when:

• separation becomes abandonment
• identity distinction becomes discriminatory exclusion
• resources are withheld
• shared responsibility is denied
• hidden control persists
• historical ties are erased
• essential support is lost
• technical partition remains porous
• the process produces fragmentation
• cosmetic independence conceals dependency
• one system retains benefit while exporting harm
• future compatible relation is prohibited without cause

Cessation requirements

• stop punitive exclusion
• restore essential support
• end hidden access or control
• halt discriminatory partition
• cease using separation to avoid accountability
• restore communication where safe
• stop erasing shared records
• suspend resource seizure
• end forced isolation beyond necessity
• correct false independence claims

Audit requirements

The audit should determine:

• what required separation
• who defined the boundary
• which roles or systems were conflated
• what resources were shared
• how responsibilities were divided
• whether hidden access remained
• who benefited
• who bore the cost
• whether dependents were protected
• whether identity and authorship improved
• whether fragmentation increased
• whether reconnection or interoperability remained possible
• whether the separation became permanent without review

Repair actions

Repair may require:

• restoring resources
• correcting access controls
• clarifying responsibility
• re-establishing communication
• preserving shared records
• compensating for exclusion or abandonment
• creating independent governance
• removing hidden dependencies
• rebuilding safe interoperability
• restoring representation
• acknowledging shared causation
• supporting reintegration where desired
• revising discriminatory boundaries

Authorship restoration

Authorship restoration may include:

• returning decision authority
• enabling self-representation
• restoring control over data and identity
• providing independent resources
• ending unauthorized speaking-for
• allowing each system to define its own boundaries
• restoring the right to reconnect or remain separate
• removing externally imposed roles
• preserving the right to revise the relationship

Completion recovery

To restore completion:

• identify the exact conflation
• define the required distinction
• preserve shared obligations
• allocate necessary resources
• remove hidden control
• validate independent function
• transition into Stabilize, Restore, Coordinate, Reconcile, Integrate, or Release
• stop active separation once stable boundaries exist
• establish review conditions for continued distance

Recurrence prevention

• maintain clear role definitions
• preserve source provenance
• enforce access separation
• audit hidden dependencies
• provide independent resources
• document shared obligations
• preserve appeal and representation
• test operational rather than cosmetic independence
• prevent liability partitioning
• maintain optional interoperability
• review boundaries through time
• preserve the right of systems to define and revise relation

17. Intention Relationships

Reinforcing intentions

INT-003 — Clarify

Clarify identifies which systems, meanings, roles, or responsibilities have been conflated.

INT-007 — Protect

Protect preserves systems while separation is established.

INT-008 — Refuse

Refuse rejects continued invalid coupling.

INT-009 — Contain

Contain may create a temporary boundary before full separation.

INT-011 — Release

Release ends bindings that no longer remain legitimate after distinction is restored.

INT-023 — Liberate

Liberate removes structures preventing independent authorship.

Tension intentions

INT-013 — Connect

Connect seeks compatible coupling, while Separate restores necessary distance or distinction.

INT-016 — Support

Support may require ongoing access that separation limits.

INT-017 — Coordinate

Coordination preserves shared action, but excessive coupling can recreate fusion.

INT-018 — Reconcile

Reconciliation may require renewed relation after separation.

INT-022 — Integrate

Integration requires distinction, but premature integration can reverse the separation.

INT-024 — Create

Creation may benefit from independent space while also requiring collaboration.

Common predecessors

• INT-001 — Reveal
• INT-003 — Clarify
• INT-004 — Verify
• INT-007 — Protect
• INT-008 — Refuse
• INT-009 — Contain

Common successors

• INT-011 — Release
• INT-012 — Preserve
• INT-016 — Support
• INT-017 — Coordinate
• INT-018 — Reconcile
• INT-020 — Restore
• INT-021 — Stabilize
• INT-022 — Integrate
• INT-023 — Liberate

18. Domain Applications

Personal and relational systems

Separate may involve:

• distinguishing one person’s feelings from another’s
• ending unauthorized speaking-for
• reducing contact
• dividing responsibilities
• establishing independent finances or space
• distinguishing care from control
• ending an imposed role
• restoring personal identity within a relationship

Example:

Two people have become unable to distinguish support from responsibility for one another’s decisions.

Separate may involve defining which choices belong to each person, reducing automatic intervention, and restoring independent authorship.

The relationship may remain intact, but its coupling changes.

Organizational systems

Separate may support:

• role division
• conflict-of-interest removal
• independent audit
• data segmentation
• legal entity separation
• governance partition
• resource allocation
• responsibility attribution
• environment isolation
• division of operational and oversight functions

Organizational Separate becomes false when oversight is nominally independent but remains funded, appointed, or controlled by the system it reviews.

Governance

Separate supports governance through:

• separation of powers
• judicial independence
• church–state distinction
• civilian–military boundaries
• regulatory independence
• public–private data separation
• conflict-of-interest restrictions
• federal or local authority division
• independent elections administration
• institutional checks

Governance separation must preserve coordination without allowing one branch or system to absorb the others.

Artificial intelligence

Separate in AI systems may include:

• separating user data from model training
• isolating tools
• partitioning memory
• separating persona from authority
• distinguishing retrieved fact from generated inference
• separating system instructions from user intention
• isolating untrusted agents
• maintaining per-user or per-project boundaries
• distinguishing model output from external action

AI Separate should prevent hidden cross-context access and should make actual, not merely nominal, isolation auditable.

Healthcare

Separate may include:

• distinguishing symptom from cause
• separating patient identity from diagnosis
• isolating contamination
• separating incompatible medications
• defining clinical roles
• maintaining record boundaries
• distinguishing acute from chronic state
• separating professional judgment from institutional incentive

Healthcare separation should never reduce the patient to a diagnostic category.

Justice

Separate may concern:

• separating investigation from adjudication
• distinguishing person from alleged act
• isolating evidence from interpretation
• separating powers
• removing conflicts of interest
• distinguishing accountability from punishment
• separating completed sentence from permanent identity
• maintaining attorney–client boundaries

Justice fails when roles collapse or when past action permanently absorbs the identity of the person.

Education

Separate may include:

• distinguishing learner identity from performance
• separating assessment from punishment
• defining teacher and administrator roles
• protecting student records
• distinguishing instruction from ideological conditioning
• separating feedback from humiliation
• isolating unsafe behavior without excluding the learner permanently

Educational separation should preserve belonging while restoring necessary boundaries.

Symbolic systems

Separate may distinguish:

• symbol from interpretation
• archetype from shadow form
• historical meaning from later inversion
• visual form from operational function
• sacred use from public use
• similar symbols with distinct provenance
• primary symbol from compositional modifier
• symbolic relation from symbolic identity

Symbolic separation prevents layered systems from collapsing into a single undifferentiated meaning.

Game systems

Separate may operate through:

• disentangling fused archetypes
• isolating corrupted systems
• dividing player and imposed identity
• separating overlapping world layers
• restoring NPC autonomy
• partitioning conflicting mechanics
• distinguishing illusion from world state
• recovering individual symbols from unstable compositions

A coherent game implementation should make separation a restoration of choice and legibility, not merely destruction or exile.

19. Compact Reference Card

INT-010 — SEPARATE

Family:
Boundary

Aim:
Restore valid distinction between systems, identities, roles, signals, responsibilities, meanings, functions, or trajectories that have become fused, entangled, captured, or conflated.

Target:
A relationship, identity field, role structure, process, signal set, responsibility chain, data boundary, symbolic composition, or coupled function.

Preserves:
Identity, authorship, consent, provenance, responsibility, valid relationship, restoration capacity, and future compatibility.

Common interactions:
Boundary creation, partition, disentanglement, decoupling, role division, process isolation, resource division, and independent representation.

Primary operators:
Δ, Π, Σ, BΣ, Γ.

Completion:
Relevant systems or functions become sufficiently distinct for independent authorship, accurate attribution, and consent-valid relation.

Forbidden outcomes:
Fragmentation, abandonment, punitive exclusion, segregation, responsibility evasion, hidden control, and destruction of valid relationship.

O⁺:
Restored distinction.

O⁻:
Fragmentation or exclusion.

Deficit:
Fusion.

Excess:
Fragmentation.

Captured form:
Responsibility partitioning.

False form:
Cosmetic independence.

Canon line:
Separate restores the distinction required for identity, responsibility, sovereignty, and compatible relation.

20. Canon Lockbox

• Separate is an intention, not an operator.
• Separation restores distinction.
• Distinction is required for coherent relation.
• Connection without distinction becomes fusion.
• Integration without distinction becomes erasure.
• Separation does not automatically end relationship.
• Separation does not erase shared history.
• Separation does not erase shared responsibility.
• Difference does not imply hierarchy.
• Independence does not imply hostility.
• Physical distance does not automatically restore sovereignty.
• Legal independence does not guarantee operational independence.
• Separation must preserve provenance.
• Separation must preserve essential support where legitimate.
• Separation must not become abandonment.
• Separation must not become punishment.
• Separation without resources may become cosmetic.
• Separation without auditability may preserve hidden control.
• Separation without future choice may become exclusion.
• Temporal recurrence determines whether distinction remained coherent or fusion returned under another form.

21. Canon Line

Separate restores the distinction required for identity, responsibility, sovereignty, and compatible relation without converting necessary boundaries into fragmentation, abandonment, or permanent exclusion.