Intention Registry Entry v1.0

Registry ID: INT-007

Title: Protect

Family: Boundary

Status: Draft

Version: 1.0.0

Primary function: Preserve identity, safety, boundary integrity, function, continuity, or restoration capacity against credible disruption while retaining agency, proportionality, and exit.

0. Canonical Definition

Protect is the intention to preserve a system, boundary, relationship, function, identity, or restoration capacity against credible disruption, degradation, capture, or harm.

Protect seeks to maintain the conditions under which a system can remain itself, continue functioning, recover, and choose.

It may concern:

• bodily safety
• identity continuity
• boundary integrity
• relational safety
• technical resilience
• institutional legitimacy
• data integrity
• privacy
• vulnerable populations
• cultural continuity
• system stability
• restoration capacity
• source protection
• memory preservation
• future possibility

Protect does not mean preventing all change.

It seeks to prevent or reduce changes that would destroy, capture, degrade, or irreversibly constrain what should remain available.

Protection becomes coherent when it preserves:

• agency
• consent
• identity
• proportionality
• reversibility
• restoration
• valid exit
• the ability to resume fuller participation after threat decreases

1. Foundational Principle

Protection preserves the conditions under which a system can remain itself, recover, and continue choosing.

Protection is not merely resistance to harm.

Its deeper function is preservation of future possibility.

A system may survive immediate disruption while losing:

• authorship
• dignity
• memory
• autonomy
• capacity
• trust
• meaningful exit
• restoration potential

Such survival is incomplete.

The basic movement of Protect is:

credible disruption
→ bounded defensive response
→ preserved invariants
→ reduced threat
→ restored agency

Protection therefore operates through a double requirement:

reduce credible harm

while also:

avoid becoming a greater source of harm

Protection must not destroy the very qualities it claims to preserve.

2. Directional Function

Starting condition

Protect commonly arises when:

• a credible threat is present
• a boundary has been crossed
• identity is vulnerable to override
• restoration capacity is declining
• sensitive information may be exposed
• a system cannot safely remain open
• trust has been materially breached
• harm is propagating
• a vulnerable system lacks sufficient defense
• coercive pressure is narrowing choice
• system continuity is at risk
• a relationship requires temporary distance
• an institution is failing to preserve those under its care
• technical failure may become irreversible
• latent risk is sufficiently probable and severe to justify prevention

Intended direction

Protect seeks movement from:

exposure
→ bounded safety

threat
→ reduced threat

boundary breach
→ restored boundary integrity

capture risk
→ preserved authorship

fragility
→ resilient continuity

uncontrolled propagation
→ constrained propagation

loss of restoration capacity
→ preserved recovery pathway

Protect does not seek:

maximum restriction

It seeks:

the minimum sufficient protection required to preserve relevant invariants

Intended outcome region

A coherent Protect intention seeks an outcome region in which:

• credible threat is reduced
• valid boundaries remain intact
• the protected system retains meaningful agency
• identity is preserved
• avoidable harm is prevented
• restoration capacity remains available
• exposure is proportional to capability
• restrictions remain temporary where possible
• exit remains available
• the protected system can later resume broader function
• defensive measures do not become permanent control
• protection does not export greater harm elsewhere

Protected invariants

Protect should preserve:

• identity
• agency
• consent
• boundary integrity
• restoration capacity
• proportionality
• truthfulness
• reversibility
• auditability
• valid exit
• dignity
• future participation
• the distinction between protection and control
• the distinction between safety and suppression

3. Active Intention Profile

aim: "Preserve a system, boundary, relationship, function, identity, or restoration capacity against credible disruption, degradation, capture, or harm."

target: "A person, system, relationship, boundary, function, body, identity, record, environment, institution, or recovery process."

scope: "Limited to the minimum sufficient range required to reduce credible harm and preserve relevant invariants."

horizon: "Active only while the relevant threat, vulnerability, or recovery condition remains."

priority: "May temporarily supersede optimization, expansion, access, convenience, or speed when those aims would increase credible harm."

forbidden_outcomes:
  - "identity override"
  - "indefinite control"
  - "dependency creation"
  - "disproportionate restriction"
  - "removal of meaningful exit"
  - "suppression presented as safety"
  - "exported harm"
  - "permanent emergency authority"

completion_condition: "Credible threat is sufficiently reduced, boundary integrity is restored, and the protected system retains or regains meaningful agency and exit."

confidence_requirements: "Protective gain must remain proportional to evidence, severity, probability, uncertainty, and reversibility."

reversibility_requirements: "Protective restrictions should remain reversible unless irreversibility is required to prevent a greater irreversible harm."

4. Admissibility

Preconditions

Protect is admissible when:

• a credible threat, vulnerability, or boundary violation exists
• the protected value can be identified
• the expected harm is material
• the protective response is proportionate
• the actor has legitimate standing or invitation
• the intervention preserves agency where possible
• a less restrictive sufficient option has been considered
• restoration capacity can be preserved
• the protection does not create greater systemic harm
• completion and exit conditions can be defined
• uncertainty is reflected in the level of intervention

Supporting evidence

Protect may be supported by:

• direct threat
• repeated boundary violation
• documented exploitation
• technical vulnerability
• escalating harm
• observable coercion
• loss of system function
• credible warning indicators
• recurrence
• power asymmetry
• breached agreement
• consent withdrawal
• source exposure risk
• declining restoration capacity
• verified environmental hazard
• demonstrated inability to safely absorb further disruption

Consent conditions

Consent is generally required when protection affects another system’s:

• movement
• access
• body
• identity
• communication
• data
• relationships
• decision-making
• participation
• property
• private life

Protection may proceed without full prior consent only under narrowly bounded conditions such as:

• imminent severe harm
• temporary incapacity
• protection of a child or dependent system
• immediate technical containment
• legal duty
• urgent preservation of life or critical infrastructure

Even then:

• scope must remain minimal
• the intervention must be auditable
• agency should be restored quickly
• the protected system should be informed
• review and appeal should follow
• emergency authority should expire

Boundary conditions

Protect must distinguish:

supporting another system’s safety

from:

assuming permanent authority over that system

and:

reducing exposure

from:

eliminating participation

Protection should preserve:

• self-authorship
• refusal
• informed consent
• audience boundaries
• access limits
• temporal limits
• review
• appeal
• restoration pathways
• the distinction between temporary protection and permanent custody

Capacity conditions

A system enacting Protect should possess sufficient capacity to:

• assess threat
• distinguish probability from certainty
• choose proportionate measures
• maintain boundaries
• protect sensitive information
• preserve records
• communicate reasons
• review ongoing necessity
• repair unintended harm
• withdraw restrictions
• restore agency
• avoid escalating the threat through poor intervention

Scale conditions

Protect should scale according to:

• severity
• probability
• irreversibility
• affected population
• power asymmetry
• propagation rate
• restoration capacity
• available alternatives
• confidence
• externalized cost

A private relational boundary may require limited separation.

A technical vulnerability may require system-wide containment.

A public safety threat may justify broader intervention, but broader scope requires stronger evidence, auditability, review, and sunset conditions.

Null conditions

Protect returns ∅ when:

• no credible threat is present
• the proposed response is disproportionate
• the protected value cannot be identified
• protection requires identity replacement
• the protected system refuses and no valid emergency condition exists
• the intervention primarily serves the protector’s control
• the response exports greater harm
• the same purpose can be achieved through a less restrictive measure
• the actor lacks standing or capacity
• restrictions lack completion and exit conditions
• fear is being treated as sufficient evidence
• the threat has ended
• protection is being used to avoid accountability or change
• the protective structure has itself become the dominant threat

5. Intention Provenance

Common sources

Protect may emerge from:

• self-preservation
• care
• stewardship
• professional duty
• guardianship
• risk assessment
• boundary recognition
• consent withdrawal
• safety review
• system monitoring
• institutional responsibility
• source protection
• environmental stewardship
• restoration planning
• relational commitment
• technical resilience
• public responsibility

Legitimate provenance

Protect may be coherently:

• self-authored by the system seeking safety
• invited by another system
• co-authored through mutual agreement
• role-derived through legitimate care, stewardship, or fiduciary duty
• condition-derived in response to credible threat
• emergency-derived under imminent danger
• restoration-derived where recovery requires temporary shielding
• public-interest-derived where preventable harm would affect many systems
• boundary-derived when consent or access has been violated

High-risk provenance

Protect becomes high-risk when driven by:

• fear
• paternalism
• ownership
• institutional self-preservation
• reputation management
• ideological purity
• permanent emergency logic
• economic extraction
• surveillance incentives
• intolerance of uncertainty
• possessiveness
• avoidance of accountability
• desire to restrict competition
• desire to preserve hierarchy

Capture vectors

Paternalistic capture

The protector substitutes its own preferences for the protected system’s authorship.

Institutional capture

Protection language is used to preserve the institution rather than those it claims to serve.

Security capture

Temporary risk response becomes permanent authority.

Reputation capture

Exposure of wrongdoing is treated as a threat to be contained.

Dependency capture

The protected system is kept weak so protection remains necessary.

Boundary capture

The protector defines all boundaries unilaterally.

Commercial capture

Safety requirements are shaped to preserve market control or data access.

Identity capture

Protection becomes justification for deciding who another system is allowed to become.

6. Interaction Profile

Common interactions

Protect commonly travels through:

• boundary setting
• refusal
• shielding
• attenuation
• containment
• access control
• warning
• separation
• redaction
• encryption
• stabilization
• support
• intervention
• monitoring
• safe exit
• risk reduction
• environmental modification
• resource preservation

Supporting interactions

Protect is often supported by:

• Reveal
• Question
• Clarify
• Verify
• Remember
• Refuse
• Contain
• Separate
• Preserve
• Support
• Stabilize
• Restore

High-risk interactions

Protect becomes high-risk when paired with:

• force
• confinement
• surveillance
• identity assignment
• permanent monitoring
• involuntary isolation
• secrecy
• censorship
• resource restriction
• compulsory dependence
• unreviewable authority
• irreversible exclusion

Incompatible interactions

Protect is incompatible with:

• deliberate harm
• fabricated threat
• identity replacement
• removal of all exit
• permanent emergency authority
• concealment of protector misconduct
• coercive fusion
• domination
• disproportionate punishment
• suppression of valid testimony
• protection claims that cannot be audited

7. Operator Profile

Primary operators

Π — Boundary

Defines and enforces legitimate limits on access, coupling, exposure, and propagation.

Σ — Invariant Preservation

Identifies what must remain intact through the protective response.

Θ — Humility

Matches intervention strength to evidence and uncertainty.

BΣ — Boundary Integrity

Tracks whether protection preserves valid identity and consent boundaries.

ℛ — Restoration

Ensures protection serves recovery rather than permanent restriction.

Supporting operators

Ψ — Presence

Maintains awareness of actual threat and current state.

Μ — Sensemaking

Interprets risk, vulnerability, and changing conditions provisionally.

Au — Auditability

Makes protective decisions and effects traceable.

Γ — Selection

Chooses the minimum sufficient response.

Λ — Compatibility

Determines whether support, proximity, or coupling remains safe.

Attenuation

Reduces incoming or outgoing gain.

Containment

Limits propagation of harm.

Conditional operators

Force

May be used only under valid high-risk gates where severe harm is imminent and lower-gain methods are insufficient.

Separation

May be required where continued contact sustains harm.

Amplification

May be used to strengthen warning, defense, or public response when threat scales.

Excluded uses

Protect must not be implemented through operators used to:

• create permanent subordination
• erase identity
• preserve institutional reputation over harmed systems
• remove all review
• fabricate risk
• keep the protected system dependent
• prevent lawful exit
• conceal evidence
• punish dissent
• define all participation as danger

8. Expected State Effects

State-effect caution

Protection may temporarily reduce:

• access
• coupling
• movement
• visibility
• participation
• speed
• openness

This does not automatically indicate incoherence.

The relevant test is whether the restriction is:

• necessary
• proportionate
• temporary
• auditable
• agency-preserving
• restoration-oriented

9. Intention Across Time

Immediate — I₀

Immediate Protect responds to a present threat or breach.

Examples:

• blocking unauthorized access
• stopping harmful contact
• moving out of immediate danger
• redacting sensitive data
• pausing a destabilizing process
• reinforcing a boundary
• warning an affected system

Tactical — I₁

Tactical Protect preserves safety across a recovery or transition period.

Examples:

• maintaining temporary separation
• securing a technical system
• preserving evidence
• limiting exposure during restoration
• protecting a source
• supporting a vulnerable person
• reducing environmental risk
• establishing supervised access

Strategic — I₂

Strategic Protect builds durable resilience.

Examples:

• secure infrastructure
• rights frameworks
• consent architecture
• redundancy
• disaster planning
• privacy systems
• protected reporting channels
• institutional safeguards
• ecological stewardship
• durable restoration capacity
• resilient communities
• security by design

Identity-trajectory conflict

Protect conflicts with identity trajectory when it becomes:

• permanent fear
• isolation
• refusal of all uncertainty
• domination
• dependency
• suppression
• inability to connect
• avoidance of development
• rigid self-enclosure
• permanent emergency identity

The trajectory conflict is:

Protect as preservation of possibility
⊥
Protect as elimination of possibility

10. Completion and Exit

Completion condition

Protect is complete when:

• credible threat is sufficiently reduced
• boundary integrity is restored
• immediate exposure is controlled
• the protected system retains or regains agency
• restoration capacity is available
• restrictions are no longer necessary at their current level
• the next intention can proceed
• future risk is managed through durable rather than emergency measures

Exit condition

Active protection should end or reduce when:

• threat falls below the relevant threshold
• the protected system can safely resume authorship
• less restrictive measures become sufficient
• restoration has established a workable baseline
• the protective intervention produces more harm than benefit
• the protector’s standing ends
• review determines that the threat was misclassified
• the remaining issue belongs to Stabilize, Restore, Support, Release, or Preserve

Common transition

Protect commonly transitions into:

Protect → Stabilize
Protect → Restore
Protect → Support
Protect → Preserve
Protect → Clarify
Protect → Verify
Protect → Release
Protect → Reconcile
Protect → Integrate

Recurrence condition

Protect may be reactivated when:

• threat returns
• boundary violations recur
• restoration capacity declines
• new vulnerabilities emerge
• conditions materially change
• prior safeguards fail
• power asymmetry increases
• evidence shows that the danger was not fully resolved

Non-completion warning

Protect without a valid exit condition becomes control, confinement, dependency, or permanent emergency authority.

11. Polarity Architecture

Coherent form — Boundary Preservation

The coherent form of Protect:

• responds to credible harm
• remains proportionate
• preserves identity
• retains agency and exit
• protects restoration capacity
• uses the least restrictive sufficient measure
• remains auditable
• ends when the threat ends
• supports eventual participation
• avoids exporting greater harm

Coherent protection preserves the protected system rather than replacing it.

Deficit form — Neglect

Too little Protect produces:

• preventable exposure
• boundary collapse
• exploitation
• avoidable injury
• privacy loss
• source endangerment
• system fragility
• recurring harm
• inability to recover
• failure of stewardship
• abandonment of vulnerable systems
• uncontained propagation

Excess form — Overprotection

Too much Protect produces:

• loss of agency
• isolation
• rigidity
• permanent restriction
• inability to learn
• dependency
• reduced resilience
• excessive monitoring
• fear-driven governance
• blocked connection
• suppressed experimentation
• inability to resume normal function

Shadow inversion — Domination

Protect inverts when preserving safety becomes a claim to control another system.

Examples:

• making decisions without consent
• permanent confinement
• censorship framed as safety
• surveillance framed as care
• removing access to alternatives
• restricting relationships
• using vulnerability to justify ownership
• suppressing testimony
• preserving institutions instead of affected systems
• refusing to return authority

Domination claims that the protected system is safer only when it is no longer sovereign.

Captured form — Institutional Self-Protection

Captured Protect preserves the system exercising power rather than the systems exposed to harm.

Examples:

• concealing misconduct to preserve trust
• silencing complaints to protect reputation
• protecting leadership from accountability
• restricting users while leaving infrastructure insecure
• classifying evidence as sensitive to avoid scrutiny
• treating criticism as a security threat
• preserving operational continuity at the expense of worker safety
• shielding abusive structures from consequence

False form — Safety Theater

False Protect creates the appearance of safety without materially reducing risk.

Examples:

• visible procedures without functional safeguards
• warnings without repair
• excessive user restrictions while backend vulnerabilities remain
• symbolic compliance
• surveillance without actual prevention
• emergency drills disconnected from real capacity
• policies that transfer liability rather than reduce harm
• security language without evidence
• barriers that inconvenience low-risk users while high-risk pathways remain open

False Protect increases visible control while leaving actual vulnerability intact.

12. Failure Modes

Formation failure

• Fear is mistaken for evidence.
• The protector assumes another system is incapable.
• Reputation risk is treated as safety risk.
• Uncertainty is treated as danger.
• The protected value is never identified.
• The protector seeks control or possession.
• A temporary vulnerability becomes total identity.
• Threat models exclude the harm created by protection itself.

Scope failure

• Protection expands beyond the threat.
• Temporary restrictions become permanent.
• A local hazard justifies system-wide control.
• Safety rules spread to unrelated domains.
• Access limitations continue after recovery.
• One protected system externalizes harm onto another.
• Emergency authority becomes normalized.

Selection failure

• Protect is used when Clarify or Verify is needed.
• Restriction replaces Support.
• Containment is chosen where Release is appropriate.
• Protection delays necessary transformation.
• The system protects a harmful structure from accountability.
• Immediate force is selected before lower-gain options.
• Self-protection replaces responsibility.

Operator failure

• Force exceeds necessity.
• Boundaries are unilateral.
• Auditability is removed.
• Attenuation suppresses valid signals.
• Containment blocks repair.
• Restoration is omitted.
• Threat monitoring becomes surveillance.
• Separation becomes abandonment.
• Protective systems cannot detect when the threat ends.

Boundary failure

• Consent is ignored.
• Exit is removed.
• Identity is overwritten.
• Privacy is invaded beyond necessity.
• The protected system cannot appeal.
• Information is withheld paternalistically.
• the protector gains indefinite access.
• temporary custody becomes permanent authority.

Completion failure

• No exit condition exists.
• Risk thresholds continually change.
• Protection becomes identity.
• The protector refuses to return control.
• restrictions remain after the threat ends.
• emergency procedures replace ordinary governance.
• the system cannot transition into restoration or participation.

Validation failure

• Amount of restriction is treated as proof of safety.
• Absence of visible incident is treated as proof of effectiveness.
• compliance is treated as reduced harm.
• protected systems are not asked whether agency remained.
• long-term dependency is ignored.
• hidden costs are externalized.
• no comparison is made with less restrictive alternatives.
• threat reduction is not measured.

Attribution failure

• Boundary setting is treated as hostility.
• Refusal of protection is treated as irrationality.
• Accepting protection is treated as incapacity.
• Harm occurring despite protection is treated as proof of malicious intent.
• a protector’s stated care is assumed to prove coherent operation.
• resistance to control is framed as danger.
• vulnerability is treated as permanent identity.

13. Forbidden Outcomes

Protect must not produce:

• identity override
• indefinite control
• permanent emergency authority
• dependency creation
• removal of meaningful exit
• disproportionate restriction
• suppression presented as safety
• exported harm
• institutional self-protection
• surveillance without necessity
• censorship of valid testimony
• abandonment after separation
• forced isolation
• safety theater
• protection that prevents restoration or development

14. Declared, Operational, and Inferred Intention

Declared signals

Declared Protect commonly appears through statements such as:

• “This needs to be kept safe.”
• “We need to prevent further harm.”
• “The boundary must be preserved.”
• “Access should be limited.”
• “This system is too vulnerable right now.”
• “We need a temporary protective measure.”
• “The source must remain confidential.”
• “Restoration cannot continue under active threat.”

Declared protective language does not itself prove coherent protection.

Operational signals

Protect is operationally present when:

• threat is defined
• evidence is documented
• measures are proportionate
• agency is preserved
• less restrictive options are considered
• the protected system can respond
• review and appeal exist
• restrictions decrease with threat
• restoration capacity improves
• protector authority is limited
• hidden costs are included
• the same safeguards apply to high-power systems

Outcome signals

Protect has produced a coherent outcome when:

• credible harm decreases
• boundary integrity improves
• identity remains intact
• the system retains meaningful choice
• restoration can proceed
• vulnerability declines
• dependency does not increase
• protective authority ends appropriately
• normal participation resumes where possible
• future resilience increases
• the protective system itself remains accountable

Common misattributions

• Assuming restriction always means protection.
• Treating safety language as proof of benign intent.
• Treating refusal as lack of judgment.
• Assuming more control creates more safety.
• Treating privacy as obstruction.
• Assuming vulnerability removes authorship.
• Treating surveillance as protection by default.
• Assuming no visible incident proves the measure worked.
• Treating boundary setting as aggression.
• Assuming protection must be permanent to be effective.

15. Responsibility Profile

Responsibility analysis for Protect should ask:

• Was a credible threat present?
• What exactly was being protected?
• Who selected the intervention?
• Did the protector have legitimate standing?
• Was consent obtained where possible?
• Was the response proportionate?
• Were less restrictive options available?
• Was agency preserved?
• Was exit maintained?
• Did the intervention export harm?
• Did protection become dependency?
• Was restoration capacity preserved?
• Were threat and effectiveness audited?
• Did restrictions end when no longer necessary?
• Was false classification corrected?
• Did the protector benefit from continued control?
• Were harms caused by protection repaired?

16. Restoration Profile

Restoration triggers

Restoration is required when:

• protection becomes domination
• restrictions continue after the threat ends
• agency is removed
• exit is blocked
• surveillance exceeds necessity
• safety claims conceal institutional self-protection
• dependency increases
• valid testimony is suppressed
• harm is exported
• vulnerable identity becomes permanent classification
• protection prevents development or connection
• emergency authority becomes normalized

Cessation requirements

• stop unnecessary restrictions
• return decision authority
• end disproportionate surveillance
• restore access where safe
• withdraw emergency powers
• cease paternalistic control
• stop suppressing complaints
• separate valid protection from institutional reputation management
• discontinue measures that produce greater harm

Audit requirements

The audit should determine:

• what threat justified protection
• what evidence supported it
• who defined the protected value
• whose consent was sought
• what measures were used
• whether alternatives existed
• who benefited
• who bore the cost
• whether threat declined
• whether restrictions changed accordingly
• whether agency and exit remained
• whether the protective system created new harm
• whether authority expanded beyond scope

Repair actions

Repair may require:

• restoring access
• returning authority
• ending confinement
• correcting risk classification
• deleting improperly collected data
• compensating for harm
• acknowledging overreach
• restoring relationships
• rebuilding trust
• repairing capacity lost through overprotection
• creating independent review
• addressing the original threat more directly
• strengthening genuine resilience

Authorship restoration

Authorship restoration may include:

• returning choice to the protected system
• restoring informed consent
• allowing refusal
• providing full information
• restoring control over data and identity
• ending compulsory dependence
• re-establishing meaningful exit
• allowing the system to define its own acceptable risk
• recognizing the right to resume participation

Completion recovery

To restore completion:

• restate the threat
• identify the protected invariant
• define measurable reduction
• establish a sunset condition
• reduce restrictions as risk falls
• transition into Stabilize, Restore, Support, Preserve, or Release
• return authority
• close the protective intervention

Recurrence prevention

• require threat evidence
• define proportionality
• use sunset clauses
• preserve appeal
• audit protector incentives
• separate safety from reputation
• review dependency effects
• maintain least-restrictive-means standards
• measure actual harm reduction
• preserve exit
• build restoration into protection
• ensure protective systems are themselves observable
• prevent emergency powers from becoming ordinary authority

17. Intention Relationships

Reinforcing intentions

INT-004 — Verify

Verify tests whether the threat is credible and whether protection is effective.

INT-008 — Refuse

Refuse rejects harmful or incompatible coupling.

INT-009 — Contain

Contain limits propagation when threat cannot yet be removed.

INT-010 — Separate

Separate restores distinction when contact or fusion sustains harm.

INT-012 — Preserve

Preserve maintains what protection keeps intact through time.

INT-021 — Stabilize

Stabilize establishes a workable baseline after immediate threat is reduced.

Tension intentions

INT-001 — Reveal

Reveal may increase accountability while threatening privacy or source safety.

INT-006 — Learn

Learning may require exposure and experimentation that protection limits.

INT-013 — Connect

Connection may increase support or reopen vulnerability.

INT-019 — Transform

Transformation may require disruption that protection resists.

INT-023 — Liberate

Protection may support liberation or become the structure from which liberation is required.

INT-024 — Create

Creation may require risk, openness, and experimentation.

Common predecessors

• INT-001 — Reveal
• INT-002 — Question
• INT-003 — Clarify
• INT-004 — Verify
• INT-005 — Remember

Common successors

• INT-008 — Refuse
• INT-009 — Contain
• INT-010 — Separate
• INT-012 — Preserve
• INT-016 — Support
• INT-020 — Restore
• INT-021 — Stabilize
• INT-011 — Release

18. Domain Applications

Personal and relational systems

Protect may involve:

• setting a boundary
• declining contact
• limiting access to private information
• leaving an unsafe environment
• preserving recovery time
• protecting another person’s confidence
• reducing exposure during conflict
• seeking support

Coherent relational Protect does not require controlling another person’s identity or choices.

Example:

A relationship enters a period of recurring harm.

Protection may involve temporary distance, clear communication boundaries, and limited contact while the affected systems determine whether restoration is possible.

The protection remains coherent when it preserves agency, does not become punishment, and includes a review point.

Organizational systems

Protect may support:

• worker safety
• information security
• whistleblower protection
• financial controls
• continuity planning
• privacy
• anti-retaliation systems
• infrastructure resilience
• incident response
• legal safeguards
• intellectual property stewardship
• preservation of critical knowledge

Organizational Protect becomes captured when leadership reputation is protected while workers, users, or affected communities remain exposed.

Governance

Protect supports governance through:

• rights protection
• public safety
• due process
• emergency response
• environmental protection
• infrastructure security
• privacy law
• consumer protection
• vulnerable-population safeguards
• disaster planning

Governance protection requires:

• legal scope
• evidence
• proportionality
• review
• transparency
• sunset conditions
• restoration of ordinary rights after emergency

Artificial intelligence

Protect in AI systems may include:

• preventing unauthorized access
• protecting private data
• refusing harmful operations
• preserving user control
• sandboxing risky tools
• limiting irreversible actions
• shielding systems from prompt injection
• maintaining audit logs
• detecting unsafe state changes
• protecting memory integrity

AI Protect should not become justification for:

• hidden platform control
• unnecessary data retention
• opaque refusal
• identity inference
• restriction without explanation
• removal of user exit

Healthcare

Protect may include:

• infection control
• privacy
• emergency intervention
• medication safeguards
• informed consent
• prevention
• isolation during contagion
• protection from contraindicated treatment
• preserving recovery capacity
• safeguarding vulnerable patients

Healthcare Protect must remain proportionate and must not erase patient authorship.

Justice

Protect may concern:

• witness protection
• victim safety
• rights preservation
• evidence protection
• due process
• prevention of retaliation
• safe custody
• public protection
• protection from wrongful state action

Justice fails when “protection” becomes indefinite confinement, rights removal, or suppression of evidence.

Education

Protect may include:

• safe learning environments
• privacy
• anti-harassment boundaries
• age-appropriate exposure
• protection from retaliation
• safeguarding student records
• preserving space for inquiry
• reducing preventable harm

Educational protection should not eliminate challenge, curiosity, or learner autonomy.

Symbolic systems

Protect may preserve:

• symbolic integrity
• cultural context
• sacred boundaries
• provenance
• legitimate stewardship
• meaning from inversion
• symbols from exploitative use
• the distinction between public and restricted knowledge

Symbolic protection should not become ownership over all interpretation.

Game systems

Protect may operate through:

• shields
• barriers
• sanctuary zones
• temporary separation
• defensive symbols
• protection of NPCs
• preservation of memory
• safeguarding restoration processes
• boundary mechanics
• containment of corruption

A coherent game system should show that protection has costs, scope, and completion rather than treating defense as unlimited invulnerability.

19. Compact Reference Card

INT-007 — PROTECT

Family:
Boundary

Aim:
Preserve a system, boundary, identity, function, relationship, or restoration capacity against credible disruption, degradation, capture, or harm.

Target:
A person, system, relationship, boundary, body, identity, record, environment, institution, or recovery process.

Preserves:
Identity, agency, consent, boundary integrity, restoration capacity, proportionality, auditability, and exit.

Common interactions:
Boundary setting, refusal, shielding, attenuation, containment, access control, warning, separation, and stabilization.

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

Completion:
Credible threat is sufficiently reduced, boundary integrity is restored, and agency and exit remain or return.

Forbidden outcomes:
Identity override, indefinite control, dependency, disproportionate restriction, surveillance, suppression, and permanent emergency authority.

O⁺:
Boundary preservation.

O⁻:
Domination.

Deficit:
Neglect.

Excess:
Overprotection.

Captured form:
Institutional self-protection.

False form:
Safety theater.

Canon line:
Protect preserves the conditions under which a system can remain itself, recover, and continue choosing.

20. Canon Lockbox

• Protect is an intention, not an operator.
• Protection must identify a credible protected value.
• Protection must identify a credible threat.
• Fear alone does not establish threat.
• Protection must remain proportional.
• Protection must preserve agency wherever possible.
• Protection must preserve valid exit.
• Protection must include restoration.
• Protection should use the least restrictive sufficient measure.
• Vulnerability does not erase authorship.
• Safety language does not prove protective operation.
• More restriction does not automatically create more safety.
• Protection without auditability becomes opaque authority.
• Protection without completion becomes control.
• Protection without exit becomes confinement.
• Protection without restoration becomes permanent restriction.
• Protection that creates dependency undermines future sovereignty.
• Protection that shields institutions from accountability is captured.
• Protection must decrease as threat decreases.
• Temporal recurrence determines whether protection built resilience or merely preserved fear and control.

21. Canon Line

Protect preserves the conditions under which a system can remain itself, reduce credible harm, recover, and continue choosing without converting safety into domination or permanent control.