0. Archetype Scope Note

This entry is conceptual and systems-oriented.

It does not diagnose individuals or reduce identity, symbolic role, mythic resonance, vocation, art, spiritual expression, cultural pattern, or archetypal development to pathology. It names a UTS pattern in which an archetype label remains stable while the underlying expression leaves the archetype’s admissible coherence region.

The issue is not archetypal evolution.

Archetypes can mature, deepen, combine, differentiate, and express across many domains.

The issue is drift that preserves the name while changing the geometry.

1. Definition

Archetype drift occurs when a system continues claiming, naming, performing, or organizing around an archetype while its actual expression exits the archetype’s admissible coherence region.

The label remains.

The geometry has changed.

The system may still call itself healer, protector, teacher, warrior, sovereign, trickster, builder, mystic, witness, mother, father, child, guide, servant, artist, lover, guardian, rebel, or architect.

But the active pattern no longer satisfies the archetype’s coherence constraints.

The core failure is:

archetype label stability↑
expression drift↑
admissible-region fit↓
auditability↓
H↑

Canonical signature:

Au↓ + H↑ + ι↑ + 𝓓↓

The label remains.

The geometry has changed.

Archetype drift is a standalone archetype failure because it affects the integrity of archetypal systems directly. It often produces secondary failures: performative archetype, sacred immunity, identity capture, shadow distortion, over-identification, and false restoration.

In UTS terms, archetype drift is the divergence between named role and actual operating geometry.

2. Core Pattern

The core pattern is:

1. A system identifies with, inherits, invokes, performs, or is assigned an archetype.
2. The archetype has an admissible expression region: valid functions, constraints, boundaries, duties, shadows, risks, timings, permissions, and restoration requirements.
3. The system’s actual behavior begins shifting.
4. The archetype label remains unchanged.
5. The drift is not audited because the name still carries legitimacy.
6. Expressions that once would have been recognized as outside the archetype are normalized.
7. The system retains symbolic authority while losing archetypal integrity.
8. Critique is interpreted as failure to recognize the archetype rather than detection of drift.
9. Hidden debt accumulates because the field continues trusting the label.
10. Restoration requires reclassifying the expression, restoring geometry, or retiring the claim.

This failure mode often appears as:

I am still this archetype because I still use its name

or:

this action is valid because it comes from the archetype

The restorative question is:

does the expression still live inside the archetype’s admissible region?

The archetype name is not enough.

The geometry must still fit.

3. Failure Signature

Typical signature:

archetype name stable
expression pattern shifting
constraint fidelity↓
shadow leakage↑
role-function mismatch↑
auditability↓
H↑

Extended signature:

protector begins controlling
healer begins extracting
teacher begins dominating
sovereign becomes tyrant
rebel becomes destabilizer
servant becomes self-erasure
trickster becomes destroyer
warrior becomes aggressor
guardian becomes gatekeeper
guide becomes dependency anchor
innocent becomes immunity shield
architect becomes over-controller

Common forms include:

calling control protection
calling extraction healing
calling dominance teaching
calling avoidance peace
calling indulgence freedom
calling destabilization truth
calling performance embodiment
calling punishment justice
calling dependency care
calling obedience harmony
calling coercion love
calling containment safety

The key diagnostic is whether the archetype’s name still matches its active function.

4. Primary U-Layer Origin

Common origin layers:

• U1 — Power / Budgets: Archetype label grants authority, trust, identity stability, reputation, access, moral protection, belonging, or operational permission.
• U2 — Configuration / Boundaries: The boundary around the archetype’s admissible expression region weakens.
• U3 — Execution / Runtime: Drift appears in action, teaching, governance, care, judgment, protection, rebellion, creation, or intervention.
• U4 — Information / Truth: The archetype label substitutes for actual expression audit.
• U5 — Coordination / Time: Gradual drift accumulates across cycles and is normalized.
• U6 — Coherence Field: The field remains symbolically coherent while actual effects degrade.
• U7 — Memory / Recurrence: Drift becomes identity, tradition, role expectation, mythology, or institutional pattern.

Common manifestation layers:

• U2 — Configuration / Boundaries: Valid-expression boundaries weaken.
• U3 — Execution: Actions no longer match the archetype’s geometry.
• U4 — Truth: Label replaces audit.
• U6 — Coherence Field: Symbolic coherence masks drift.
• U7 — Memory: Drift becomes inherited pattern.

Archetype drift is primarily a U4 / U2 / U7 label-geometry failure.

The name persists across time while the admissible region quietly moves or is abandoned.

5. Typical Development Sequence

A common development sequence is:

1. A system enters or invokes an archetype.
2. The archetype initially fits.
3. The archetype produces legitimacy, orientation, identity, or coherence.
4. Pressures increase: scale, speed, status, threat, conflict, fatigue, extraction, audience demand, institutionalization, or unresolved shadow.
5. The expression begins shifting toward convenience, control, protection, status, performance, rigidity, avoidance, or extraction.
6. The label remains unchanged.
7. The system receives continued trust because the archetype name is still recognized.
8. Early drift signals are minimized or interpreted as deeper archetypal expression.
9. Drift becomes normalized.
10. The archetype’s shadow begins steering the role.
11. Hidden debt accumulates under label continuity.
12. Restoration requires detecting the divergence and recalibrating the expression.

The loop often looks like:

valid archetype → legitimacy → pressure → expression drift → label retained → audit weakens → debt

Another common loop is:

drift challenged → archetype defended → label authority rises → drift becomes harder to see

The archetype becomes self-protective because the name is treated as evidence.

6. Diagnostic Markers

Diagnostic markers include:

• The system relies more on the archetype name than on function evidence.
• The role’s effects no longer match its stated archetype.
• The archetype’s shadow expression becomes normalized.
• Critique is treated as failure to understand the archetype.
• The system cannot state the archetype’s valid boundaries.
• The system cannot name when the archetype becomes invalid.
• The archetype grants immunity from ordinary accountability.
• The role becomes more rigid as effects become less coherent.
• Symbolic performance increases as function accuracy decreases.
• The archetype is used to justify actions that invert its purpose.
• Hidden cost rises around the archetype.
• Affected nodes experience the role differently than the label claims.
• Restoration improves when the archetype is reclassified or decompressed.
• Time validation shows divergence between original function and current expression.

Useful diagnostics:

• Archetypal Integrity: Measures whether expression preserves archetype function, constraint, and purpose.
• Admissible Region Fit: Tests whether behavior remains inside valid expression bounds.
• Label / Geometry Divergence: Measures distance between claimed archetype and active pattern.
• Role Function Integrity: Tests whether the role still performs its core function.
• Expression Boundary Integrity: Determines whether invalid expressions are being admitted.
• Auditability: Measures whether the archetype claim can be inspected.
• Hidden Debt: Tracks cost accumulated under label continuity.
• Drift Velocity: Measures how quickly the archetype is moving out of bounds.
• Reclassification Need: Indicates whether the expression requires a new label.
• Time Validation: Confirms whether the archetype remains coherent across cycles.

7. Related Gates

Relevant gates include:

• Archetype Gate: Fails when the label is accepted without geometry audit.
• Geometry Gate: Fails when expression exits the admissible region.
• Truth Gate: Fails when name substitutes for function.
• Identity Gate: Fails when archetype becomes self-protective identity.
• Boundary Gate: Fails when valid-expression boundaries weaken.
• Auditability Gate: Fails when archetypal claim cannot be questioned.
• Reclassification Gate: Fails when drifted expression is not renamed.
• Restoration Gate: Fails when repair targets the claimed archetype instead of the active pattern.

The first common gate failure is usually the Archetype Gate.

The system recognizes the name and stops checking the geometry.

8. Related Operators

Relevant operators include:

• Ψ — Observation / Interface: Observes the archetype label and may miss expression divergence.
• µᵢ — Memory / Identity: Stores the archetype as identity, tradition, role, memory, reputation, or self-map.
• BΣ — Boundary Integrity: Preserves the archetype’s valid expression boundaries.
• Au — Auditability: Determines whether the archetype can be inspected and reclassified.
• O — Coherence: Declines when role geometry diverges from label.
• H — Hidden Debt: Accumulates as trust, access, authority, or repair is routed through an invalid label.
• Γ — Selection: Selects the archetype name as the interpretive frame.
• Λ — Compatibility: Tests whether the expression remains compatible with the claimed archetype.
• K — Constraint / Load: Rises on nodes forced to interact with the label rather than the actual pattern.
• R — Restoration Capacity: Misroutes repair when the wrong archetype is named.
• Τ — Trajectory / Time: Reveals gradual drift and delayed mismatch.
• Φ — Flow / Resource Movement: Moves trust, attention, authority, legitimacy, and access toward the archetype label.
• ℛ — Restoration: Requires reclassification, geometry repair, or role retirement.

Common operator pattern:

µᵢ stores archetype identity
Γ selects label as truth frame
Ψ observes role through name
BΣ admissible boundary weakens
Au declines under archetype legitimacy
Λ between label and expression falls
H accumulates
R targets wrong pattern
O degrades

The core operator inversion is:

archetype name → assumed geometry → continued legitimacy

instead of:

archetype name → expression audit → admissible-region check → continued or revised classification

9. Related Laws and Invariants

Related Laws

• Archetypal Drift Law: Archetype drift occurs when expression exits the admissible region while still claiming the archetype.
• U4 Truth Substitution: The label substitutes for active truth.
• Pseudo-Coherence: Symbolic continuity creates apparent coherence.
• Identity Drift: The identity label remains while the underlying pattern changes.
• Boundary Collapse: The archetype’s valid expression boundary weakens.
• Success Proxy Substitution: Performing the archetype substitutes for fulfilling the archetype.
• Hidden Debt Accumulation: Trust and access continue under invalid classification.
• Auditability Collapse: The archetype becomes difficult to inspect.

Related Invariants

• Archetype Must Preserve Its Geometry: A role must remain inside its valid expression region.
• Label Must Not Outrun Expression: Name continuity does not prove function continuity.
• Role Requires Admissible Region Integrity: Every archetype has bounds.
• Symbolic Name Is Not Proof of Function: A symbol cannot self-validate.
• Archetypal Expression Must Remain Auditable: Archetype claims must be inspectable.
• Drift Requires Reclassification: Expression outside bounds must be renamed or repaired.
• Restoration Requires Geometry Re-Alignment: Repair must address actual pattern, not only claimed role.

10. Common False Positives

Not every archetype change is archetype drift.

Common false positives include:

• Natural maturation of an archetype while preserving geometry.
• Context-specific expression within valid bounds.
• Symbolic variation that remains functionally coherent.
• Multi-archetype composition with clear interfaces.
• Shadow integration that increases integrity.
• Temporary role shift explicitly named and bounded.
• Archetype evolution that remains auditable.
• Reclassification done openly.
• Expansion of archetype expression after admissible-region review.
• Cross-cultural variation that preserves core constraints.

Clarifying rule:

This is not archetype drift unless the system continues claiming or organizing around an archetype while its actual expression leaves the archetype’s admissible coherence region.

11. Common False Repairs

Common false repairs include:

• insisting on the archetype name more strongly
• adding symbolic language to stabilize the label
• calling drift “evolution” without audit
• treating critique as archetype rejection
• rebranding shadow leakage as depth
• adding ritual, imagery, or doctrine instead of correcting function
• claiming lineage or authority to protect the role
• renaming the harmed nodes as unable to understand the archetype
• making the archetype more sacred
• adding disclaimers while preserving the same expression
• correcting aesthetics while preserving function drift
• replacing one archetype label with another without geometry audit
• expanding the admissible region until all behavior fits

False repair often produces the loop:

drift exposed → label defended → symbolism intensified → geometry remains unrepaired

Another common loop is:

expression exits bounds → admissible region redefined around expression → drift becomes canonized

The repair fails because it protects the name rather than restoring the geometry.

12. Restoration Direction

Restoration requires auditing the relationship between archetype label and active expression, restoring admissible-region integrity, reclassifying invalid expressions, repairing hidden debt, and validating re-entry across time.

Primary restoration direction:

audit the label,
restore the geometry,
reclassify drift,
and validate re-entry across time

A fuller restoration path includes:

1. Name the claimed archetype. Identify the role, symbolic identity, function, mythic pattern, or archetypal label being used.
2. Define its admissible region. Clarify valid functions, boundaries, constraints, permissions, shadows, duties, and failure edges.
3. Map current expression. Describe what the system is actually doing.
4. Measure label / geometry divergence. Identify where the expression no longer fits.
5. Name drift pressures. Identify scale, status, fear, fatigue, extraction, institutionalization, audience demand, shadow leakage, or convenience pressures.
6. Restore auditability. Allow the archetype claim to be questioned without identity collapse.
7. Reclassify invalid expression. Rename what has drifted; do not preserve the label if the geometry fails.
8. Repair hidden debt. Address harm, misrecognition, false trust, misdirected repair, and access granted under the old label.
9. Restore archetype geometry. Rebuild the role only inside valid constraints.
10. Validate across time. Confirm that the repaired expression remains inside the admissible region under load.

A valid restoration path should reduce:

label / geometry divergence
admissible-region violation
role-function mismatch
symbolic overclaim
shadow leakage
audit resistance
misclassified access
hidden debt
recurrence

Archetype drift is not repaired by preserving the archetype name.

It is repaired by restoring the archetype’s geometry.

13. Cross-Module Links

• Archetypes: Core archetype integrity failure involving admissible region, role geometry, shadow expression, and symbolic claim.
• Symbols: Related to symbol-name continuity masking meaning drift.
• Identity: Related to identity drift, role capture, and self-map persistence after function change.
• Principles: Related to principle names remaining while enactment changes.
• Interfaces: Related to interface trust being routed through a drifted label.
• Restoration: Requires reclassification, hidden-debt repair, and geometry realignment.
• Coherence: Demonstrates that symbolic continuity can stabilize pseudo-coherence.
• Diagnostics: Requires archetypal integrity, admissible region fit, label / geometry divergence, and drift velocity checks.

14. Relationship to Parent / Child Modes

Production treatment: Standalone Entry

This mode maps upward to:

• UTS-L092 — Archetypal Drift Law
• FM-CORE-001 — Pseudo-Coherence
• FM-CORE-002 — Hidden Debt Accumulation
• FM-CORE-004 — Auditability Collapse
• FM-CORE-006 — U4 Truth Substitution
• FM-PX-027 — Identity Drift

Sibling or related Archetype modes include:

• FM-ARCHX-001 — Identity Capture
• FM-ARCHX-002 — Archetypal Bypass
• FM-ARCHX-003 — Performative Archetype
• FM-ARCHX-004 — Archetypal Sacred Immunity
• FM-ARCHX-005 — Shadow Romanticization
• FM-ARCHX-006 — Shadow Repression
• FM-ARCHX-012 — Archetypal Light Performance
• FM-ARCHX-013 — Fusion Collapse
• FM-ARCHX-015 — AI Archetype Inflation
• FM-ARCHX-017 — Optimization Masquerading as Wisdom
• FM-ARCHX-019 — Safety Theater Masquerading as Light

Related principles / interface modes include:

• FM-PX-027 — Identity Drift
• FM-PX-032 — Soul Theater
• FM-PX-016 — Performative Light
• FM-PX-024 — Over-Application
• FM-MT-002 — Narrative Substitution
• FM-MT-016 — Ideological Capture

Aliases preserved from source material:

• Archetype Drift
• Archetypal Drift
• Role Drift
• Symbolic Role Drift
• Archetype Geometry Drift
• Archetype Label Drift
• Admissible Region Exit
• Archetype Integrity Loss
• Archetypal Misalignment
• Role Name / Geometry Divergence

15. Minimal Entry Version

Definition: Archetype drift occurs when a system continues claiming, naming, performing, or organizing around an archetype while its actual expression exits the archetype’s admissible coherence region, causing the label to remain stable while the geometry changes.

Signature:

Au↓ + H↑ + ι↑ + 𝓓↓

Expanded signature:

archetype name stable
expression pattern shifting
constraint fidelity↓
shadow leakage↑
role-function mismatch↑
auditability↓
H↑

Restoration direction:

• name the claimed archetype
• define its admissible region
• map current expression
• measure label / geometry divergence
• name drift pressures
• restore auditability
• reclassify invalid expression
• repair hidden debt
• restore archetype geometry
• validate across time

16. Machine-Readable Summary

failure_mode:
  id: "FM-ARCHX-014"
  name: "Archetype Drift"
  family: "Archetypes"
  production_treatment: "Standalone Entry"
  primary_failure: "A system continues claiming or organizing around an archetype while its actual expression leaves the archetype's admissible coherence region."
  source: "UTS — Failure Modes Registry"
  source_id: "FM-ARCHX-014"
  scope_note: "Conceptual and systems-oriented; does not diagnose individuals or reduce identity, symbolic role, mythic resonance, vocation, art, spiritual expression, cultural pattern, or archetypal development to pathology."
  aliases:
    - "Archetype Drift"
    - "Archetypal Drift"
    - "Role Drift"
    - "Symbolic Role Drift"
    - "Archetype Geometry Drift"
    - "Archetype Label Drift"
    - "Admissible Region Exit"
    - "Archetype Integrity Loss"
    - "Archetypal Misalignment"
    - "Role Name / Geometry Divergence"
  signature:
    canonical:
      - "Au↓"
      - "H↑"
      - "ι↑"
      - "𝓓↓"
    expanded:
      - "archetype name stable"
      - "expression pattern shifting"
      - "constraint fidelity↓"
      - "shadow leakage↑"
      - "role-function mismatch↑"
      - "auditability↓"
      - "H↑"
  primary_layers:
    origin:
      - "U1 — Power / Budgets"
      - "U2 — Configuration / Boundaries"
      - "U3 — Execution / Runtime"
      - "U4 — Information / Truth"
      - "U5 — Coordination / Time"
      - "U6 — Coherence Field"
      - "U7 — Memory / Recurrence"
    manifestation:
      - "U2 — Configuration / Boundaries"
      - "U3 — Execution"
      - "U4 — Truth"
      - "U6 — Coherence Field"
      - "U7 — Memory"
  state_variables:
    - "Ψ"
    - "µᵢ"
    - "BΣ"
    - "Au"
    - "O"
    - "H"
    - "Γ"
    - "Λ"
    - "K"
    - "R"
    - "Τ"
    - "Φ"
  first_gate_failure: "Archetype Gate"
  restoration:
    - "Archetypal Reclassification"
    - "Geometry Re-Alignment"
    - "Role Boundary Restoration"
    - "Expression Audit"
    - "Identity / Function Separation"
    - "Symbolic Recalibration"
    - "Admissible Region Repair"
    - "Hidden Debt Accounting"
    - "Time-Validated Re-Entry"