Claim Mutation / HIR Encapsulation Simulator v0.0.4 — Equation Fidelity + Public Readiness Patch

Did the claim stay in resonance?

A claim can be repeated endlessly without being preserved.
Repetition without resonance is just noise.

A claim survives transfer when the carried version remains structurally resonant with the original.

Misinformation is not always invented. Sometimes resonance breaks during transfer.

A claim can keep its words and lose its meaning.

This simulator does not decide whether the claim is true. It checks whether the carried version still preserves what was originally claimed.

HIR = Honesty, Integrity, Respect
Honesty names the claim accurately.
Integrity keeps source, context, uncertainty, scope, consent, and repair path attached.
Respect prevents distortion, weaponized ambiguity, and erasure of limits.

Public-readiness rule: The HIR capsule does not make the claim true. It helps the carried version remain structurally resonant with the original by keeping source, context, uncertainty, scope, consent, and repair path attached.

Dual transfer paths

S_claim = A_source × B_meaning − P_mutation
S_encapsulated = (A_source × B_meaning × (1 + C_HIR)) − P_mutation

The same starting claim runs through two paths: one exposed to mutation pressure, one carried inside an HIR capsule that adds resonance lift by keeping source, context, uncertainty, scope, consent, and repair path attached.

v0.0.4 patch: equation fidelity, resonance-lift explanation, and public-readiness language. Route logic, thresholds, presets, and shareable state unchanged.

Explain this to me as…

This tool checks whether a carried claim remains structurally resonant with the original after being summarized, quoted, clipped, reposted, cited, or argued against.

Original claim → two transfer paths

Original Claim

Carried / Public Version

v0.0.2 does not automatically analyze the text. The text fields preserve scenario context for the export report while the sliders model the resonance and mutation-pressure conditions.

Simulator

v0.0.3 route-proof note: thresholds remain strict. Severe low-resonance cases route to QUARANTINE_CLAIM rather than softer meaning-drift language.

Claim preservation

Mutation pressure

HIR capsule attachments

Route gates

Drift Path
exposed transfer / resonance loss
MEANING DRIFT

Resonance Support
Mutation Pressure
Resonance Loss Risk
Claim Resonance
Read:

Why this route?

Action:

Drift Flags

Protected Carry Path
HIR capsule / resonance preservation
HIR ENCAPSULATED

Capsule Strength
Encap Support
Encap Stability
Resonance Lift
Read:

Why this route?

Action:

Capsule Flags

Exportable pressure report

How the model works

S_claim = A_source × B_meaning − P_mutation
S_encapsulated = (A_source × B_meaning × (1 + C_HIR)) − P_mutation
Encapsulated Support = Resonance Support × (1 + Capsule Strength)

The Drift Path shows the claim traveling exposed: base resonance support is eroded by mutation pressure.

The Protected Carry Path shows the same claim traveling inside an HIR capsule. The capsule does not replace the original claim and does not make the claim true — it provides resonance lift. The factor (1 + C_HIR) adds protective lift so the carried version better survives compression, speed, paraphrase, incentive, and status pressure while preserving source, context, uncertainty, scope, consent, and repair path.

A good paraphrase changes the route while preserving the claim. A mutation changes the claim while pretending it only changed the route.

Where:
A_source = Source Match
B_meaning = 0.30×Meaning Match + 0.20×Context Preserved + 0.20×Uncertainty Preserved + 0.15×Scope Preserved + 0.15×Source Match
C_HIR = 0.20×Source Attached + 0.18×Context Attached + 0.18×Uncertainty Attached + 0.16×Scope Attached + 0.14×Consent Attached + 0.14×Repair Path Attached
P_mutation = average mutation pressure

Route taxonomy