Intention Registry Entry v1.0

Registry ID: INT-009

Title: Contain

Family: Boundary

Status: Draft

Version: 1.0.0

Primary function: Limit the propagation, amplification, reach, or secondary effects of harm, instability, breach, contamination, or incoherent state while preserving auditability, proportionality, and restoration potential.

0. Canonical Definition

Contain is the intention to limit the spread, amplification, reach, or secondary effects of a harmful, unstable, breached, contaminated, or incoherent state without treating temporary restriction as permanent resolution.

Contain does not necessarily remove the source.

Its first task is to prevent the condition from expanding beyond its present boundaries while the system:

• assesses cause
• protects affected systems
• preserves evidence
• stabilizes critical functions
• prepares restoration
• determines whether separation, repair, release, or transformation is required

Contain may concern:

• physical hazard
• technical compromise
• data breach
• infectious process
• environmental contamination
• financial instability
• misinformation propagation
• relational escalation
• institutional misconduct
• identity capture
• emotional amplification
• symbolic inversion
• conflict
• cascading system failure
• resource loss
• unsafe coupling

Contain becomes coherent when it reduces propagation while preserving:

• truth
• identity
• agency
• auditability
• valid exit
• review
• restoration
• proportionality
• the possibility of reopening once the condition is resolved

1. Foundational Principle

What cannot yet be safely resolved must first be prevented from spreading.

Containment creates a workable boundary around an unresolved condition.

Its basic movement is:

unbounded propagation
→ bounded field
→ reduced amplification
→ preserved observability
→ restoration pathway

Containment protects the wider system from secondary harm while preserving enough of the affected state to understand and repair it.

This requires a distinction between:

limiting spread

and:

hiding the problem

between:

temporary restriction

and:

permanent confinement

and between:

preserving the system

and:

isolating the affected system indefinitely

Containment is therefore an intermediate intention.

It is rarely the final state.

Its legitimacy depends on what it makes possible next.

2. Directional Function

Starting condition

Contain commonly arises when:

• harm is actively propagating
• a breach remains open
• instability is cascading
• a source cannot yet be safely removed
• a system is amplifying an incoherent signal
• contamination may spread
• a conflict is escalating
• a compromised subsystem threatens the larger whole
• sensitive information is dispersing
• an unsafe interaction cannot immediately be resolved
• evidence may be destroyed
• a technical process is producing uncontrolled outputs
• institutional misconduct is recurring across units
• a damaged system requires isolation during repair
• immediate removal would create greater harm
• the full cause remains uncertain but propagation is observable

Intended direction

Contain seeks movement from:

propagation
→ bounded spread

amplification
→ reduced gain

open breach
→ controlled perimeter

cascading failure
→ localized failure

uncontrolled exposure
→ limited exposure

escalating interaction
→ restricted interaction

unstable field
→ auditable bounded field

Contain does not seek:

permanent isolation

It seeks:

the minimum sufficient boundary required to prevent further harm while resolution becomes possible

Intended outcome region

A coherent Contain intention seeks an outcome region in which:

• propagation slows or stops
• secondary harm decreases
• critical systems remain available
• evidence is preserved
• the affected condition becomes more observable
• boundaries are clear
• access is limited to legitimate roles
• restoration can proceed
• restrictions remain proportional
• the affected system is not abandoned
• the containment field can later be reduced or dissolved
• the source can be addressed without greater spread

Protected invariants

Contain should preserve:

• identity
• auditability
• proportionality
• restoration capacity
• source integrity
• evidence
• valid privacy
• agency where possible
• review
• temporal limitation
• distinction between cause and affected carrier
• distinction between containment and punishment
• distinction between restriction and erasure
• the possibility of reintegration or release

3. Active Intention Profile

aim: "Limit the propagation, amplification, reach, or secondary effects of a harmful, unstable, breached, contaminated, or incoherent state."

target: "A process, signal, breach, hazard, conflict, subsystem, relationship, data flow, contamination field, or propagating pattern."

scope: "Limited to the minimum sufficient boundary required to prevent further spread while preserving observability and restoration."

horizon: "Active only while propagation risk remains above the relevant threshold or until the source is resolved."

priority: "May temporarily supersede access, connection, expansion, speed, convenience, or ordinary participation when those would increase spread."

forbidden_outcomes:
  - "permanent confinement"
  - "abandonment of the contained system"
  - "concealment presented as containment"
  - "identity reduction"
  - "punitive isolation"
  - "indefinite emergency authority"
  - "destruction of evidence"
  - "containment without restoration"

completion_condition: "Propagation is sufficiently controlled, the source is identified or stabilized, and a viable restoration, separation, release, or reintegration pathway exists."

confidence_requirements: "Containment strength must remain proportional to observed propagation, severity, uncertainty, reversibility, and available alternatives."

reversibility_requirements: "Containment measures should remain reducible and removable as risk declines unless irreversible action is necessary to prevent greater irreversible harm."

4. Admissibility

Preconditions

Contain is admissible when:

• active or credible propagation exists
• the spread can be meaningfully bounded
• immediate resolution is unavailable or unsafe
• containment reduces expected harm
• the proposed boundary is proportionate
• evidence and state can remain observable
• restoration remains possible
• the actor has legitimate standing
• the contained system is not treated as disposable
• completion and review conditions can be defined
• a less restrictive sufficient measure is unavailable

Supporting evidence

Contain may be supported by:

• active spread
• repeated transmission
• open technical compromise
• escalating conflict
• measurable contamination
• compromised access credentials
• cascading system errors
• uncontrolled replication
• verified secondary harm
• boundary breach
• rapid amplification
• cross-system recurrence
• compromised supply chain
• information leakage
• instability exceeding local restoration capacity
• inability to safely remove the source immediately

Consent conditions

Consent is generally required when containment restricts another system’s:

• movement
• access
• communication
• data
• participation
• bodily autonomy
• property
• relationships
• work
• public visibility

Consent may be limited under conditions such as:

• imminent severe harm
• infectious spread
• active technical breach
• public safety emergency
• evidence preservation
• protection of dependent systems
• prevention of irreversible contamination

Even then:

• authority must remain bounded
• reasons should be disclosed
• review must occur
• restrictions must decrease with risk
• the affected system must retain rights and care
• containment must not become abandonment

Boundary conditions

Contain must distinguish:

limiting the spread of a condition

from:

treating the affected system as the condition itself

and:

temporarily limiting access

from:

removing all meaningful rights

Containment should preserve:

• dignity
• care
• auditability
• due process
• source distinction
• access to restoration
• information
• appeal
• review
• temporal limits
• the right to reintegration where possible

Capacity conditions

A system enacting Contain should possess sufficient capacity to:

• define the propagation boundary
• monitor state
• preserve evidence
• distinguish source from carrier
• provide necessary care
• prevent escape pathways
• maintain records
• review necessity
• repair contained harm
• reduce restrictions
• identify transition conditions
• avoid exporting the hazard elsewhere

Scale conditions

Contain should scale according to:

• propagation rate
• severity
• irreversibility
• affected population
• system interdependence
• observability
• restoration capacity
• time sensitivity
• confidence
• cost of failure

A local relational escalation may require temporary reduced contact.

A technical breach may require network segmentation.

A public hazard may require regional controls.

Broader containment requires stronger:

• evidence
• legal standing
• auditability
• resource support
• review
• sunset conditions
• compensation
• restoration planning

Null conditions

Contain returns ∅ when:

• no meaningful propagation exists
• the condition can be directly resolved safely
• the proposed boundary exceeds the actual risk
• containment primarily hides institutional failure
• the affected system is being punished
• restoration is not planned
• the actor lacks standing
• the same goal can be achieved through a less restrictive measure
• the contained system would be abandoned
• the measure exports greater harm
• the threat has ended
• the containment architecture has become the primary source of harm
• evidence is being destroyed
• identity is being reduced to risk classification

5. Intention Provenance

Common sources

Contain may emerge from:

• incident response
• public safety
• infection control
• technical security
• environmental protection
• conflict de-escalation
• evidence preservation
• boundary defense
• institutional oversight
• crisis management
• relational stabilization
• restoration planning
• resource protection
• source isolation
• risk containment
• data governance

Legitimate provenance

Contain may be coherently:

• self-authored by a system limiting its own propagation
• co-authored through shared safety agreement
• role-derived through legitimate stewardship or emergency duty
• condition-derived in response to active spread
• evidence-derived when transmission or cascading harm is observed
• restoration-derived when a damaged system requires bounded recovery
• public-interest-derived when secondary harm affects many systems
• boundary-derived where an open breach must be closed
• technical-derived where compromised subsystems require segmentation

High-risk provenance

Contain becomes high-risk when driven by:

• stigma
• punishment
• reputation management
• institutional concealment
• fear
• prejudice
• permanent emergency logic
• political suppression
• censorship
• desire to isolate dissent
• resource denial
• ownership
• avoidance of root-cause repair
• desire to remove inconvenient systems

Capture vectors

Punitive capture

Containment becomes punishment without a restoration pathway.

Institutional capture

An institution isolates evidence, complainants, or affected groups to preserve itself.

Security capture

Temporary containment becomes permanent surveillance or authority.

Stigma capture

The affected system is treated as identical to the hazard.

Concealment capture

The problem is hidden from public view rather than bounded for repair.

Resource capture

The contained system is denied support, ensuring continued dependency or failure.

Political capture

Containment language is used to suppress dissent or opposition.

Proxy capture

Visible restriction is measured while actual propagation continues elsewhere.

6. Interaction Profile

Common interactions

Contain commonly travels through:

• isolation
• segmentation
• quarantine
• throttling
• access control
• rate limiting
• redaction
• sandboxing
• separation
• de-escalation
• communication limits
• resource partitioning
• evidence preservation
• temporary suspension
• perimeter establishment
• circuit breaking
• monitoring
• controlled transfer

Supporting interactions

Contain is often supported by:

• Reveal
• Verify
• Protect
• Refuse
• Separate
• Stabilize
• Preserve
• Support
• Restore
• Coordinate
• Release

High-risk interactions

Contain becomes high-risk when paired with:

• force
• confinement
• secrecy
• censorship
• surveillance
• resource deprivation
• indefinite detention
• public stigmatization
• total communication shutdown
• abandonment
• identity classification
• irreversible exclusion

Incompatible interactions

Contain is incompatible with:

• destruction of evidence
• abandonment
• fabricated threat
• punishment without process
• permanent emergency status
• identity erasure
• hidden propagation
• denial of restoration
• unrestricted authority
• containment used solely to protect reputation
• deliberate export of harm

7. Operator Profile

Primary operators

Π — Boundary

Creates the perimeter within which propagation is limited.

Attenuation

Reduces gain, intensity, or transmission.

Σ — Invariant Preservation

Protects what must remain intact during restriction.

Au — Auditability

Preserves visibility into state, decisions, access, and effects.

ℛ — Restoration

Ensures containment serves recovery rather than indefinite restriction.

Supporting operators

Ψ — Presence

Maintains awareness of the actual state inside and outside the boundary.

Μ — Sensemaking

Interprets source, propagation, and evolving risk.

Γ — Selection

Chooses the minimum sufficient containment measure.

Θ — Humility

Matches restriction to uncertainty and evidence.

Δ — Differentiation

Separates source, carrier, affected system, and secondary effect.

BΣ — Boundary Integrity

Tracks whether the containment perimeter remains coherent.

Λ — Compatibility

Determines whether limited reintegration is safe.

Conditional operators

Force

May be used only under a valid high-risk gate where imminent severe propagation cannot otherwise be stopped.

Separation

May be required when continued coupling sustains transmission.

Amplification

May be used for warnings, coordination, or public response when containment depends on wider awareness.

Compression

May reduce system load during crisis if critical structure remains intact.

Excluded uses

Contain must not be implemented through operators used to:

• erase the contained system
• conceal institutional responsibility
• destroy evidence
• create indefinite confinement
• deny all care
• remove review
• export the hazard
• suppress valid testimony
• equate affected identity with harmful state
• preserve emergency authority after risk declines

8. Expected State Effects

State-effect caution

Containment may make the bounded condition appear more concentrated.

distributed harm
→ bounded harm

may increase the visible density of the problem within the containment field while reducing total propagation.

This does not necessarily mean the condition worsened.

However, concentration becomes incoherent when the contained system is denied:

• resources
• care
• ventilation
• review
• communication
• restoration
• exit conditions

9. Intention Across Time

Immediate — I₀

Immediate Contain limits active spread.

Examples:

• isolating a compromised device
• pausing a harmful interaction
• restricting access to leaked data
• separating parties during escalation
• stopping movement through a contaminated area
• disabling a propagating process

Tactical — I₁

Tactical Contain maintains a bounded field during assessment and repair.

Examples:

• network segmentation
• quarantine
• controlled communication
• preserving evidence
• limiting financial exposure
• isolating a compromised organizational unit
• maintaining temporary relational distance
• restricting distribution of sensitive information

Strategic — I₂

Strategic Contain builds durable anti-propagation architecture.

Examples:

• compartmentalized systems
• circuit breakers
• public-health infrastructure
• ecological buffer zones
• incident-response frameworks
• safe reporting channels
• risk partitioning
• sandboxed AI tools
• layered access control
• anti-cascade financial systems
• conflict de-escalation protocols
• modular infrastructure

Identity-trajectory conflict

Contain conflicts with identity trajectory when it becomes:

• permanent isolation
• fear-based enclosure
• loss of participation
• identity reduction
• abandonment
• surveillance
• inability to reconnect
• permanent emergency state
• confinement as identity
• avoidance of root-cause repair

The trajectory conflict is:

Contain as temporary boundary
⊥
Contain as permanent exclusion

10. Completion and Exit

Completion condition

Contain is complete when:

• propagation is sufficiently controlled
• the source is identified, stabilized, or removed
• evidence is preserved
• the affected field is auditable
• restoration can proceed safely
• secondary harm is no longer expanding
• restrictions can begin to decrease
• a transition into Restore, Separate, Release, or Reintegrate is available

Exit condition

Active containment should end or reduce when:

• propagation falls below threshold
• the source is resolved
• less restrictive measures become sufficient
• safe reintegration becomes possible
• the measure causes greater harm than the remaining risk
• review shows that the threat was misclassified
• the contained system can safely resume function
• restoration has established a stable baseline

Common transition

Contain commonly transitions into:

Contain → Stabilize
Contain → Restore
Contain → Separate
Contain → Release
Contain → Protect
Contain → Preserve
Contain → Support
Contain → Coordinate
Contain → Integrate

Recurrence condition

Contain may be reactivated when:

• spread resumes
• the source reappears
• boundaries fail
• new transmission pathways emerge
• restoration proves incomplete
• the condition changes form
• affected systems remain unsafe
• secondary effects return

Non-completion warning

Contain without a transition, review, and exit condition becomes permanent confinement, concealment, or abandonment.

11. Polarity Architecture

Coherent form — Bounded Harm

The coherent form of Contain:

• limits propagation
• preserves observability
• remains proportionate
• protects identity
• provides care
• supports restoration
• preserves evidence
• defines review and exit
• reduces restrictions as risk falls
• avoids exporting harm

Coherent containment stabilizes the field long enough for a more complete response.

Deficit form — Uncontrolled Propagation

Too little Contain produces:

• cascading failure
• widespread contamination
• repeated transmission
• secondary victims
• evidence loss
• runaway amplification
• system-wide instability
• uncontrolled breach
• escalating conflict
• irreversible spread
• depletion of restoration capacity
• collapse of critical boundaries

Excess form — Overcontainment

Too much Contain produces:

• excessive isolation
• resource deprivation
• reduced function
• loss of agency
• blocked communication
• permanent emergency logic
• delayed restoration
• oversegmentation
• inability to reconnect
• stigmatization
• confinement beyond risk
• institutional rigidity

Shadow inversion — Permanent Confinement

Contain inverts when temporary boundary becomes indefinite restriction without proportionate review or restoration.

Examples:

• indefinite detention
• permanent quarantine
• endless account restriction
• organizational blacklisting
• isolation without care
• institutionalization without exit
• continuous suspension
• permanent exclusion based on prior risk
• containment after the threat has ended

Permanent confinement treats risk status as identity.

Captured form — Concealment

Captured Contain protects the dominant system by hiding the existence, source, or scale of harm.

Examples:

• isolating whistleblowers
• suppressing incident reports
• sealing records
• quarantining reputational risk
• silencing affected communities
• containing public knowledge rather than technical harm
• hiding contamination instead of remediating it
• isolating symptoms while leaving causes untouched

False form — Perimeter Theater

False Contain creates visible boundaries without materially limiting spread.

Examples:

• symbolic access controls
• ineffective quarantine
• network segmentation with hidden shared credentials
• communication bans that push activity into unmonitored channels
• visible barriers around the wrong source
• temporary shutdowns without remediation
• policy containment while operational pathways remain open
• incident closure while recurrence continues

False Contain restricts appearance while leaving propagation intact.

12. Failure Modes

Formation failure

• Fear is mistaken for active propagation.
• The affected system is mistaken for the source.
• Institutional reputation is treated as the protected field.
• A temporary anomaly is treated as systemic contamination.
• Containment begins before relevant differentiation.
• The actor assumes isolation itself is resolution.
• Stigma determines who is contained.
• Threat models exclude the harm of confinement.

Scope failure

• The boundary expands beyond the actual propagation field.
• A local incident triggers system-wide restriction.
• Temporary containment becomes permanent policy.
• Unrelated systems are restricted.
• The contained condition is generalized to identity.
• Resources are withheld beyond necessity.
• Public knowledge is contained along with actual harm.

Selection failure

• Contain is used when direct repair is possible.
• Isolation replaces Support.
• Containment delays Release.
• A relational conflict is contained when Clarify or Reconcile is needed.
• Evidence is sealed instead of preserved.
• Containment protects the institution from accountability.
• The root cause remains active outside the boundary.

Operator failure

• The perimeter is porous.
• Auditability is removed.
• Attenuation suppresses warning signals.
• Separation becomes abandonment.
• Resource support is insufficient.
• Monitoring becomes surveillance.
• The wrong subsystem is isolated.
• Propagation pathways remain active.
• Restoration is not initiated.

Boundary failure

• Rights are removed without necessity.
• Appeal is absent.
• The contained system lacks information.
• Identity is reduced to risk.
• Communication is completely severed.
• Care is withheld.
• The boundary cannot be reviewed.
• Dependents are abandoned.
• Private containment becomes public stigma.

Completion failure

• No exit threshold exists.
• The source is never addressed.
• Restrictions continue after risk declines.
• containment becomes the permanent operating model.
• Review repeatedly extends authority.
• Reintegration is never attempted.
• the system remains isolated because restoration resources were never provided.
• emergency status becomes normalized.

Validation failure

• Visible restriction is treated as reduced propagation.
• Lack of reported incidents is treated as success.
• concealed spread is ignored.
• actual transmission is not measured.
• contained-system harm is excluded.
• restoration progress is not tracked.
• perimeter compliance replaces outcome assessment.
• recurrence after release is never studied.

Attribution failure

• The contained system is treated as the cause.
• Risk status is treated as guilt.
• Need for containment is treated as malicious intent.
• Resistance to confinement is treated as proof of danger.
• prior exposure becomes permanent identity.
• failure of containment is blamed on those contained rather than system design.
• public disclosure is treated as propagation even when it supports accountability.

13. Forbidden Outcomes

Contain must not produce:

• permanent confinement
• abandonment
• identity reduction
• punitive isolation
• concealment of institutional harm
• destruction of evidence
• indefinite emergency authority
• deprivation of necessary care
• export of harm
• stigmatization
• suppression of valid testimony
• blocked restoration
• overcontainment
• perimeter theater
• reintegration made impossible

14. Declared, Operational, and Inferred Intention

Declared signals

Declared Contain commonly appears through statements such as:

• “We need to stop this from spreading.”
• “This system should be isolated temporarily.”
• “Access must be restricted.”
• “The breach needs to be bounded.”
• “We need to preserve evidence.”
• “The situation must be stabilized before reopening.”
• “This process should be sandboxed.”
• “Further propagation would create greater harm.”

Declared containment language does not itself prove that spread is being reduced.

Operational signals

Contain is operationally present when:

• the propagation pathway is identified
• boundaries are actually enforced
• transmission decreases
• evidence is preserved
• critical resources continue
• the contained system receives support
• monitoring remains relevant
• restrictions are reviewed
• root-cause work begins
• less restrictive measures replace stronger ones as risk declines
• exit conditions remain visible
• institutional responsibility is not concealed

Outcome signals

Contain has produced a coherent outcome when:

• secondary harm declines
• propagation stops or slows
• the affected field becomes more observable
• critical systems remain intact
• evidence survives
• restoration can proceed
• the contained system retains dignity and a future pathway
• restrictions decline with risk
• recurrence is reduced
• the source is addressed
• reintegration or release becomes possible

Common misattributions

• Assuming isolation always means containment.
• Treating visible boundaries as proof of effectiveness.
• Treating the contained system as the source.
• Assuming containment resolves the underlying cause.
• Treating resistance as proof of danger.
• Assuming secrecy is necessary for containment.
• Treating public accountability as harmful propagation.
• Assuming stronger restriction always reduces spread.
• Treating temporary risk as permanent identity.
• Assuming containment without restoration is sufficient.

15. Responsibility Profile

Responsibility analysis for Contain should ask:

• What is propagating?
• What evidence supports active spread?
• What exactly is being contained?
• Is the affected system also the source?
• Did the actor have legitimate standing?
• Was the boundary proportionate?
• Were less restrictive options available?
• Was care preserved?
• Was evidence protected?
• Was restoration initiated?
• Did the measure conceal institutional responsibility?
• Was harm exported?
• Were review and appeal available?
• Did restrictions decline with risk?
• Was the source addressed?
• Did containment become permanent?
• Were harms caused by containment repaired?

16. Restoration Profile

Restoration triggers

Restoration is required when:

• containment becomes permanent confinement
• the affected system is abandoned
• evidence is concealed or destroyed
• risk classification becomes identity
• care is denied
• institutional harm is hidden
• restrictions continue after spread ends
• reintegration is blocked
• containment exports harm
• surveillance exceeds necessity
• root cause remains untouched
• perimeter theater allows continued propagation

Cessation requirements

• stop unnecessary restrictions
• restore communication
• provide care and resources
• end concealment
• suspend invalid risk classification
• withdraw emergency authority
• restore access where safe
• stop punitive isolation
• halt measures that no longer reduce spread
• expose and address root causes

Audit requirements

The audit should determine:

• what condition was contained
• whether it was propagating
• who defined the boundary
• what evidence supported it
• whether the source was correctly identified
• who was restricted
• what support was provided
• whether spread declined
• whether harm was exported
• whether evidence was preserved
• whether institutional interests shaped the response
• whether exit conditions existed
• whether restoration occurred
• whether reintegration was attempted

Repair actions

Repair may require:

• ending confinement
• restoring rights
• providing delayed care
• correcting risk classifications
• reopening communication
• compensating for harm
• restoring data or access
• exposing concealed institutional failure
• repairing trust
• remediating the actual source
• creating a safe reintegration pathway
• rebuilding lost function
• preserving records of overreach

Authorship restoration

Authorship restoration may include:

• returning decision authority
• restoring informed participation
• allowing the contained system to contest classification
• restoring control over data
• ending compulsory isolation
• permitting self-description
• rebuilding exit
• restoring relationships and access
• recognizing the contained system as more than the risk event

Completion recovery

To restore completion:

• identify the actual propagation field
• define the source
• establish measurable reduction
• provide restoration resources
• define review intervals
• reduce restrictions
• transition into Restore, Separate, Release, Support, or Integrate
• close the containment authority
• preserve recurrence monitoring without permanent control

Recurrence prevention

• build layered boundaries
• preserve observability
• define sunset conditions
• separate care from punishment
• audit institutional concealment incentives
• distinguish source from carrier
• measure actual spread
• preserve evidence
• maintain reintegration pathways
• review risk classifications
• resource restoration inside containment
• prevent emergency authority from becoming permanent
• test containment architecture through recurrence

17. Intention Relationships

Reinforcing intentions

INT-004 — Verify

Verify determines whether active propagation exists and whether containment works.

INT-007 — Protect

Protect preserves systems at risk from spread.

INT-008 — Refuse

Refuse blocks further access, participation, or transmission.

INT-010 — Separate

Separate restores distinction between affected or incompatible systems.

INT-021 — Stabilize

Stabilize creates a workable baseline within the contained field.

INT-020 — Restore

Restore addresses the damage and source after propagation is controlled.

Tension intentions

INT-001 — Reveal

Reveal may increase accountability while containment may restrict dissemination.

INT-013 — Connect

Connection may support recovery or reopen propagation pathways.

INT-016 — Support

Support requires access that containment may limit.

INT-017 — Coordinate

Coordination may be necessary, but excessive coupling can increase spread.

INT-023 — Liberate

Containment may preserve safety or become the structure from which liberation is needed.

INT-024 — Create

Creation may require openness and experimentation that containment restricts.

Common predecessors

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

Common successors

• INT-010 — Separate
• INT-011 — Release
• INT-012 — Preserve
• INT-016 — Support
• INT-017 — Coordinate
• INT-020 — Restore
• INT-021 — Stabilize
• INT-022 — Integrate

18. Domain Applications

Personal and relational systems

Contain may involve:

• pausing an escalating conversation
• limiting contact
• separating a specific topic from the wider relationship
• preventing private information from spreading
• establishing temporary communication rules
• isolating a harmful interaction pattern
• protecting other relationships from spillover

Example:

A conflict becomes too amplified for coherent dialogue.

Contain may involve ending the conversation for the present, limiting communication to essential matters, and preserving notes about unresolved issues.

The containment remains coherent when it supports later clarification or reconciliation rather than becoming indefinite silence or punishment.

Organizational systems

Contain may support:

• incident isolation
• suspension of compromised processes
• access restriction
• financial loss limitation
• evidence preservation
• anti-retaliation measures
• temporary removal from sensitive duties
• crisis communication boundaries
• contamination control
• legal hold
• operational segmentation

Organizational containment becomes captured when the institution contains disclosure rather than the underlying harm.

Governance

Contain supports governance through:

• emergency response
• public-health quarantine
• environmental exclusion zones
• financial circuit breakers
• conflict de-escalation
• infrastructure isolation
• evidence preservation
• temporary movement restrictions
• controlled access to hazardous areas

Governance containment requires:

• lawful authority
• necessity
• proportionality
• support
• review
• sunset conditions
• remedy
• reintegration

Artificial intelligence

Contain in AI systems may include:

• sandboxing tools
• isolating compromised agents
• restricting permissions
• rate limiting
• disabling unsafe workflows
• quarantining corrupted memory
• containing prompt injection
• separating untrusted outputs
• preventing autonomous propagation
• preserving logs during incident response

AI containment should not become indefinite opaque restriction or justification for hidden platform control.

Healthcare

Contain may include:

• infection-control isolation
• limiting exposure
• protecting sterile fields
• controlling contamination
• restricting contraindicated interactions
• stabilizing acute conditions
• preserving samples and records
• preventing transmission

Healthcare containment must include care, communication, review, and release criteria.

Justice

Contain may concern:

• separating parties during immediate danger
• evidence preservation
• witness safety
• temporary restrictions
• limiting ongoing criminal harm
• controlled custody
• preventing retaliation
• containing institutional misconduct

Justice fails when temporary containment becomes indefinite punishment without due process or restoration.

Education

Contain may include:

• pausing harmful behavior
• separating an escalating conflict
• limiting access to sensitive systems
• preventing harassment from spreading
• preserving learning continuity during incidents
• protecting student data
• containing misinformation while teaching verification

Educational containment should not isolate learners permanently or substitute exclusion for support and repair.

Symbolic systems

Contain may preserve:

• restricted symbolic knowledge
• sacred boundaries
• contextual use
• protection from uncontrolled inversion
• limited circulation of incomplete interpretations
• separation between symbol families
• containment of harmful amplification

Symbolic containment should not become monopolistic control over meaning.

Game systems

Contain may operate through:

• sealing corrupted zones
• isolating unstable artifacts
• limiting enemy spread
• pausing a ritual
• containing an archetypal inversion
• restricting access to unsafe layers
• stabilizing world-state boundaries
• preserving NPCs during an event

A coherent game system should make containment temporary and connect it to restoration, investigation, or release rather than treating sealed spaces as forgotten content.

19. Compact Reference Card

INT-009 — CONTAIN

Family:
Boundary

Aim:
Limit the propagation, amplification, reach, or secondary effects of a harmful, unstable, breached, contaminated, or incoherent state.

Target:
A process, signal, breach, hazard, conflict, subsystem, relationship, data flow, contamination field, or propagating pattern.

Preserves:
Identity, auditability, evidence, proportionality, restoration capacity, care, review, and the possibility of reintegration.

Common interactions:
Isolation, segmentation, throttling, quarantine, access control, rate limiting, separation, de-escalation, and evidence preservation.

Primary operators:
Π, Attenuation, Σ, Au, ℛ.

Completion:
Propagation is sufficiently controlled, the source is stabilized or identified, and a restoration, release, separation, or reintegration pathway exists.

Forbidden outcomes:
Permanent confinement, abandonment, concealment, identity reduction, punitive isolation, evidence destruction, and containment without restoration.

O⁺:
Bounded harm.

O⁻:
Permanent confinement.

Deficit:
Uncontrolled propagation.

Excess:
Overcontainment.

Captured form:
Concealment.

False form:
Perimeter theater.

Canon line:
Contain limits unresolved harm from spreading while preserving the conditions required for truth, care, restoration, and eventual release.

20. Canon Lockbox

• Contain is an intention, not an operator.
• Containment limits propagation; it does not automatically resolve cause.
• The affected system is not always the source.
• Temporary restriction must not become permanent identity.
• Containment must preserve observability.
• Containment must preserve evidence.
• Containment must preserve care.
• Containment must include restoration.
• Containment must include review.
• Containment must include an exit condition.
• Visible restriction does not prove reduced spread.
• Secrecy is not equivalent to containment.
• Containment that hides institutional harm is captured.
• Containment without support becomes abandonment.
• Containment without proportionality becomes overreach.
• Containment without reintegration becomes exclusion.
• Containment without root-cause repair becomes recurrence.
• Containment without auditability becomes opaque authority.
• Restrictions must decrease as propagation risk decreases.
• Temporal recurrence determines whether containment prevented spread or merely displaced it.

21. Canon Line

Contain limits unresolved harm from propagating while preserving identity, evidence, care, auditability, restoration, and a viable path toward release or reintegration.