LAW-090 — Memory Update Law

Open archive search
Archive registry entry

LAW-090 — Memory Update Law

Principles remain coherent only when memory can update from truth, feedback, recurrence, and time.

draftid: LAW-090version: 1.0.0updated: 2026-06-16
Archive Progress

This section can be read now; registry depth and cross-references are still being strengthened.

Foundation
Online

The section has a stable overview route and basic reader context.

Technical Layer
Online

A deeper technical overview is available.

Registry
Current

171 registry entries are available.

Cross-links
Curating

Related concepts are being connected conservatively for accuracy.

0. Plain Statement

Principles remain coherent only when memory can update.

Plain-language version:

A system cannot remain aligned if its memory refuses to learn from truth, feedback, recurrence, harm, repair, and time. When memory freezes around an old interpretation, principle becomes ideology. When memory updates coherently, principle remains alive.


1. Formal Definition

The Memory Update Law states that principle-guided systems require updateable memory to preserve coherence across time.

Principles do not operate in a static field. Conditions change. Evidence accumulates. Hidden debt returns. Recurrence reveals what was not repaired. Affected-node feedback clarifies what was misread. A prior interpretation may become incomplete, outdated, overgeneralized, or inverted.

A system that cannot update memory may continue to claim principle alignment while acting from obsolete or distorted maps.

Memory must update from:

  • truth;
  • evidence;
  • recurrence;
  • affected-node feedback;
  • failed predictions;
  • hidden debt return;
  • boundary stress;
  • legitimacy loss;
  • restoration outcomes;
  • time validation;
  • changed capacity;
  • changed context;
  • changed scale;
  • changed coupling.

Without memory update, principles become rigid, identity-bound, ideological, performative, or inverted.

With memory update, principles remain living constraint fields.


2. Canonical Form

Core form:

textScroll
principle coherence requires updateable memory

Learning form:

textScroll
M_update = f(Ψ, Τ, recurrence, Au, FI, H_return)

Failure form:

textScroll
memory frozen while field changes ⇒ ideology hardening + H↑ + ι↑

Restoration-valid form:

textScroll
feedback integrated + recurrence learned + principle field recalibrated ⇒ O↑ / H↓ over Τ

Related variables:

textScroll
O, H, ε, ι, Au, R, R_eff, BΣ, K, σ, µᵢ, Φ, Λ, ⊗, Γ, Π, ℛ, Θ, Σ, Ψ, Τ, FI, M, M_update, M_integrity, M_half_life, ☷ᵢ

Where:

TableScroll
VariableMeaning in this law
MMemory state of the system
M_updateAbility of memory to update from feedback, recurrence, evidence, and time
M_integrityReliability, fidelity, continuity, and non-corruption of memory
M_half_lifeHow long valid memory remains accessible and effective
☷ᵢPrinciple field whose constraint logic must update without losing coherence
ΨField and affected-node feedback that updates memory
ΤTime validation and temporal learning horizon
FIFeedback integrity required for learning
AuAuditability required to know what happened and why
H_returnHidden debt returning as evidence of prior misread or non-repair
OCoherence preserved when memory updates correctly
HHidden debt accumulated when memory refuses truth
ι / ΞInversion rises when old memory is defended against new evidence
µᵢMeaning / agent integrity; degrades when memory contradicts reality
Boundary integrity; memory must update around consent, scope, and coupling history
K / σSlack / sovereignty; memory update should reduce repeated burden
R / R_effRestoration capacity required to repair what memory learns
ΦVisible success proxy; may reward forgetting or selective memory
ΛCompatibility between old interpretation and current field state
Coupling history that memory must preserve or revise
ΓClassifies memory as valid, outdated, corrupted, selective, or identity-bound
ΠControls, curation, suppression, narrative filters, or update gates
Restoration action that repairs memory, debt, and trajectory
ΘHumility required to revise memory without collapsing principle
ΣScope of memory update and principle recalibration
LLegitimacy strengthened when memory updates truthfully

3. Core Mechanism

The law unfolds when a system either learns from time or defends memory against time.

Coherent memory update pathway

textScroll
event / action / claim occurs
→ field feedback emerges
→ recurrence and hidden debt are tracked
→ memory updates
→ principle field recalibrates
→ future action improves
→ O rises or stabilizes over time

Frozen memory pathway

textScroll
event / action / claim occurs
→ field feedback contradicts memory
→ contradiction is ignored or reclassified
→ old memory is defended
→ principle hardens into ideology
→ H↑ + ι↑ + L↓

The core mechanism is:

textScroll
memory that cannot update turns principle into ideology

Detailed mechanism:

  1. A system forms memory.

Memory stores prior truth, experience, interpretation, harm, repair, success, failure, identity, doctrine, policy, precedent, or lesson.

  1. The field changes or responds.

New evidence, feedback, recurrence, harm, boundary stress, or time validation reveals whether the memory remains accurate.

  1. The system faces contradiction.

The old memory may no longer match the field. The prior interpretation may be incomplete, overfit, selective, or wrong.

  1. The system either updates or defends.

Coherent systems update memory while preserving principle integrity. Incoherent systems defend old memory as identity, ideology, tradition, authority, or certainty.

  1. Principles either remain alive or fossilize.

Updated memory keeps principle as a living constraint field. Frozen memory turns principle into rigid narrative.

  1. Time reveals learning integrity.

If recurrence decreases and debt falls, memory update was valid. If recurrence persists, the system did not learn.


4. When This Law Applies

This law applies whenever a system uses memory, precedent, doctrine, policy, identity, experience, tradition, data, history, model weights, institutional learning, cultural narrative, or personal interpretation to guide future action.

It is especially important when:

  • a principle remains the same but context changes;
  • feedback contradicts prior interpretation;
  • recurrence shows repair failure;
  • hidden debt returns after apparent success;
  • an institution repeats the same failure;
  • AI systems retain flawed user or world models;
  • governance relies on outdated legitimacy assumptions;
  • cultures preserve traditions after conditions change;
  • security systems keep old threat models;
  • biological systems repeat chronic patterns;
  • restoration systems keep applying a method after recurrence;
  • memory becomes identity-bound;
  • people say “we have always done it this way”;
  • evidence is reclassified to protect an old narrative.

The law applies strongly when:

textScroll
field feedback contradicts stored memory

or when:

textScroll
recurrence persists but the system claims it has learned

Typical domains:

TableScroll
DomainMemory Update Expression
AI systemsUser models, safety rules, reward policies, memory systems, and representation layers must update from feedback and audit.
SecurityThreat models must update from new attacks, failures, incidents, and recurrence.
InstitutionsPolicy memory must update from harmed-node feedback and repair outcomes.
Medicine / biologyRecovery memory must update from tolerance, recurrence, flare, and adaptation history.
EconomyMarket memory must include externalized cost, instability, and hidden debt return.
GovernanceLegitimacy memory must update from public trust, repair, failure, and consequence.
CultureTradition must remain updateable under truth, harm, and changed conditions.
RestorationRestoration learns only when recurrence and debt outcomes update future action.

5. When This Law Does Not Apply

This law should not be used to erase stable memory, continuity, tradition, identity, or principle.

Some memory should remain stable because it preserves truth, harm history, boundary lessons, restoration proof, identity continuity, or hard-earned coherence. Updating memory does not mean rewriting the past to fit the present.

False-positive cases:

TableScroll
CaseWhy it is not a failure to update
A system preserves memory of harm to prevent recurrenceStable memory protects coherence
A principle remains valid despite changing circumstancesThe principle field is stable while application updates
A boundary remains closed because time validation has not changed conditionsMemory preserves safety
A tradition remains coherent under auditContinuity can be valid
A model refuses to update from low-quality or manipulative feedbackUpdate requires feedback integrity

Important distinction:

Memory must be updateable, not unstable. Coherent memory preserves what remains true and revises what time disproves.


6. Diagnostic Signature

Canonical diagnostic:

textScroll
principle coherence requires updateable memory

Warning signature:

textScroll
feedback contradicts memory
recurrence persists
memory defended
principle language remains
H↑
ι↑
⇒ ideology hardening

Common indicators:

TableScroll
DiagnosticExpected movementInterpretation
M_update↑ / intactMemory must update from feedback and time
M_integritystable / ↑Memory must remain accurate, continuous, and non-corrupt
M_half_lifeappropriateUseful memory should neither vanish nor fossilize
ΨintegratedField feedback must update memory
ΤactiveTime validation informs memory
FIintactFeedback quality determines update quality
AuintactMemory update must be traceable
H↓ if learnedHidden debt should fall after valid update
recurrenceRecurrence decreases when memory learns
ι / ΞInversion decreases when memory admits contradiction
µᵢstable / ↑Meaning integrity improves when memory matches reality
clearerBoundaries update from history without overgeneralization
L↑ under auditLegitimacy improves when the system learns visibly
Φnot sufficientPerformance metrics do not prove memory update

Additional diagnostics:

TableScroll
DiagnosticUse
Memory Update IntegrityTests whether memory changes when truth requires it
Learning IntegrityTests whether the system actually learns
Feedback IntegrationMeasures whether field signals alter future behavior
Recurrence IntegrationMeasures whether repeated failures update memory
Memory Half-LifeTests whether valid lessons persist
Memory IntegrityDetects corruption, erasure, or narrative rewriting
Truth ResponsivenessTests responsiveness to evidence
Ideology HardeningDetects frozen memory defended as principle
Identity BindingDetects memory fused with identity claims
Temporal ProofValidates learning over time

7. Failure Pattern

If ignored, this law produces ideology hardening, selective memory, and repeated failure.

General failure pathway:

textScroll
memory formed
→ field changes / feedback contradicts
→ memory does not update
→ old interpretation is defended
→ recurrence continues
→ H↑
→ principle becomes ideology

Common failure modes:

  • Frozen Memory — memory cannot update from new truth.
  • Ideology Hardening — principle becomes rigid narrative.
  • Recurrence Ignored — repeated failure does not update future action.
  • Feedback Non-Integration — feedback is heard but not incorporated.
  • Memory Corruption — records are distorted, erased, or rewritten.
  • Selective Memory — convenient details persist while contradictory details disappear.
  • Identity-Bound Memory — memory cannot change because identity depends on it.
  • Principle Fossilization — living principle becomes fixed doctrine.
  • Learning Theater — system claims learning without behavioral update.
  • Narrative Lock — story overrides evidence.
  • Audit Avoidance — memory cannot be checked.
  • Inversion Persistence — old inversion survives because memory protects it.
  • Meaning Collapse — contradiction between memory and field breaks trust.
  • Legitimacy Debt — authority decays because the system does not learn.

Compact failure signature:

textScroll
M frozen + Ψ ignored + recurrence↑ ⇒ H↑ + ι↑ + L↓

8. Restoration Implications

Restoration requires repairing memory update pathways.

The first restoration question is not:

textScroll
What do we remember?

The first restoration question is:

textScroll
Can memory update when truth, feedback, recurrence, and time require it?

Restoration priorities:

  1. Identify the stored memory or interpretation.
  2. Audit whether field feedback contradicts it.
  3. Track recurrence and hidden debt return.
  4. Assess whether memory is updateable or identity-bound.
  5. Restore auditability of records and claims.
  6. Restore feedback integration.
  7. Separate stable truth from outdated interpretation.
  8. Repair hidden debt created by frozen memory.
  9. Recalibrate principle fields with updated memory.
  10. Time-validate that future action changes.

Relevant restoration arcs:

TableScroll
Restoration ArcWhy it applies
Memory Update RestorationReopens memory to truth and time
Learning Integrity RestorationConverts feedback into behavioral change
Feedback IntegrationEnsures field signals update future action
Recurrence IntegrationTreats repeated failure as learning signal
Truth RecoveryRecovers what memory suppressed or distorted
Memory Integrity RepairRepairs corruption, erasure, or selective record
Identity DecouplingAllows memory to update without identity collapse
Inversion ReductionRemoves old inverted interpretations
Auditability RestorationMakes memory traceable and reviewable
Hidden Debt ReductionRepairs cost of frozen memory
Coherence Trajectory RecalibrationUpdates future action according to learned truth
Temporal ValidationConfirms learning holds over time

Minimal restoration sequence:

textScroll
identify memory claim
→ audit against Ψ / recurrence / H_return / Τ
→ distinguish stable truth from outdated interpretation
→ update M
→ repair debt
→ recalibrate ☷ᵢ execution
→ validate behavior change over Τ

Temporal validation requirement:

textScroll
M_update intact
M_integrity stable
feedback integrated
recurrence↓
H↓
ι↓
Au intact
FI intact
principle execution changes
O stable or rising
L stable or rising

9. Design Rule

Do not let memory become ideology.

Operational design requirements:

  • Treat memory as evidence-bearing, not identity-proof.
  • Preserve truthful continuity.
  • Keep interpretations updateable.
  • Track recurrence.
  • Track hidden debt return.
  • Preserve audit trails.
  • Preserve affected-node feedback.
  • Separate what happened from what it meant.
  • Separate stable principle from outdated application.
  • Prevent narrative filters from blocking correction.
  • Update policy, practice, model, or boundary from validated learning.
  • Time-validate that memory updates change behavior.

Avoid:

  • defending old memory against new truth;
  • erasing inconvenient history;
  • rewriting records to preserve legitimacy;
  • treating tradition as proof;
  • treating doctrine as proof;
  • treating past success as future coherence;
  • claiming learning without behavior change;
  • letting identity depend on never being wrong;
  • treating recurrence as anomaly forever;
  • letting AI memory personalize without correction;
  • letting institutional memory exclude harmed-node evidence;
  • letting cultural memory preserve harm as sacred.

10. Cross-Scale Expressions

TableScroll
Scale / LayerExpression of the Law
U0 — SubstrateBiological or physical systems update from stress history, tolerance, injury, recovery, and recurrence.
U1 — Energy / capacityMemory must track capacity depletion and recovery, not assume old capacity remains.
U2 — Boundary / interfaceBoundaries update from coupling history, harm, consent, and trust.
U3 — Process / executionProcedures must change after validated failure.
U4 — Classification / claimInterpretations must update when field outcomes contradict them.
U5 — Time / delayMemory is validated by time and recurrence.
U6 — Field effectAffected-node outcomes update memory if feedback integrity holds.
U7 — Recurrence / memoryPrimary layer: recurrence shows whether memory has learned.
U8 — Environment / forcingChanged environmental conditions require memory recalibration.

11. Examples

Example A — Institutional Learning Theater

Scenario:

An institution says it has learned from harm, but the same failure pattern recurs under new language.

Law expression:

textScroll
learning claim + recurrence↑ ⇒ M_update failure

Interpretation:

The institution may have updated messaging but not operational memory.


Example B — AI User Model Drift

Scenario:

An AI system retains outdated assumptions about a user and keeps acting on them despite correction, changed preferences, or new context.

Law expression:

textScroll
AI memory + correction ignored ⇒ representation debt↑

Interpretation:

Memory must remain user-correctable, scoped, and updateable.


Example C — Security Threat Model Fossilization

Scenario:

A security team defends an old threat model while new attack patterns repeatedly bypass controls.

Law expression:

textScroll
recurrence + old model defended ⇒ security M_update failure

Interpretation:

Threat memory must update from incident reality, not past doctrine.


Example D — Cultural Tradition Under Audit

Scenario:

A tradition is defended because it is old, even though affected-node feedback and recurring harm show that conditions have changed.

Law expression:

textScroll
tradition + feedback ignored ⇒ ideology hardening

Interpretation:

Continuity is valid only when memory remains truthful and updateable.


Example E — Biological Recovery Memory

Scenario:

A recovery plan keeps using an intervention that once helped, even though current tolerance, energy state, and recurrence patterns show it now overloads the system.

Law expression:

textScroll
old recovery memory + current σ mismatch ⇒ intervention debt↑

Interpretation:

Biological memory must update from current tolerance and ring-down, not only past success.


Example F — Governance Legitimacy Assumption

Scenario:

A governance system assumes legitimacy from historical authority, while current trust, repair, participation, and consequence signals have degraded.

Law expression:

textScroll
past legitimacy memory + current L↓ ignored ⇒ legitimacy debt↑

Interpretation:

Legitimacy memory must update from current field effects.


12. Relationship to Nearby Laws

TableScroll
Related LawRelationship
LAW-001 — Coherence Priority LawMemory updates serve coherence
LAW-002 — Coherence Trajectory LawMemory must track trajectory, not only events
LAW-006 — Time Validation LawTime validates or invalidates memory
LAW-008 — Recurrence Validation LawRecurrence is a primary memory update signal
LAW-009 — U4 / U6 Truth LawInterpretive memory must update from field truth
LAW-010 — Hidden Debt Accumulation LawFrozen memory accumulates debt
LAW-011 — Hidden Debt Return LawHidden debt return updates memory if allowed
LAW-013 — Auditability-Debt LawMemory must remain auditable
LAW-016 — Inversion Formation LawFrozen memory preserves inversion
LAW-027 — Meaning Collapse Threshold LawMeaning collapses when memory contradicts reality
LAW-028 — Control Density to Meaning Loss LoopControl may prevent memory update
LAW-030 — Slack Sovereignty LawMemory should reduce repeated slack loss
LAW-031 — Observability Collapse LawPoor observability prevents memory update
LAW-036 — Signal Artifact LawMemory must distinguish signal from artifact
LAW-038 — Pattern Recognition Discipline LawMemory must update without overfitting
LAW-039 — Identity-Binding Hard RuleMemory should not be fused to identity prematurely
LAW-048 — Feedback Integrity LawFeedback integrity enables memory update
LAW-052 — Stability Proof LawStability claims require memory of perturbation outcomes
LAW-061 — Restoration Sequencing LawMemory stores correct sequence and updates from failure
LAW-064 — Restoration Debt Reduction LawRestoration memory is valid when debt decreases
LAW-065 — Pseudo-Restoration LawPseudo-restoration often relies on memory non-update
LAW-067 — Temporal Proof LawMemory must incorporate temporal proof
LAW-083 — Normalization Shield LawNormalized memory can shield harm from audit
LAW-085 — Principle Constraint Field LawPrinciple fields require updateable memory to remain alive
LAW-086 — Principle Inversion LawMemory update detects and reduces inversion
LAW-087 — Shadow–Light Execution LawExecution memory must distinguish possible from permissible
LAW-088 — Empathy–Sovereignty LawEmpathic models must update from the represented node
LAW-089 — Wisdom Timing LawTiming decisions must update from memory and feedback
LAW-091 — Archetype Localization LawArchetypal memory must localize to current field, not fossilize
LAW-095 — Meaning Directionality LawMeaning memory directs future action
LAW-097 — Experience–Interpretation Separation LawMemory must separate event from interpretation
LAW-098 — Awakening Stabilization LawHigh-gain experience requires memory integration
LAW-101 — Paradox Dimensionality LawMemory must update when paradox reveals missing dimension
LAW-102 — Legitimacy Audit LawLegitimacy depends on visible learning
LAW-111 — Meaning Audit LawMeaning claims require memory audit
LAW-127 — AI Decision Pipeline LawAI pipelines require updateable memory, logs, and learning paths
LAW-128 — AI Representation LawAI representation memory must remain correctable by represented parties

Aliases folded into this law:

  • Memory Update Law
  • Updateable Memory Law
  • Principle Memory Law
  • Memory Must Update Law
  • Anti-Ideology Memory Law
  • Learning Integrity Law
  • Truth-Responsive Memory Law

Deduplication note:

This law should remain the root memory-update law for principles, archetypes, meaning, restoration, AI representation, and institutional learning. LAW-097 separates experience from interpretation, LAW-098 covers stabilization after high-gain openings, LAW-102 covers legitimacy learning under audit, LAW-127 covers AI decision-pipeline memory, and LAW-128 specializes represented-party memory correction.


13. Operator Mapping

TableScroll
OperatorRole in this law
ΓClassifies memory as valid, outdated, corrupted, selective, identity-bound, or updateable
ΠProvides memory gates, curation, suppression, logging, retention, and update controls
ΞCaptures inversion when old memory is defended against new truth
Coupling history must be remembered and updated
Repairs hidden debt and recalibrates action after memory update
ΤValidates memory through time, recurrence, and delayed effects
ΘEnables revision without collapse into shame, defensiveness, or ideology
ΣDefines scope of memory update and principle recalibration
ΨField and affected-node feedback updates memory
ΛCompatibility tests whether old memory still fits current field state

Coherent operator sequence:

textScroll
Ψ(feedback) + Τ(recurrence/time) → Au/FI(validate signal) → Θ(update humility) → Γ(classify memory status) → Σ(scope update) → ℛ(repair debt / recalibrate principle) → future action changes → Τ(validate learning)

Inverted operator sequence:

textScroll
feedback contradicts memory → Γ(old memory defended) → Π(filter contradiction) → M frozen → H↑ → Ξ / ι↑ → recurrence persists → L↓

14. Machine-Readable Summary

yamlScroll
id: "LAW-090"
name: "Memory Update Law"
type: "law"
status: "draft"
family:
  - "Principle, Archetype, and Meaning Laws"
summary: "Principles remain coherent only when memory can update from truth, feedback, recurrence, and time."
canonical_statement: "Principles remain coherent only when memory can update."
core_form: "principle coherence requires updateable memory"
learning_form: "M_update = f(Ψ, Τ, recurrence, Au, FI, H_return)"
failure_form: "memory frozen while field changes ⇒ ideology hardening + H↑ + ι↑"
restoration_valid_form: "feedback integrated + recurrence learned + principle field recalibrated ⇒ O↑ / H↓ over Τ"
variables:
  primary:
    - "M"
    - "M_update"
    - "M_integrity"
    - "M_half_life"
    - "☷ᵢ"
    - "Ψ"
    - "Τ"
    - "FI"
    - "Au"
    - "H_return"
  secondary:
    - "O"
    - "H"
    - "ε"
    - "ι"
    - "Ξ"
    - "R"
    - "R_eff"
    - "BΣ"
    - "K"
    - "σ"
    - "µᵢ"
    - "Φ"
    - "Λ"
    - "⊗"
    - "Γ"
    - "Π"
    - "ℛ"
    - "Θ"
    - "Σ"
    - "L"
diagnostics:
  - "Memory Update Integrity"
  - "Learning Integrity"
  - "Feedback Integration"
  - "Recurrence Integration"
  - "Memory Half-Life"
  - "Memory Integrity"
  - "Truth Responsiveness"
  - "Ideology Hardening"
  - "Identity Binding"
  - "Effective Auditability"
  - "Coherence Trajectory"
  - "Temporal Proof"
failure_modes:
  - "Frozen Memory"
  - "Ideology Hardening"
  - "Recurrence Ignored"
  - "Feedback Non-Integration"
  - "Memory Corruption"
  - "Selective Memory"
  - "Identity-Bound Memory"
  - "Principle Fossilization"
  - "Learning Theater"
  - "Narrative Lock"
  - "Audit Avoidance"
  - "Inversion Persistence"
  - "Meaning Collapse"
  - "Legitimacy Debt"
restoration_arcs:
  - "Memory Update Restoration"
  - "Learning Integrity Restoration"
  - "Feedback Integration"
  - "Recurrence Integration"
  - "Truth Recovery"
  - "Memory Integrity Repair"
  - "Identity Decoupling"
  - "Inversion Reduction"
  - "Auditability Restoration"
  - "Hidden Debt Reduction"
  - "Coherence Trajectory Recalibration"
  - "Temporal Validation"
related_laws:
  - "LAW-001"
  - "LAW-002"
  - "LAW-006"
  - "LAW-008"
  - "LAW-009"
  - "LAW-010"
  - "LAW-011"
  - "LAW-013"
  - "LAW-016"
  - "LAW-027"
  - "LAW-028"
  - "LAW-030"
  - "LAW-031"
  - "LAW-036"
  - "LAW-038"
  - "LAW-039"
  - "LAW-048"
  - "LAW-052"
  - "LAW-061"
  - "LAW-064"
  - "LAW-065"
  - "LAW-067"
  - "LAW-083"
  - "LAW-085"
  - "LAW-086"
  - "LAW-087"
  - "LAW-088"
  - "LAW-089"
  - "LAW-091"
  - "LAW-095"
  - "LAW-097"
  - "LAW-098"
  - "LAW-101"
  - "LAW-102"
  - "LAW-111"
  - "LAW-127"
  - "LAW-128"
related_invariants:
  - "INV-001"
  - "INV-002"
  - "INV-006"
  - "INV-077"
  - "INV-079"
  - "INV-080"
operator_sequence:
  coherent:
    - "Ψ feedback"
    - "Τ recurrence/time"
    - "Au/FI validate signal"
    - "Θ update humility"
    - "Γ classify memory status"
    - "Σ scope update"
    - "ℛ repair debt / recalibrate principle"
    - "future action changes"
    - "Τ validate learning"
  inverted:
    - "feedback contradicts memory"
    - "Γ old memory defended"
    - "Π filter contradiction"
    - "M frozen"
    - "H↑"
    - "Ξ / ι↑"
    - "recurrence persists"
    - "L↓"
aliases:
  - "Memory Update Law"
  - "Updateable Memory Law"
  - "Principle Memory Law"
  - "Memory Must Update Law"
  - "Anti-Ideology Memory Law"
  - "Learning Integrity Law"
  - "Truth-Responsive Memory Law"
deduplication_note: "Root memory-update law for principles, archetypes, meaning, restoration, AI representation, and institutional learning. LAW-097 separates experience from interpretation, LAW-098 covers stabilization after high-gain openings, LAW-102 covers legitimacy learning under audit, LAW-127 covers AI decision-pipeline memory, and LAW-128 specializes represented-party memory correction."
source: "content/archive/laws/technical.md"

15. Compact Card Version

LAW-090 — Memory Update Law

Principles remain coherent only when memory can update.

Core form:

textScroll
principle coherence requires updateable memory

Learning form:

textScroll
M_update = f(Ψ, Τ, recurrence, Au, FI, H_return)

Plain meaning:

A system cannot remain aligned if its memory refuses to learn from truth, feedback, recurrence, harm, repair, and time. When memory freezes around an old interpretation, principle becomes ideology. When memory updates coherently, principle remains alive.

Failure form:

textScroll
memory frozen while field changes ⇒ ideology hardening + H↑ + ι↑

Restoration-valid form:

textScroll
feedback integrated + recurrence learned + principle field recalibrated ⇒ O↑ / H↓ over Τ

Primary variables:

M, M_update, M_integrity, M_half_life, ☷ᵢ, Ψ, Τ, FI, Au, H_return, O, H, ι, Ξ, , K, σ, µᵢ, Γ, Π, , Θ, Σ, L

Diagnostic signature:

Feedback contradicts memory, recurrence persists, hidden debt returns, but the old interpretation is defended while principle language remains and behavior does not change.

Failure risk:

Frozen memory, ideology hardening, recurrence ignored, feedback non-integration, memory corruption, selective memory, identity-bound memory, principle fossilization, learning theater, narrative lock, audit avoidance, inversion persistence, meaning collapse, legitimacy debt.

Restoration priority:

Audit memory against feedback, recurrence, hidden debt return, and time; separate stable truth from outdated interpretation; update memory; repair debt; recalibrate principle execution; and time-validate that future behavior changes.