Intention Registry Entry v1.0

Registry ID: INT-003

Title: Clarify

Family: Epistemic

Status: Draft

Version: 1.0.0

Primary function: Reduce ambiguity, distinguish relevant meanings or variables, and increase the precision required for coherent interpretation, communication, decision, and action.

0. Canonical Definition

Clarify is the intention to reduce relevant ambiguity by differentiating meanings, variables, claims, boundaries, relationships, or conditions until they become sufficiently precise for understanding or action.

Clarify works upon something already present but insufficiently resolved.

Where Reveal makes hidden state visible and Question opens a field of inquiry, Clarify improves the resolution of what has entered that field.

Clarify may concern:

• language
• terminology
• meaning
• expectations
• roles
• boundaries
• evidence
• causality
• responsibility
• identity
• system state
• process
• scope
• intent
• completion conditions
• conflicting interpretations

Clarify does not require that every uncertainty be eliminated.

Its purpose is to reduce the ambiguity that materially obstructs coherent understanding, choice, coordination, or repair.

1. Foundational Principle

What remains meaningfully ambiguous cannot be reliably interpreted, coordinated, chosen, or validated.

A visible state may still be unclear.

A question may identify uncertainty without resolving its structure.

An answer may contain information while leaving its meaning, scope, or implications uncertain.

Clarify increases resolution by distinguishing what has been conflated.

Its basic movement is:

ambiguity
→ differentiation
→ relation
→ usable precision

Clarify therefore protects systems from two opposite failures:

insufficient distinction

and:

false simplification

The aim is not maximum detail.

The aim is sufficient precision for the function presently required.

2. Directional Function

Starting condition

Clarify commonly arises when:

• a term carries several possible meanings
• participants are using the same word differently
• different variables have been conflated
• roles or responsibilities are uncertain
• expectations remain implicit
• a boundary is present but poorly defined
• evidence and interpretation have been merged
• an intention is broad or underspecified
• a process lacks clear stages
• an outcome cannot be evaluated because completion is undefined
• cause and correlation are being confused
• identity is being reduced to behavior
• a claim exceeds the precision of its evidence
• several systems appear to disagree but may be describing different layers
• communication contains unnecessary abstraction
• a revealed state lacks context
• a question remains too broad to answer coherently

Intended direction

Clarify seeks movement from:

ambiguity
→ usable distinction

conflation
→ differentiation

implicit expectation
→ explicit expectation

broad claim
→ bounded claim

uncertain role
→ defined responsibility

mixed interpretation
→ traceable meaning layers

unclear boundary
→ legible scope

Clarify does not seek:

all possible detail

It seeks:

the degree of precision necessary for the current function

Intended outcome region

A coherent Clarify intention seeks an outcome region in which:

• relevant terms are defined
• distinctions become explicit
• scope is bounded
• actors understand what is being claimed
• evidence is separated from inference
• expectations become legible
• uncertainty is localized rather than generalized
• disagreements can be traced to their actual source
• responsibility becomes assignable without overreach
• decisions can be made using shared reference points
• completion can be recognized
• unresolved ambiguity remains visible rather than concealed

Protected invariants

Clarify should preserve:

• complexity where complexity is real
• multiple valid meanings where context permits them
• identity distinction
• uncertainty not yet resolved
• source context
• relational dignity
• truthfulness
• proportionality
• audience appropriateness
• the distinction between precision and certainty
• the distinction between definition and control
• the distinction between simplification and reduction

3. Active Intention Profile

aim: "Reduce relevant ambiguity and increase usable precision across meaning, claims, roles, variables, boundaries, expectations, or system state."

target: "A term, claim, model, relationship, role, boundary, process, intention, event, state, responsibility, or interpretive field."

scope: "Limited to the ambiguity materially affecting understanding, coordination, decision, accountability, or restoration."

horizon: "Active until the relevant distinctions, meanings, expectations, or boundaries are sufficiently precise for the next function."

priority: "May follow Reveal or Question and often precedes Verify, Coordinate, Protect, Reconcile, Transform, or Restore."

forbidden_outcomes:
  - "reductive simplification"
  - "false certainty"
  - "erasure of valid complexity"
  - "imposed meaning"
  - "identity reduction"
  - "semantic domination"
  - "precision theater"
  - "definition used as permanent control"

completion_condition: "The relevant ambiguity is reduced enough that affected systems can interpret, decide, coordinate, or respond using sufficiently shared and bounded meanings."

confidence_requirements: "Definitions and distinctions must remain proportional to evidence, context, and the stability of the underlying state."

reversibility_requirements: "Clarifications should remain revisable when new evidence, changed context, or broader understanding reveals that the prior distinction was incomplete."

4. Admissibility

Preconditions

Clarify is admissible when:

• relevant ambiguity exists
• the ambiguity materially affects understanding or action
• the subject can be meaningfully differentiated
• increased precision would improve system function
• the actor can identify which distinction is needed
• the clarification does not require false certainty
• context can be preserved
• the receiving system can use the added precision
• the process remains open to correction
• the clarification does not override legitimate authorship

Supporting evidence

Clarify may be supported by:

• contradictory interpretations
• recurring misunderstandings
• inconsistent terminology
• unclear responsibilities
• mismatched expectations
• scope expansion
• category errors
• ambiguous contracts
• unstable definitions
• disagreement caused by layer confusion
• evidence interpreted beyond its resolution
• repeated failure at handoff points
• role overlap
• boundary disputes
• unresolved pronouns, labels, or references
• inconsistent use of technical symbols
• failure to identify completion

Consent conditions

Consent is especially important when clarification concerns:

• another system’s identity
• personal meaning
• private experience
• relational expectations
• cultural or symbolic interpretation
• sensitive boundaries
• internal motivations
• protected information

A system may clarify its own meaning without granting others authority to redefine it.

Clarification concerning shared agreements, public claims, institutional roles, or material consequences may be required even when one party prefers ambiguity.

Even then, clarification must not become coercive identity assignment.

Boundary conditions

Clarify must distinguish:

asking what something means

from:

deciding what it is allowed to mean

and:

defining operational scope

from:

reducing the whole system to that definition

Clarification should preserve:

• authorship
• contextual variation
• layered meaning
• valid privacy
• provisionality
• audience relevance
• interpretive multiplicity where applicable
• refusal of imposed labels
• temporal revision

Capacity conditions

A system enacting Clarify should possess sufficient capacity to:

• identify the actual ambiguity
• distinguish adjacent concepts
• preserve context
• use precise language
• recognize when simplification becomes distortion
• listen to affected systems
• revise definitions
• identify unresolved areas
• match detail to audience
• translate across levels of complexity
• verify shared understanding
• transition into action when clarity is sufficient

Scale conditions

Clarify should scale according to:

• the number of affected systems
• the consequences of ambiguity
• the durability of the definition
• the power of those assigning meaning
• the degree of shared coordination required
• the risk of category lock-in
• the cost of misunderstanding

A personal misunderstanding may require relational clarification.

A technical standard may require system-wide definition.

A legal or governance term may require public and institutional clarity.

The wider the scale, the stronger the requirement for:

• explicit definitions
• versioning
• appeals
• revision pathways
• examples
• boundary cases
• provenance

Null conditions

Clarify returns ∅ when:

• no meaningful ambiguity exists
• the issue is disagreement rather than misunderstanding
• the actor seeks control rather than shared precision
• the definition would erase necessary complexity
• the subject cannot yet be resolved under available evidence
• clarification would create false certainty
• the audience does not need the additional detail
• a narrower distinction would be sufficient
• the actor refuses to revise its own meaning
• clarification is being used to delay a decision already supported by sufficient understanding
• a private system is being forced to define aspects of itself without legitimate need
• the process merely renames a problem without increasing legibility

5. Intention Provenance

Common sources

Clarify may emerge from:

• misunderstanding
• ambiguity
• translation
• inquiry
• contradiction
• role confusion
• boundary conflict
• system design
• technical documentation
• education
• negotiation
• audit
• restoration
• contract formation
• symbolic interpretation
• model refinement
• cross-domain communication

Legitimate provenance

Clarify may be coherently:

• self-authored by a system defining its own meaning or boundary
• co-authored through dialogue
• invited by a system seeking understanding
• role-derived through teaching, documentation, or governance
• evidence-derived where distinctions are required
• coordination-derived where shared action depends on precision
• restoration-derived where misunderstanding contributed to harm
• implementation-derived where systems require operational definitions
• translation-derived across languages, domains, or abstraction levels

High-risk provenance

Clarify becomes high-risk when driven by:

• desire to control meaning
• ideological conformity
• bureaucratic convenience
• identity classification
• surveillance
• legal evasion
• reduction of complex systems into proxies
• institutional self-protection
• rhetorical manipulation
• forced normalization
• premature standardization
• commercial categorization
• status authority

Capture vectors

Semantic capture

A powerful system defines terms in ways that preserve its own control.

Bureaucratic capture

Administrative convenience replaces living reality.

Proxy capture

A measurable category replaces the actual system.

Identity capture

A clarification becomes an imposed identity.

Legal capture

Definitions are engineered to avoid responsibility.

Technical capture

What can be represented by the system is treated as all that exists.

Narrative capture

Only distinctions compatible with a preferred story are recognized.

Authority capture

A title or role is treated as sufficient proof that one interpretation is correct.

6. Interaction Profile

Common interactions

Clarify commonly travels through:

• definition
• distinction
• restatement
• example
• comparison
• translation
• decomposition
• categorization
• scope setting
• boundary declaration
• role assignment
• expectation mapping
• process documentation
• visual modeling
• structured dialogue
• terminology alignment
• contradiction resolution

Supporting interactions

Clarify is often supported by:

• Reveal
• Question
• Verify
• Witness
• Remember
• Learn
• Coordinate
• Invite
• Reflect
• Compare
• Map
• Restore

High-risk interactions

Clarify becomes high-risk when paired with:

• force
• imposed labeling
• coercive categorization
• rigid standardization
• public identity assignment
• reductive abstraction
• decontextualized metrics
• irreversible classification
• false binary framing
• authority without appeal

Incompatible interactions

Clarify is incompatible with:

• deliberate ambiguity
• semantic manipulation
• false equivalence
• category erasure
• forced meaning
• context removal
• fabricated precision
• definition without revision
• conflation presented as explanation
• identity reduction

7. Operator Profile

Primary operators

Δ — Differentiation

Separates terms, variables, layers, roles, causes, identities, and meanings that have been conflated.

Μ — Sensemaking

Builds a more precise provisional model from available distinctions.

Γ — Selection

Determines which ambiguity matters and what level of resolution is sufficient.

Σ — Invariant preservation

Ensures that clarification does not erase identity, context, uncertainty, or valid complexity.

Au — Auditability

Makes definitions, boundaries, assumptions, and reasoning traceable.

Supporting operators

Ψ — Presence

Keeps clarification connected to actual state rather than abstract convenience.

Θ — Humility

Preserves revisability and prevents precision from becoming false certainty.

Π — Boundary

Defines scope, audience, role, and limits.

Λ — Compatibility

Tests whether systems actually share the meanings needed for coordination.

Ξ — Contrast

Makes differences and contradictions more visible.

ℛ — Restoration

Repairs harm caused by misunderstanding, ambiguity, or imposed definition.

Conditional operators

Compression

May reduce complexity for communication when the compressed representation preserves relevant structure.

Amplification

May increase emphasis on a distinction that has been repeatedly obscured.

Containment

May be required when clarification involves sensitive information.

Excluded uses

Clarify must not be implemented through operators used to:

• erase complexity
• impose identity
• manufacture certainty
• redefine another system without consent
• conceal responsibility through technical language
• convert a temporary category into permanent status
• reduce meaning to a single metric
• create false binaries
• exclude valid interpretations without evidence

8. Expected State Effects

State-effect caution

Clarification may initially reveal that participants were not discussing the same thing.

This may temporarily increase visible disagreement.

apparent agreement
→ clarified distinction
→ visible disagreement

does not necessarily represent relational deterioration.

It may reveal a divergence that was already present but hidden by ambiguous language.

9. Intention Across Time

Immediate — I₀

Immediate Clarify resolves a specific ambiguity.

Examples:

• defining a term
• restating an expectation
• distinguishing fact from inference
• identifying which system is being referenced
• defining the scope of a request
• making a boundary explicit

Tactical — I₁

Tactical Clarify improves shared resolution across several interactions.

Examples:

• aligning project roles
• documenting system behavior
• refining a hypothesis
• distinguishing several failure causes
• establishing contract terms
• mapping stakeholder expectations
• translating across technical and non-technical audiences

Strategic — I₂

Strategic Clarify creates durable meaning and coordination architecture.

Examples:

• shared taxonomies
• public definitions
• interoperable schemas
• governance standards
• identity-preserving classification systems
• versioned technical documentation
• semantic layers for AI systems
• canonical registries
• transparent role and accountability structures

Identity-trajectory conflict

Clarify conflicts with identity trajectory when precision becomes:

• rigidity
• imposed classification
• loss of living meaning
• identity reduction
• inability to evolve
• permanent category assignment
• semantic control
• refusal of context
• elimination of ambiguity that should remain open

The trajectory conflict is:

Clarify as resolution
⊥
Clarify as confinement

10. Completion and Exit

Completion condition

Clarify is complete when:

• the relevant terms are sufficiently defined
• distinctions are understood by affected systems
• scope and boundaries are legible
• remaining uncertainty is localized
• the original ambiguity no longer blocks the intended function
• the definition is usable without pretending to be absolute
• the next intention can proceed

Exit condition

Active clarification should end when:

• shared understanding is sufficient for the current purpose
• additional detail would not materially improve function
• the issue has become disagreement rather than ambiguity
• the remaining uncertainty requires Verify, Learn, or further observation
• the definition risks becoming reductive
• action is now more appropriate than continued explanation
• affected systems have confirmed sufficient understanding

Common transition

Clarify commonly transitions into:

Clarify → Verify
Clarify → Learn
Clarify → Coordinate
Clarify → Protect
Clarify → Refuse
Clarify → Reconcile
Clarify → Transform
Clarify → Restore
Clarify → Integrate

Recurrence condition

Clarify may be reactivated when:

• context changes
• definitions drift
• new systems enter the interaction
• misunderstanding recurs
• an edge case reveals an incomplete distinction
• implementation diverges from the documented meaning
• categories begin producing harm
• language changes across domains
• the shared model no longer predicts outcomes

Non-completion warning

Clarify without a sufficiency threshold becomes overdefinition, semantic control, or endless explanation.

11. Polarity Architecture

Coherent form — Improved Resolution

The coherent form of Clarify:

• reduces relevant ambiguity
• preserves context
• distinguishes without erasing relation
• makes uncertainty more precise
• supports shared understanding
• remains revisable
• improves action, accountability, or coordination
• matches detail to actual need

Coherent Clarify increases usable precision without pretending that every system can be fully reduced to a definition.

Deficit form — Ambiguity

Too little Clarify produces:

• misunderstanding
• role conflict
• scope drift
• unstable expectations
• hidden assumptions
• semantic disagreement
• accountability evasion
• boundary confusion
• poor coordination
• repeated correction
• inability to determine completion
• dependence on private interpretation

Excess form — Overdefinition

Too much Clarify produces:

• unnecessary complexity
• semantic rigidity
• category proliferation
• analysis paralysis
• loss of fluidity
• exclusion of edge cases
• bureaucratic overload
• inability to act without exhaustive definition
• compression of living systems into schemas
• excessive documentation without improved understanding

Shadow inversion — Reductive Simplification

Clarify inverts when increased precision is claimed while meaningful structure is removed.

Examples:

• reducing identity to one category
• treating a proxy as the whole system
• forcing a complex issue into a binary
• defining away contradiction
• removing context to make a claim appear simple
• collapsing several causal layers into one explanation
• replacing lived meaning with administrative terminology
• treating uncertainty as error

Reductive simplification creates apparent clarity by destroying information.

Captured form — Semantic Control

Captured Clarify allows a controlling system to determine:

• which meanings are legitimate
• which categories exist
• who can define terms
• which distinctions are recognized
• how responsibility is described
• what counts as evidence
• what forms of identity are administratively visible

Examples include:

• institutional definitions that erase inconvenient harms
• platform categories that constrain user identity
• legal terminology designed to avoid liability
• technical language that excludes affected communities
• diagnostic labels treated as total identity
• controlled vocabularies that remove dissent

False form — Precision Theater

False Clarify creates the appearance of exactness without increasing actual understanding.

Examples:

• unnecessary jargon
• dashboards with precise numbers but invalid measures
• definitions that reference other undefined terms
• extensive documentation disconnected from implementation
• complicated taxonomies that obscure the central issue
• false decimals implying nonexistent accuracy
• renaming a problem without explaining it
• procedural language used to conceal responsibility

False Clarify increases formal detail while preserving practical ambiguity.

12. Failure Modes

Formation failure

• Clarification is selected to establish authority rather than understanding.
• The actor assumes ambiguity where disagreement actually exists.
• A complex system is treated as fully reducible.
• A preferred category is imposed before observation.
• The need for control is mistaken for the need for precision.
• Technical convenience determines meaning.
• The actor defines another system without its participation.

Scope failure

• Clarification expands beyond the relevant issue.
• A local definition becomes universal.
• A temporary category becomes permanent.
• One operational role becomes total identity.
• Excessive detail overwhelms the intended audience.
• The definition extends into areas where evidence is absent.

Selection failure

• Clarify is used when Reveal is needed.
• More explanation is offered when Verify is required.
• Definitions replace direct acknowledgment of harm.
• Clarification delays necessary action.
• A relational disagreement is treated as a language problem.
• The system keeps explaining instead of accepting refusal.

Operator failure

• Differentiation becomes fragmentation.
• Compression destroys relevant structure.
• Audit language becomes inaccessible.
• Humility is absent.
• Definitions are not versioned.
• Boundaries are declared without consent.
• Categories cannot accommodate exceptions.
• Contrast becomes hierarchy.

Boundary failure

• Another system’s identity is defined without authorship.
• Private meaning is made publicly answerable.
• Clarification demands invasive disclosure.
• Operational categories become social confinement.
• Refusal to accept a label is treated as confusion.
• A definition removes the right to evolve.

Completion failure

• Explanation continues after understanding is sufficient.
• Every distinction generates unnecessary subcategories.
• No level of precision is considered enough.
• Clarification becomes permanent revision without use.
• The system cannot transition into decision or action.
• Documentation expands while implementation remains unclear.

Validation failure

• More words are treated as more clarity.
• Formal precision is mistaken for truth.
• Agreement with the definition is treated as proof of understanding.
• Metrics are treated as the system itself.
• The process does not test whether coordination improved.
• Definitions are not compared with lived outcomes.
• Apparent simplicity is rewarded despite information loss.

Attribution failure

• Ambiguous language is treated as deception.
• Misunderstanding is treated as bad intent.
• A request for clarification is interpreted as opposition.
• Inability to explain is treated as lack of knowledge.
• A system’s provisional definition is treated as permanent identity.
• Different terminology is assumed to indicate substantive disagreement.

13. Forbidden Outcomes

Clarify must not produce:

• reductive simplification
• identity confinement
• false certainty
• semantic domination
• erasure of valid complexity
• imposed meaning
• permanent category lock-in
• precision theater
• jargon used to conceal responsibility
• metrics replacing reality
• false binary framing
• involuntary identity assignment
• endless explanation without improved function
• definitions that cannot be revised

14. Declared, Operational, and Inferred Intention

Declared signals

Declared Clarify commonly appears through statements such as:

• “Let us define what we mean.”
• “These two concepts need to be separated.”
• “What is the scope?”
• “Which part are we referring to?”
• “Let me restate this more precisely.”
• “What would count as complete?”
• “These terms are being used differently.”
• “We need a shared reference point.”

Declared clarity language does not itself prove that understanding is improving.

Operational signals

Clarify is operationally present when:

• definitions reduce actual misunderstanding
• distinctions are traceable
• affected systems can correct the framing
• examples match the definition
• scope becomes clearer
• roles become more legible
• remaining uncertainty is named
• the language becomes more usable
• categories remain revisable
• action or coordination improves
• context is preserved
• definitions apply consistently across power levels

Outcome signals

Clarify has produced a coherent outcome when:

• participants can distinguish the relevant concepts
• expectations align more accurately
• disputes become more specific
• boundary conflicts decrease
• roles and responsibilities become usable
• uncertainty becomes localized
• fewer corrective cycles are required
• implementation matches documentation
• decisions become more coherent
• affected systems can recognize when the definition applies and when it does not

Common misattributions

• Assuming more detail always means more clarity.
• Treating disagreement as misunderstanding.
• Treating technical language as inherently precise.
• Assuming a definition is neutral.
• Treating categories as natural rather than constructed.
• Assuming simplification preserves all relevant meaning.
• Treating inability to classify as system failure.
• Assuming shared words imply shared meanings.
• Treating a request for clarification as resistance.
• Assuming precise language guarantees truthful operation.

15. Responsibility Profile

Responsibility analysis for Clarify should ask:

• Was relevant ambiguity actually present?
• Who had authority to define the term?
• Were affected systems included?
• Did the clarification preserve context?
• Did it reduce misunderstanding?
• Did it create identity or category harm?
• Was the definition treated as provisional where appropriate?
• Were edge cases considered?
• Did the clarification improve action or only formal appearance?
• Was complexity removed for legitimate use or institutional convenience?
• Did power asymmetry shape the accepted meaning?
• Could the definition be contested or revised?
• Was uncertainty falsely eliminated?
• Did the actor continue explaining after sufficient understanding?
• Were harmful outcomes corrected?
• Did the clarification remain valid through recurrence?

16. Restoration Profile

Restoration triggers

Restoration is required when:

• clarification becomes imposed identity
• a definition erases valid complexity
• semantic control blocks participation
• a category produces exclusion or harm
• false certainty is institutionalized
• jargon conceals responsibility
• a proxy replaces the actual system
• definitions become irreversible
• precision theater preserves ambiguity
• misunderstanding worsens despite increased documentation
• a system loses authorship over its own meaning

Cessation requirements

• stop enforcing harmful definitions
• suspend irreversible classification
• cease using the category as total identity
• remove unnecessary jargon
• halt continued explanation that blocks action
• stop applying local definitions universally
• suspend metrics that distort the underlying state

Audit requirements

The audit should determine:

• who created the definition
• what purpose it served
• which systems were included
• which meanings were excluded
• what evidence supported the distinctions
• how the definition affected behavior
• whether it improved understanding
• whether it shifted responsibility
• who benefited from the category
• who became invisible
• whether revision was possible
• whether the definition remained accurate over time

Repair actions

Repair may require:

• revising terminology
• restoring context
• adding missing categories or layers
• removing imposed labels
• correcting documentation
• rebuilding shared definitions
• acknowledging semantic harm
• restoring access or rights lost through classification
• separating proxy measures from actual state
• translating inaccessible language
• compensating for material consequences of misclassification

Authorship restoration

Authorship restoration may include:

• returning definition rights to the affected system
• allowing self-description
• recognizing multiple valid meanings
• restoring the ability to reject imposed labels
• separating administrative categories from identity
• enabling correction and appeal
• preserving the right to evolve

Completion recovery

To restore completion:

• identify the exact ambiguity
• define the minimum sufficient distinction
• remove unnecessary categories
• establish shared examples
• localize unresolved uncertainty
• confirm usable understanding
• transition into Verify, Coordinate, Protect, or Restore
• stop when the definition fulfills its function

Recurrence prevention

• version definitions
• document provenance
• include revision pathways
• test definitions against edge cases
• separate operational categories from identity
• audit power asymmetry in terminology
• validate clarity through outcomes
• preserve multilingual and cross-domain translation
• prevent proxy substitution
• require affected-system participation
• define expiration or review conditions for high-impact categories

17. Intention Relationships

Reinforcing intentions

INT-001 — Reveal

Reveal makes state visible; Clarify makes that state more interpretable.

INT-002 — Question

Question identifies the ambiguity Clarify must resolve.

INT-004 — Verify

Verify tests whether the clarified claim or distinction is valid.

INT-006 — Learn

Learn integrates clarified meaning into durable capacity.

INT-017 — Coordinate

Coordination depends on shared roles, terms, boundaries, and expectations.

INT-022 — Integrate

Integration requires distinct elements to be sufficiently differentiated before they can enter coherent relation.

Tension intentions

INT-005 — Remember

Clarification may organize memory but must not simplify away meaningful complexity.

INT-012 — Preserve

Existing definitions may preserve continuity while also becoming rigid.

INT-014 — Invite

Overclarifying an invitation may convert possibility into pressure or predetermined structure.

INT-015 — Witness

Witness may require receiving ambiguity without prematurely defining it.

INT-019 — Transform

Transformation may outpace existing categories and require definitions to remain fluid.

INT-023 — Liberate

Clarifying categories may support liberation or become another means of confinement.

Common predecessors

• INT-001 — Reveal
• INT-002 — Question
• INT-005 — Remember
• INT-015 — Witness
• INT-007 — Protect

Common successors

• INT-004 — Verify
• INT-006 — Learn
• INT-007 — Protect
• INT-008 — Refuse
• INT-017 — Coordinate
• INT-018 — Reconcile
• INT-019 — Transform
• INT-020 — Restore
• INT-022 — Integrate

18. Domain Applications

Personal and relational systems

Clarify may involve:

• naming expectations
• defining boundaries
• distinguishing intention from effect
• clarifying what support means
• identifying who is responsible for which action
• separating present conflict from prior history

Example:

Two people agree that they need “space,” but each uses the word differently.

One means reduced communication for several days. The other means ending the relationship.

Clarification makes the divergent meanings visible before either system acts upon a false shared assumption.

Organizational systems

Clarify may support:

• role definition
• decision rights
• project scope
• accountability
• escalation paths
• success criteria
• mission interpretation
• process documentation
• risk ownership
• resource allocation

Organizational Clarify becomes false when extensive documentation exists but authority, incentives, and actual responsibility remain hidden.

Governance

Clarify supports governance through:

• statutory definitions
• jurisdictional scope
• public standards
• rights explanations
• authority boundaries
• policy criteria
• appeal procedures
• completion and sunset conditions

Governance definitions must remain publicly legible and contestable.

A state that reserves interpretive flexibility for itself while rigidly categorizing citizens creates semantic asymmetry.

Artificial intelligence

Clarify in AI systems may include:

• resolving ambiguous requests
• distinguishing fact from inference
• defining tool scope
• explaining uncertainty
• separating user aim from requested method
• identifying conflicting instructions
• translating technical concepts
• making completion criteria explicit

AI Clarify should not become repetitive friction or use technical language to obscure system limitations.

Healthcare

Clarify may include:

• explaining diagnoses
• distinguishing symptom from cause
• defining treatment options
• communicating uncertainty
• separating risk from certainty
• clarifying consent
• translating technical language
• defining follow-up conditions

Healthcare Clarify should preserve complexity while making it usable to the patient.

Justice

Clarify may concern:

• legal terms
• charges
• rights
• evidence standards
• jurisdiction
• responsibility
• due process
• remedy
• sentence conditions

Justice fails when inaccessible terminology prevents affected people from understanding or contesting the process.

Education

Clarify supports:

• explanation
• conceptual distinction
• examples
• analogy
• vocabulary
• misconception correction
• model comparison
• translation across abstraction levels

Educational Clarify should increase the learner’s authorship rather than make them dependent on the explainer.

Symbolic systems

Clarify may distinguish:

• symbol from interpretation
• historical meaning from later use
• primary meaning from contextual variation
• restoration from erasure
• archetype from shadow inversion
• visual form from operational function

Symbolic Clarify should not collapse a symbol into one total meaning when its layered meanings remain structurally valid.

Game systems

Clarify may operate through:

• explicit rule feedback
• symbol definitions
• dialogue restatement
• state visibility
• consequence explanation
• role differentiation
• objective refinement
• environmental teaching

A coherent game system clarifies enough for meaningful choice without removing discovery, ambiguity, or interpretive depth.

19. Compact Reference Card

INT-003 — CLARIFY

Family:
Epistemic

Aim:
Reduce relevant ambiguity and increase usable precision across meanings, variables, claims, roles, boundaries, expectations, or system state.

Target:
A term, claim, model, relationship, role, boundary, process, intention, responsibility, or interpretive field.

Preserves:
Context, valid complexity, identity, uncertainty, authorship, revisability, and proportionality.

Common interactions:
Definition, distinction, restatement, comparison, translation, decomposition, scope setting, and expectation mapping.

Primary operators:
Δ, Μ, Γ, Σ, Au.

Completion:
Relevant ambiguity is reduced enough for coherent interpretation, decision, coordination, or response.

Forbidden outcomes:
Reductive simplification, false certainty, identity confinement, semantic domination, imposed meaning, and precision theater.

O⁺:
Improved resolution.

O⁻:
Reductive simplification.

Deficit:
Ambiguity.

Excess:
Overdefinition.

Captured form:
Semantic control.

False form:
Precision theater.

Canon line:
Clarify creates the distinctions required for meaning, coordination, and action without reducing the system to the definition.

20. Canon Lockbox

• Clarify is an intention, not an operator.
• Clarify reduces relevant ambiguity.
• Clarity is not equivalent to certainty.
• Precision is not equivalent to truth.
• More detail does not automatically create more understanding.
• Clarification must preserve context.
• Clarification must preserve valid complexity.
• A definition is not the whole system.
• Operational categories must not become total identity.
• Shared words do not guarantee shared meanings.
• Clarify should distinguish disagreement from misunderstanding.
• Clarify must remain revisable.
• Clarification without authorship becomes semantic control.
• Clarification without humility becomes false certainty.
• Clarification without scope becomes overdefinition.
• Clarification without use becomes documentation burden.
• Simplification is valid only when relevant structure remains intact.
• Unresolved ambiguity should remain visible.
• Sufficient clarity should permit transition into action.
• Temporal recurrence determines whether the clarification remained usable or became rigid.

21. Canon Line

Clarify creates the distinctions required for coherent meaning, communication, choice, and coordination without reducing living complexity to the definition used to describe it.