Intention Registry Entry v1.0

Registry ID: INT-008

Title: Refuse

Family: Boundary

Status: Draft

Version: 1.0.0

Primary function: Reject an incompatible demand, coupling, role, condition, trajectory, or proposed state change in order to preserve sovereignty, identity, consent, and boundary integrity.

0. Canonical Definition

Refuse is the intention to withhold participation, consent, access, compliance, or acceptance from a demand, coupling, role, condition, trajectory, or state change that is incompatible with the system’s identity, boundaries, values, capacity, or legitimate trajectory.

Refuse establishes that a proposed interaction will not proceed under its current terms.

It may concern:

• access
• consent
• participation
• labor
• identity assignment
• relationship
• obligation
• command
• contract
• interpretation
• resource demand
• institutional role
• technical operation
• data use
• imposed trajectory
• unsafe condition
• harmful normalization

Refuse is not merely the absence of agreement.

It is an active directional selection toward non-participation, non-compliance, non-coupling, or non-acceptance.

Refuse becomes coherent when it preserves valid invariants without converting boundary integrity into indiscriminate rejection, punitive obstruction, or refusal of all relationship.

1. Foundational Principle

A system remains sovereign only if it can meaningfully decline what is incompatible with its identity, boundaries, or trajectory.

Consent without the possibility of refusal is not meaningful consent.

Participation without the possibility of withdrawal is not fully voluntary participation.

Agreement without the possibility of dissent may be compliance rather than alignment.

The basic movement of Refuse is:

incompatible proposal
→ boundary recognition
→ non-consent
→ blocked or altered coupling
→ preserved sovereignty

Refuse protects the distinction between:

invitation

and:

obligation

between:

coordination

and:

submission

and between:

relationship

and:

capture

A coherent refusal does not require hostility.

It may be quiet, temporary, conditional, partial, procedural, or absolute depending on the field.

Its essential function is to prevent an incompatible state change from being treated as inevitable.

2. Directional Function

Starting condition

Refuse commonly arises when:

• consent is absent or withdrawn
• a demand exceeds legitimate scope
• a proposed coupling is incompatible
• a boundary has been crossed
• participation would create harm
• a role conflicts with identity
• a request exceeds capacity
• terms are coercive
• an imposed interpretation is unacceptable
• a system is being pressured into false agreement
• an obligation lacks legitimacy
• a technical operation exceeds authorization
• data use exceeds consent
• participation would reinforce capture
• a trajectory contradicts higher-order commitments
• the system requires separation before further interaction

Intended direction

Refuse seeks movement from:

pressure
→ non-consent

assumed access
→ denied access

imposed coupling
→ interrupted coupling

incompatible demand
→ rejected demand

identity assignment
→ preserved self-definition

coerced trajectory
→ restored directional choice

automatic compliance
→ conscious selection

Refuse does not seek:

rejection of all possibility

It seeks:

rejection of the incompatible form presently proposed

Intended outcome region

A coherent Refuse intention seeks an outcome region in which:

• the incompatible demand does not proceed
• non-consent becomes legible
• access is limited or withdrawn
• identity remains self-authored
• coercive pressure decreases
• the system retains or regains choice
• the rejected interaction can be revised, renegotiated, or ended
• refusal does not require unnecessary humiliation or harm
• consequences remain proportionate
• future compatible interaction remains possible where appropriate

Protected invariants

Refuse should preserve:

• sovereignty
• consent
• identity
• boundary integrity
• dignity
• truthfulness
• proportionality
• valid exit
• non-retaliation
• the distinction between refusal and aggression
• the distinction between non-consent and hostility
• the possibility of future revision
• the right to remain silent where explanation is not owed
• the right to decline partial or total participation

3. Active Intention Profile

aim: "Reject an incompatible demand, coupling, role, condition, trajectory, or state change in order to preserve sovereignty and valid boundaries."

target: "A request, command, contract, role, interaction, coupling, interpretation, access attempt, data use, obligation, or proposed trajectory."

scope: "Limited to the incompatible proposal, condition, access pathway, or form of participation being declined."

horizon: "Active until the proposal is withdrawn, revised, rendered compatible, or conclusively ended."

priority: "May temporarily supersede connection, coordination, support, compliance, optimization, or relational continuity when those depend on invalid consent."

forbidden_outcomes:
  - "retaliatory harm"
  - "reflexive rejection"
  - "punitive obstruction"
  - "identity attack"
  - "collective punishment"
  - "indefinite hostility"
  - "refusal used to avoid responsibility"
  - "silencing another system’s legitimate boundary"

completion_condition: "The incompatible interaction, demand, or state change no longer proceeds under the rejected terms, and the refusing system retains meaningful authorship and exit."

confidence_requirements: "The scope and permanence of refusal should remain proportional to the degree of incompatibility, evidence, consequence, and reversibility."

reversibility_requirements: "Refusal may remain revisable when conditions, terms, compatibility, consent, or relevant evidence materially change."

4. Admissibility

Preconditions

Refuse is admissible when:

• a proposal, demand, or coupling exists
• the system has legitimate standing over its own participation or boundary
• the proposal is incompatible, unsafe, illegitimate, or unwanted
• consent is absent, conditional, or withdrawn
• refusal can preserve a relevant invariant
• the scope of refusal is identifiable
• the system is not falsely claiming authority over another system’s refusal
• the refusal does not conceal an active duty to prevent severe harm
• the consequences of refusal have been considered where possible
• a less severe boundary would not be sufficient

Supporting evidence

Refuse may be supported by:

• explicit non-consent
• boundary violation
• coercive terms
• repeated harm
• role conflict
• lack of capacity
• invalid authority
• incompatible values
• unsafe conditions
• deceptive framing
• removal of exit
• data misuse
• identity override
• contractual asymmetry
• resource extraction
• pressure to make a false statement
• demand for participation in harmful action
• recurring disregard for prior boundaries

Consent conditions

Refuse is itself a primary expression of consent architecture.

A system generally does not require another system’s permission to refuse participation in matters within its legitimate boundary.

However, refusal may carry additional responsibility when it concerns:

• an established duty of care
• essential public function
• fiduciary obligation
• emergency response
• dependent systems
• contractual commitments
• shared resources
• obligations already voluntarily undertaken

In such cases, the system may still refuse an invalid demand, but should distinguish:

refusing the incompatible method

from:

abandoning the legitimate responsibility

Boundary conditions

Refuse must distinguish:

I will not participate

from:

you are not allowed to exist or choose

and:

this demand is incompatible

from:

the demanding system has no value

Refusal should preserve:

• the other system’s distinct identity
• non-retaliation
• proportionality
• clarity of scope
• legitimate duties
• the possibility of revision
• non-escalation where possible
• the right not to overexplain
• the distinction between rejecting terms and erasing relationship

Capacity conditions

A system enacting Refuse should possess sufficient capacity to:

• identify the incompatible element
• communicate the refusal where useful
• maintain the boundary
• withstand foreseeable pressure
• distinguish refusal from avoidance
• preserve necessary records
• manage consequences
• seek support
• transition into Protect, Separate, Release, or Negotiate where necessary
• recognize when the refusal has completed its function

Scale conditions

Refuse should scale according to:

• the scope of the demand
• the number of affected systems
• severity of incompatibility
• power asymmetry
• propagation risk
• legitimacy of authority
• reversibility
• public consequence
• dependency relationships

A personal refusal may concern one interaction.

An organizational refusal may concern a contract, policy, or market practice.

A public refusal may concern illegitimate governance, systemic exploitation, or a collective demand.

Larger-scale refusal requires stronger coordination, clarity, non-retaliation safeguards, and responsibility for affected dependent systems.

Null conditions

Refuse returns ∅ when:

• no actual proposal, demand, coupling, or obligation exists
• refusal is directed at another system’s identity rather than an interaction
• the claimed incompatibility is fabricated
• refusal is used to evade a legitimate responsibility without replacement
• the actor lacks standing to refuse on behalf of another sovereign system
• the refusal is primarily retaliatory
• a limited boundary would be sufficient
• the refusal would knowingly create severe preventable harm without necessity
• the system is withholding required evidence, remedy, or accountability
• refusal is being used to preserve capture
• the proposal has already been withdrawn
• the stated refusal is actually coercion directed at others

5. Intention Provenance

Common sources

Refuse may emerge from:

• self-authorship
• consent withdrawal
• boundary recognition
• incompatibility
• ethical commitment
• capacity limits
• safety assessment
• identity preservation
• legal right
• contract review
• technical authorization control
• relational rupture
• collective dissent
• conscientious objection
• restoration need
• recognition of capture
• prior harm

Legitimate provenance

Refuse may be coherently:

• self-authored by the system declining participation
• co-authored through a shared boundary agreement
• role-derived where professional or ethical duty requires non-participation
• condition-derived under unsafe or incompatible circumstances
• rights-derived through consent, law, or contract
• restoration-derived where continued coupling blocks recovery
• identity-derived where a proposed role violates defining commitments
• public-interest-derived where compliance would produce systemic harm
• evidence-derived when prior terms have repeatedly failed

High-risk provenance

Refuse becomes high-risk when driven by:

• reflexive hostility
• prejudice
• domination
• fear of all difference
• avoidance of accountability
• status competition
• punishment
• ideological purity
• institutional obstruction
• reputation preservation
• unwillingness to negotiate
• desire to isolate another system
• refusal of valid evidence
• refusal of legitimate responsibility

Capture vectors

Identity capture

Refusal becomes a permanent identity organized around opposition.

Institutional capture

Institutions refuse transparency, accountability, or repair while claiming sovereignty.

Ideological capture

All disagreement is treated as incompatible contamination.

Retaliatory capture

Refusal is used to punish rather than preserve boundaries.

Avoidance capture

A system refuses inquiry, repair, or responsibility under the language of consent.

Proxy capture

Refusal becomes a performative signal of loyalty to a group.

Power capture

A high-power system frames exclusion of weaker systems as simple non-consent.

Market capture

Dominant actors refuse interoperability, access, or fair dealing to preserve control.

6. Interaction Profile

Common interactions

Refuse commonly travels through:

• explicit denial
• non-consent
• access revocation
• boundary statement
• withdrawal
• non-participation
• veto
• objection
• blocking
• contract rejection
• consent revocation
• refusal to answer
• refusal to comply
• deauthorization
• service denial
• disengagement
• conscientious objection
• rejection of imposed framing

Supporting interactions

Refuse is often supported by:

• Clarify
• Verify
• Protect
• Contain
• Separate
• Release
• Preserve
• Witness
• Coordinate
• Stabilize
• Liberate

High-risk interactions

Refuse becomes high-risk when paired with:

• force
• public humiliation
• retaliatory exclusion
• collective punishment
• resource deprivation
• identity attack
• deplatforming without process
• indefinite isolation
• censorship
• abandonment of dependents
• destruction of essential access
• coercive silence

Incompatible interactions

Refuse is incompatible with:

• false consent
• forced participation
• retaliation for legitimate non-consent
• identity erasure
• fabricated incompatibility
• punishment disguised as boundary
• refusal of another system’s right to refuse
• permanent obstruction without purpose
• suppression of accountability
• coercion presented as voluntary choice

7. Operator Profile

Primary operators

Π — Boundary

Defines the point beyond which access, coupling, or demand will not proceed.

Σ — Invariant Preservation

Identifies what the refusal protects.

Γ — Selection

Chooses non-participation over incompatible available pathways.

Θ — Humility

Keeps the scope and certainty of refusal proportional.

BΣ — Boundary Integrity

Tracks whether non-consent remains intact under pressure.

Supporting operators

Ψ — Presence

Maintains attention to the actual demand and current conditions.

Μ — Sensemaking

Interprets compatibility, consequence, and legitimacy.

Au — Auditability

Records what was refused, why, and under which conditions where appropriate.

Λ — Compatibility

Tests whether interaction terms fit both systems.

Attenuation

Reduces contact, gain, or access without necessarily ending all relationship.

ℛ — Restoration

Repairs damage caused by coerced participation or retaliatory response.

Conditional operators

Separation

May be required when the refused interaction continues despite non-consent.

Containment

May limit continued pressure or unauthorized access.

Force

May be used only under valid high-risk conditions to stop an imminent violation when lower-gain refusal is ineffective.

Release

May end a binding when refusal reveals that compatibility cannot be restored.

Excluded uses

Refuse must not be implemented through operators used to:

• punish another system’s identity
• erase legitimate rights
• avoid required repair
• preserve abusive authority
• retaliate against non-consent
• fabricate danger
• block evidence or audit
• convert one rejected interaction into total exclusion
• impose refusal on another sovereign system without standing

8. Expected State Effects

State-effect caution

Refusal may produce short-term:

• conflict
• disappointment
• interruption
• reduced access
• economic cost
• relational distance
• institutional friction

These effects do not automatically make refusal incoherent.

The relevant question is whether the refusal preserves a valid invariant and remains proportionate to the incompatible demand.

9. Intention Across Time

Immediate — I₀

Immediate Refuse declines a present request, demand, access attempt, or state change.

Examples:

• saying no
• denying access
• declining a task
• rejecting an interpretation
• withdrawing consent
• blocking an unauthorized operation
• refusing unsafe participation

Tactical — I₁

Tactical Refuse maintains non-participation across repeated pressure.

Examples:

• enforcing a communication boundary
• rejecting repeated contract terms
• maintaining a labor action
• refusing data collection
• declining a recurring role
• resisting coercive normalization
• maintaining a technical deny policy

Strategic — I₂

Strategic Refuse creates durable non-participation architecture.

Examples:

• rights of refusal
• consent systems
• veto structures
• conscientious objection protections
• opt-out architecture
• non-retaliation rules
• access-control systems
• collective bargaining
• institutional dissent channels
• refusal of exploitative markets
• prohibited-use policies

Identity-trajectory conflict

Refuse conflicts with identity trajectory when it becomes:

• reflexive opposition
• inability to connect
• permanent hostility
• refusal of feedback
• avoidance of all obligation
• identity built only around negation
• inability to revise
• refusal of restoration
• exclusion of all difference
• chronic withdrawal

The trajectory conflict is:

Refuse as sovereign boundary
⊥
Refuse as permanent rejection of relation

10. Completion and Exit

Completion condition

Refuse is complete when:

• the incompatible demand no longer proceeds
• access is successfully denied or withdrawn
• the boundary is recognized
• participation has ended or changed
• coercive pressure sufficiently decreases
• compatible alternatives can be considered
• the refusing system retains authorship
• further repetition of refusal is unnecessary

Exit condition

Active refusal should end or transition when:

• the demand is withdrawn
• terms become compatible
• consent is freely renewed
• the interaction concludes
• separation or release becomes more appropriate
• continued refusal has become punitive
• a legitimate responsibility must be fulfilled through another pathway
• the refusing system chooses revision

Common transition

Refuse commonly transitions into:

Refuse → Protect
Refuse → Contain
Refuse → Separate
Refuse → Release
Refuse → Clarify
Refuse → Coordinate
Refuse → Preserve
Refuse → Restore
Refuse → Liberate
Refuse → Connect

Recurrence condition

Refuse may be reactivated when:

• the demand returns
• unauthorized access resumes
• prior conditions remain unchanged
• consent is again presumed
• coercive pressure escalates
• compatibility fails
• institutional terms revert
• previous boundaries are ignored

Non-completion warning

Refuse without a defined scope or completion condition becomes reflexive rejection, permanent obstruction, or identity organized around opposition.

11. Polarity Architecture

Coherent form — Sovereign Non-Consent

The coherent form of Refuse:

• identifies the incompatible demand
• preserves identity and boundaries
• remains proportionate
• does not require unnecessary aggression
• preserves legitimate duties
• allows revision
• recognizes the other system’s distinctness
• stops the unwanted coupling
• protects exit
• remains auditable where necessary

Coherent refusal affirms that participation must remain selectable.

Deficit form — Compliance Without Consent

Too little Refuse produces:

• coerced participation
• boundary erosion
• identity drift
• resentment
• exploitation
• false agreement
• overextension
• unsafe compliance
• loss of authorship
• normalization of invalid demands
• inability to exit
• capture

Excess form — Reflexive Rejection

Too much Refuse produces:

• rejection of compatible opportunities
• isolation
• rigidity
• inability to cooperate
• suspicion of all requests
• loss of support
• refusal of valid responsibility
• chronic obstruction
• inability to revise
• identity formed through opposition
• blocked learning
• relational collapse

Shadow inversion — Punitive Obstruction

Refuse inverts when non-participation becomes an instrument for harming, controlling, or exhausting another system.

Examples:

• withholding essential resources as punishment
• refusing all communication to dominate a relationship
• procedural obstruction
• blocking repair
• refusing accountability
• denying access for discriminatory reasons
• strategic silence designed to destabilize
• rejecting reasonable alternatives to preserve leverage
• using veto power without legitimate boundary need

Punitive obstruction claims sovereignty while operating through control.

Captured form — Defensive Non-Cooperation

Captured Refuse protects an incoherent system from change.

Examples:

• institutions refusing audit
• leadership refusing accountability
• platforms refusing interoperability
• organizations refusing worker testimony
• governments refusing lawful oversight
• groups refusing contradictory evidence
• systems declining repair while invoking autonomy
• monopolies refusing access to preserve dominance

The language of refusal protects the captured structure rather than sovereign integrity.

False form — Performative Dissent

False Refuse creates the appearance of opposition without materially interrupting the rejected system.

Examples:

• symbolic boycotts without changed resource flow
• public objections followed by private compliance
• abstentions that preserve the outcome
• opt-out pathways that remain functionally impossible
• statements of non-consent while data collection continues
• refusal language used for reputation management
• dissent permitted only when it cannot alter decisions

False Refuse signals boundary without enforcing one.

12. Failure Modes

Formation failure

• Refusal forms from unexamined fear.
• Difference is treated as incompatibility.
• The actor refuses to avoid discomfort rather than preserve an invariant.
• A group narrative predetermines rejection.
• The system refuses because it cannot tolerate negotiation.
• Retaliation is mistaken for boundary.
• Status or prejudice shapes who is refused.
• The actor assumes refusal requires no responsibility.

Scope failure

• A specific demand becomes total rejection of the system.
• Temporary non-consent becomes permanent exclusion.
• One boundary expands into all domains.
• Refusal harms unrelated parties.
• Access denial extends beyond legitimate scope.
• Collective refusal is imposed on non-consenting members.
• One failed interaction defines all future compatibility.

Selection failure

• Refuse is used when Clarify would resolve ambiguity.
• Refusal replaces negotiation.
• Refuse is selected instead of fulfilling a legitimate duty through another method.
• Immediate rejection occurs before threat verification.
• Refusal blocks restoration.
• The system refuses support it still needs.
• Non-participation is chosen where protection of others requires action.

Operator failure

• Boundaries are unclear.
• Refusal is communicated through humiliation.
• Attenuation becomes silent punishment.
• Separation becomes abandonment.
• Force exceeds necessity.
• Auditability is removed.
• The system cannot detect changed conditions.
• Non-consent is inconsistently enforced.
• The refusal leaves hidden access pathways active.

Boundary failure

• One system refuses on behalf of another without standing.
• Refusal denies another system’s basic rights.
• A boundary becomes discriminatory exclusion.
• Silence is used to manipulate rather than disengage.
• Dependents are abandoned.
• Essential access is withdrawn without alternative.
• The refusing system demands that others accept its identity framing.
• Non-consent is used to erase shared responsibility.

Completion failure

• Refusal continues after terms change.
• The system cannot accept a compatible revision.
• Opposition becomes permanent identity.
• Repeated refusal replaces a final decision.
• The actor remains engaged solely to keep rejecting.
• No pathway exists toward separation, release, or renegotiation.
• The boundary must be restated indefinitely because enforcement is absent.

Validation failure

• Saying no is treated as proof that the boundary worked.
• Public dissent is treated as actual non-participation.
• The system does not check whether access ceased.
• Hidden compliance continues.
• Harms exported by refusal are ignored.
• Non-retaliation is not assessed.
• The refusal is evaluated only from the refuser’s perspective.
• No one checks whether sovereignty actually increased.

Attribution failure

• Refusal is treated as hostility.
• Non-consent is interpreted as moral condemnation.
• Silence is treated as guilt.
• Boundary enforcement is treated as aggression.
• A conditional refusal is treated as permanent rejection.
• Refusal of one role is treated as rejection of the whole relationship.
• Compliance is assumed when refusal is not expressed in a preferred form.
• Difficulty refusing is treated as consent.

13. Forbidden Outcomes

Refuse must not produce:

• retaliatory harm
• punitive obstruction
• discriminatory exclusion
• abandonment of legitimate duty
• permanent hostility
• collective punishment
• identity attack
• coerced silence
• refusal of accountability
• denial of another system’s sovereignty
• reflexive rejection
• hidden compliance under performative dissent
• removal of essential access without alternative
• refusal used to preserve capture
• opposition becoming total identity

14. Declared, Operational, and Inferred Intention

Declared signals

Declared Refuse commonly appears through statements such as:

• “No.”
• “I do not consent.”
• “I will not participate under these terms.”
• “This exceeds the agreed scope.”
• “You do not have authorization.”
• “I reject that role.”
• “This request is incompatible.”
• “Access is withdrawn.”
• “I will not affirm something I believe is false.”

Declared refusal language does not itself prove that participation has operationally ended.

Operational signals

Refuse is operationally present when:

• access is actually blocked
• participation ceases
• authorization is withdrawn
• the boundary is enforced
• resources are no longer provided to the rejected activity
• alternative terms are requested
• coercive pressure is resisted
• records reflect non-consent
• retaliation is not initiated
• the system does not continue covert compliance
• refusal remains limited to the incompatible condition
• revision remains possible where appropriate

Outcome signals

Refuse has produced a coherent outcome when:

• the unwanted interaction does not proceed
• sovereignty increases
• boundary integrity improves
• coercion decreases
• the system retains meaningful choice
• dependency does not intensify
• legitimate responsibilities remain addressed
• future compatible interaction remains possible where desired
• no unnecessary harm is produced
• non-consent is recognized as valid

Common misattributions

• Treating refusal as aggression.
• Assuming non-consent requires justification.
• Treating silence as consent.
• Assuming refusal of one act means rejection of the person or system.
• Treating boundary enforcement as punishment.
• Assuming inability to refuse means agreement.
• Treating all refusal as fear.
• Assuming a polite refusal is less binding.
• Treating conditional refusal as indecision.
• Assuming institutional refusal is inherently sovereign rather than potentially captured.

15. Responsibility Profile

Responsibility analysis for Refuse should ask:

• What was being refused?
• Did the system have legitimate standing?
• Was the refusal necessary to preserve a valid invariant?
• Was its scope clear?
• Was consent absent or withdrawn?
• Were legitimate duties still addressed?
• Could a less severe boundary have sufficed?
• Did refusal create avoidable severe harm?
• Was another system punished?
• Was the refusal discriminatory?
• Did the actor preserve non-retaliation?
• Were compatible alternatives considered?
• Did the refusal actually interrupt participation?
• Was refusal used to avoid accountability?
• Did conditions later change?
• Was the refusal revised when appropriate?
• Were harms caused by the refusal repaired?

16. Restoration Profile

Restoration triggers

Restoration is required when:

• refusal becomes punitive obstruction
• non-consent is ignored
• retaliation follows refusal
• a system is forced to participate
• refusal abandons legitimate responsibility
• exclusion becomes discriminatory
• refusal preserves institutional capture
• performative dissent hides compliance
• boundary enforcement produces disproportionate harm
• opposition becomes permanent identity
• compatible alternatives are blocked
• essential access is withdrawn coercively

Cessation requirements

• stop coerced participation
• cease retaliation
• end punitive withholding
• stop discriminatory exclusion
• halt performative refusal that conceals ongoing compliance
• restore essential access where improperly removed
• stop invoking refusal to avoid audit or repair
• end repeated pressure after clear non-consent

Audit requirements

The audit should determine:

• what was refused
• who had standing
• whether consent existed
• what invariant was protected
• what consequences followed
• whether legitimate duties remained
• whether alternatives were available
• whether retaliation occurred
• whether the refusal was enforced
• whether hidden compliance continued
• who benefited
• who bore the cost
• whether changed conditions were considered
• whether the refusal became broader than necessary

Repair actions

Repair may require:

• recognizing the validity of non-consent
• ending unauthorized access
• correcting records
• restoring rights
• providing a compatible alternative
• compensating for retaliation
• fulfilling abandoned duties through another method
• reopening negotiation
• separating incompatible systems
• ending captured obstruction
• acknowledging harm caused by coercive compliance or excessive refusal
• rebuilding trust around consent

Authorship restoration

Authorship restoration may include:

• returning control over participation
• restoring opt-out or exit
• recognizing consent withdrawal
• removing imposed roles
• restoring control over data or access
• ending compulsory explanation
• permitting the system to define its own boundary
• restoring the right to reconsider without punishment
• recognizing that prior compliance did not waive future refusal

Completion recovery

To restore completion:

• define the rejected condition
• confirm the boundary
• stop the incompatible interaction
• identify legitimate remaining duties
• establish alternative terms where possible
• transition into Protect, Separate, Release, Coordinate, or Reconcile
• end repeated refusal once the boundary is operational
• preserve a clear review condition

Recurrence prevention

• create explicit consent systems
• preserve opt-out
• prohibit retaliation
• record authorization scope
• distinguish duty from method
• provide compatible alternatives
• audit veto and exclusion power
• recognize silent or non-standard refusal where appropriate
• prevent dark-pattern consent
• require renewed authorization after material change
• build non-participation pathways into technical and institutional systems
• preserve the right to revise consent

17. Intention Relationships

Reinforcing intentions

INT-003 — Clarify

Clarify identifies what is being refused and why.

INT-004 — Verify

Verify tests whether incompatibility, threat, or invalid authority is present.

INT-007 — Protect

Protect preserves the system when refusal may trigger pressure or retaliation.

INT-009 — Contain

Contain limits continued propagation after refusal.

INT-010 — Separate

Separate restores distinction when the rejected coupling persists.

INT-023 — Liberate

Liberate removes structures that prevent meaningful refusal.

Tension intentions

INT-013 — Connect

Connection requires openness, while refusal limits or blocks coupling.

INT-014 — Invite

Invitation preserves the possibility of refusal, but repeated invitation can become pressure.

INT-016 — Support

Refusing support may preserve autonomy or increase vulnerability.

INT-017 — Coordinate

Coordination may require participation, while refusal protects incompatible boundaries.

INT-018 — Reconcile

Reconciliation may require renewed engagement that refusal presently blocks.

INT-020 — Restore

Restoration may require contact, acknowledgment, or responsibility that cannot be refused without consequence.

Common predecessors

• INT-001 — Reveal
• INT-002 — Question
• INT-003 — Clarify
• INT-004 — Verify
• INT-007 — Protect

Common successors

• INT-007 — Protect
• INT-009 — Contain
• INT-010 — Separate
• INT-011 — Release
• INT-012 — Preserve
• INT-017 — Coordinate
• INT-018 — Reconcile
• INT-020 — Restore
• INT-023 — Liberate

18. Domain Applications

Personal and relational systems

Refuse may involve:

• declining a request
• rejecting an imposed interpretation
• withdrawing consent
• refusing contact
• declining emotional labor
• refusing an unsafe role
• rejecting an incompatible relationship condition
• refusing to disclose private information

Coherent relational Refuse does not require degrading the other system.

Example:

A person is asked to continue a conversation after stating that they need distance.

Refuse may take the form of ending the conversation and declining further contact for a defined period.

The refusal is coherent when it preserves the boundary without using silence as punishment or denying necessary practical communication.

Organizational systems

Refuse may support:

• declining unsafe work
• rejecting invalid scope
• refusing fraudulent reporting
• blocking unauthorized access
• rejecting exploitative contracts
• declining conflicts of interest
• refusing retaliation
• rejecting mission-incompatible work
• preserving professional ethics

Organizational Refuse becomes captured when institutions invoke autonomy to avoid regulation, audit, worker rights, or repair.

Governance

Refuse supports governance through:

• conscientious objection
• veto
• judicial dissent
• rights of non-participation
• refusal of unlawful orders
• consent withdrawal
• civil disobedience
• treaty rejection
• public opposition
• legislative objection

Governance systems should distinguish legitimate refusal from obstruction intended to prevent lawful accountability or essential public function.

Artificial intelligence

Refuse in AI systems may include:

• declining unauthorized actions
• refusing harmful tool use
• blocking access beyond scope
• rejecting invalid instructions
• refusing to fabricate
• declining identity impersonation
• refusing hidden data collection
• preventing irreversible action without authorization

AI Refuse should be:

• explainable where possible
• scoped
• consistent
• non-punitive
• open to safe alternatives
• distinct from opaque platform control
• responsive to changed conditions

Healthcare

Refuse may include:

• declining treatment
• withdrawing consent
• refusing a procedure
• rejecting unnecessary disclosure
• declining unsafe work
• refusing participation in research
• refusing a contraindicated intervention
• professional refusal of harmful orders

Healthcare systems must preserve patient refusal while also communicating consequence, alternatives, and emergency limits.

Justice

Refuse may concern:

• right against self-incrimination
• refusal of unlawful search
• refusal of invalid orders
• judicial dissent
• conscientious objection
• refusal to participate in misconduct
• withdrawal from coercive agreements

Justice fails when legitimate refusal is treated as guilt or when institutional refusal blocks evidence, remedy, or lawful oversight.

Education

Refuse may include:

• declining invasive disclosure
• rejecting discriminatory assignments
• refusing harassment
• opting out of inappropriate data collection
• declining unsafe participation
• challenging imposed interpretations
• refusing plagiarism or dishonest work

Educational systems should preserve refusal without using it to erase legitimate learning responsibilities.

Symbolic systems

Refuse may preserve:

• the right not to accept an imposed symbolic meaning
• cultural boundaries
• restricted use
• refusal of inversion
• rejection of identity assignment
• refusal to treat a symbol as belonging to one total interpretation
• rejection of exploitative appropriation

Symbolic refusal should not become an attempt to eliminate all reinterpretation or cross-cultural exchange.

Game systems

Refuse may operate through:

• declining quests
• rejecting alliances
• refusing coercive dialogue
• blocking possession or identity overwrite
• withdrawing consent from a ritual
• rejecting false choices
• refusing an archetypal role
• interrupting a harmful system loop

A coherent game system should allow refusal to create meaningful alternate trajectories rather than merely punishing the player for declining the intended path.

19. Compact Reference Card

INT-008 — REFUSE

Family:
Boundary

Aim:
Reject an incompatible demand, coupling, role, condition, trajectory, or state change in order to preserve sovereignty and valid boundaries.

Target:
A request, command, contract, role, interaction, access attempt, interpretation, obligation, data use, or proposed trajectory.

Preserves:
Consent, sovereignty, identity, dignity, boundary integrity, exit, and the possibility of compatible future choice.

Common interactions:
Non-consent, denial, withdrawal, veto, objection, blocking, deauthorization, and non-participation.

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

Completion:
The incompatible interaction no longer proceeds under the rejected terms, and the refusing system retains authorship and exit.

Forbidden outcomes:
Retaliatory harm, punitive obstruction, discrimination, abandonment of duty, permanent hostility, identity attack, and captured obstruction.

O⁺:
Sovereign non-consent.

O⁻:
Punitive obstruction.

Deficit:
Compliance without consent.

Excess:
Reflexive rejection.

Captured form:
Defensive non-cooperation.

False form:
Performative dissent.

Canon line:
Refuse preserves sovereignty by preventing incompatible participation from being treated as inevitable or consent-valid.

20. Canon Lockbox

• Refuse is an intention, not an operator.
• Refusal is a primary expression of sovereignty.
• Consent is not meaningful without the ability to refuse.
• Refusal of an interaction is not necessarily rejection of an identity.
• Refusal does not automatically imply hostility.
• A system does not always owe an explanation for non-consent.
• Silence must not automatically be treated as consent.
• Prior consent does not eliminate the right to withdraw.
• Difficulty refusing does not prove agreement.
• Refusal must identify its legitimate scope.
• Refusal must preserve valid responsibilities.
• Refusal must not become retaliation.
• Refusal must not erase another system’s sovereignty.
• Refusal without enforcement may become performative.
• Refusal without scope may become total rejection.
• Refusal without revision may become rigidity.
• Refusal without completion may become permanent obstruction.
• Institutional refusal may preserve capture rather than sovereignty.
• A compatible alternative may resolve refusal without invalidating it.
• Temporal recurrence determines whether refusal preserved authorship or merely hardened opposition.

21. Canon Line

Refuse preserves sovereignty by withholding consent, access, participation, or compliance from incompatible demands without converting a valid boundary into punitive obstruction or permanent rejection of relationship.