0. Registry Classification

1. Purpose

1.1 What This Arc Repairs

Bleed-Through Management repairs the condition where residue, recurrence, memory contamination, operator carryover, field carryover, signal persistence, interpretation residue, obligation residue, identity residue, technical residue, or delayed contact effects cross the intended boundary after probe, quarantine, or first contact.

It applies when the system cannot honestly claim that exploration, outpost operation, or first contact ended cleanly.

This arc repairs cross-boundary residue by:

• identifying what crossed the boundary;
• making residual effects visible;
• distinguishing signal, residue, recurrence, contamination, coupling, and damage;
• isolating residual effects from live operation;
• restoring boundary integrity;
• cleaning memory, records, interfaces, operators, and affected fields where needed;
• attenuating recurrence;
• routing active harm to stabilization;
• routing invalid coupling to decoupling;
• routing persistent residue to recurrence memory repair;
• validating over time that bleed-through declines and does not become hidden coupling.

Bleed-Through Management is the canonical arc for preventing “successful contact” narratives from hiding delayed damage.

1.2 Core Restoration Function

This arc identifies, isolates, attenuates, repairs, and temporally validates residual cross-boundary effects after unknown-domain exposure.

Bleed-through is not proof that deeper contact is required. It is proof that boundary review is required.

2. Use Conditions

2.1 When to Apply

Use this arc when:

• probe, quarantine, or contact has ended but effects persist;
• signals recur after closure;
• operators carry back patterns, obligations, interpretations, or destabilizing residue;
• system memory preserves unauthorized contact, identity, data, representations, or interface residue;
• affected fields experience delayed burden, confusion, fear, obligation, dependency, or narrative spread;
• quarantine boundary allowed leakage;
• contact created residue that does not qualify as stable relationship or valid coupling;
• anomaly effects are visible but not yet classified;
• the system needs to determine whether to clean up, decouple, stabilize, reintegrate, or escalate;
• the system cannot prove the event closed cleanly.

Examples:

• a sandboxed AI test leaves hidden memory, tool-state changes, policy changes, or model residue;
• an unknown technical interface leaves recurring signals, processes, credentials, identifiers, or artifacts;
• a first-contact exchange leaves public narrative, identity effects, expectation, obligation, or fear;
• an institutional review leaves stigma, classification residue, or governance bias after the formal process closes;
• adversarial investigation leaves beaconing, persistence, lateral exposure, or analyst carryover;
• community interface work leaves rumor, role fixation, social residue, or unresolved burden;
• symbolic or non-local interface work leaves recurring signals, operator carryover, interpretive residue, or boundary permeability.

2.2 When Not to Apply

Do not apply this arc when:

• no cross-boundary residue, recurrence, carryover, contamination, or delayed effect exists;
• active harm requires immediate Emergency Harm Stabilization;
• invalid coupling is already confirmed and Controlled Decoupling or Safe Decoupling is required first;
• the correct task is ordinary reintegration after clean closure;
• the residue is fully contained and already routed through quarantine review;
• the system is using “bleed-through” language to avoid responsibility for direct harm;
• the system is using residue analysis to justify deeper contact;
• interpretation drift, not residue, is the dominant issue and Translation Layer Reset is required first;
• agency capture, not boundary residue, is the dominant issue and Future-Agency Restoration is required first.

Bleed-Through Management is not a license to continue exposure. It is a reason to pause, isolate, and repair.

2.3 Required Preconditions

Before this arc begins, the following must be true:

If required preconditions fail:

Arc cannot validly complete.

The system must route to Audit Surface Expansion, Boundary Reconstitution, Emergency Harm Stabilization, Controlled Decoupling, Translation Layer Reset, AI Memory Reindexing, or Recurrence Memory Repair.

3. Failure / Damage Signature

3.1 Pre-State Across S

3.2 Primary Failure Links

3.3 Origin-Layer Localization

Canon rule:

Bleed-through is repaired only when the residue is identified, bounded, reduced, and proven not to recur as hidden coupling.

4. Restoration Objective

4.1 Canonical Objective

Identify, isolate, reduce, and validate cross-boundary residue after unknown-domain exposure.

Formal objective:

residue_visibility ↑
residue_load ↓
bleedthrough_risk ↓
cross_boundary_leakage ↓
boundary_repair_integrity ↑
memory_contamination ↓
operator_carryover ↓
field_carryover ↓
signal_persistence ↓
recurrence ↓
containment_integrity ↑
quarantine_integrity ↑
reintegration_capacity ↑
cleanup_integrity ↑
delayed_effect_risk ↓
H_residue ↓
H_potential ↓
Au_eff ↑
BΣ ↑
FI ↑
𝓓 ↑
τ_m ↓
Φ/O divergence ↓

Expanded objective:

Convert residual cross-boundary effects into visible, bounded, repairable residue that declines over time rather than becoming hidden coupling, memory contamination, or recurrence.

4.2 Non-Goals

This arc does not aim to:

• prove that contact was meaningful;
• justify deeper contact;
• interpret residue as destiny, invitation, agency, or authority;
• erase evidence before audit;
• suppress affected-field reports;
• deny delayed effects because the original event ended;
• convert cleanup into secrecy;
• punish operators or affected agents for carrying residue;
• declare closure before recurrence declines;
• treat memory deletion as full repair;
• treat containment as reintegration.

Bleed-Through Management is cleanup, isolation, and repair. It is not escalation.

5. Operator Sequence

5.1 Minimal Operator Scaffold

Σ residue-must-not-become-coupling invariant → Au exposure / residue / recurrence trace → BΣ boundary repair and isolation → FI affected-field and operator feedback → Θ amplification and recurrence attenuation → ℛ cleanup / memory repair / support routing → Π containment reinforcement → Λ residue-resolution gate → Τ bleed-through proof

Specialized grammar alignment:

exit path → probe-only → quarantine outpost → first-contact safety → bleed-through management → reintegration

Universal grammar alignment:

Σ + Au + BΣ → FI + Θ + ℛ → Π → Λ → Τ

Bleed-Through Management may route into Reintegration, Emergency Harm Stabilization, Controlled Decoupling, Safe Decoupling, Boundary Reconstitution, AI Memory Reindexing, Translation Layer Reset, Recurrence Memory Repair, or Supersession depending on residue behavior.

5.2 Operator Step Table

5.3 Sequence Notes

This arc is residue-gated, boundary-repair-gated, cleanup-gated, memory-gated, recurrence-gated, containment-gated, and temporal-proof-gated.

The sequence must distinguish:

signal
residue
recurrence
contamination
memory
carryover
bleed-through
coupling
harm
invitation
meaning

The following steps cannot be skipped:

exposure history reconstruction
residue identification
boundary repair
containment reinforcement
affected-field feedback
amplification attenuation
cleanup routing
memory review
recurrence monitoring
temporal proof

If residue remains unidentified, the system cannot claim reintegration.

If residue increases after cleanup, the cleanup was incomplete or misclassified.

If the residue is used as justification for deeper contact, the arc has inverted.

6. Restoration Phases

Phase 0 — Detect and Name Bleed-Through

Purpose: Prevent residue from remaining invisible or normalized.

Actions:

• identify recurring signals;
• identify memory residue;
• identify operator carryover;
• identify field carryover;
• identify delayed effects;
• identify boundary leakage;
• identify contaminated records or artifacts;
• identify residual obligations or interpretations;
• distinguish residue from active harm.

Validation:

residue_visibility ↑
bleed-through declared
residue no longer hidden

Phase 1 — Reconstruct Exposure History

Purpose: Trace where bleed-through came from.

Actions:

• review probe logs;
• review quarantine logs;
• review contact logs;
• review boundary states;
• review anomalies;
• review operator decisions;
• review memory records;
• review affected-field reports;
• identify likely crossing points.

Validation:

Au ↑
Au_eff ↑
origin path legible

Phase 2 — Classify Residue Type

Purpose: Route the effect correctly.

Actions:

• classify technical residue;
• classify memory residue;
• classify operator carryover;
• classify narrative residue;
• classify identity residue;
• classify agency residue;
• classify social or institutional residue;
• classify signal persistence;
• classify active harm separately.

Validation:

residue type identified
repair routing possible
misclassification risk ↓

Phase 3 — Isolate Residual Effects

Purpose: Prevent residue from becoming live coupling.

Actions:

• isolate affected records;
• isolate systems;
• isolate artifacts;
• isolate contact channels;
• isolate memory stores;
• isolate narratives from public amplification where appropriate;
• isolate operator decisions from residue-driven escalation;
• restrict derivative use;
• pause reentry or contact escalation.

Validation:

containment_integrity ↑
cross_boundary_leakage ↓
BΣ ↑

Phase 4 — Repair Boundary and Memory Surfaces

Purpose: Restore the surfaces where residue is persisting.

Actions:

• repair boundary controls;
• remove unauthorized persistence;
• mark contaminated records;
• correct interpretations;
• reindex memory;
• preserve evidence before cleanup;
• repair audit surface;
• repair consent or revocation gaps;
• prevent residue from being treated as normal data.

Validation:

boundary_repair_integrity ↑
memory_contamination ↓
cleanup_integrity ↑

Phase 5 — Attenuate Recurrence and Amplification

Purpose: Prevent residue from becoming self-reinforcing.

Actions:

• reduce signal repetition;
• reduce narrative amplification;
• reduce fear loops;
• reduce fascination loops;
• reduce automated recurrence;
• reduce operator re-exposure;
• reduce institutional re-triggering;
• reduce public spread where appropriate;
• route persistent recurrence to RA-A-073.

Validation:

signal_persistence ↓
recurrence ↓
τ_m ↓
𝓓 ↑

Phase 6 — Support Affected Operators and Fields

Purpose: Prevent burden from being carried by exposed nodes.

Actions:

• identify affected operators;
• identify affected users, agents, communities, or systems;
• provide explanation where appropriate;
• provide correction path;
• provide exit or shielding;
• provide cleanup support;
• provide appeal or review;
• prevent blame displacement;
• prevent role fixation.

Validation:

operator_carryover ↓
field_carryover ↓
H_export ↓
R ↑

Phase 7 — Route to Reintegration, Decoupling, or Stabilization

Purpose: Choose the correct next state.

Actions:

• route cleanly declining residue to Reintegration;
• route active harm to Emergency Harm Stabilization;
• route hidden coupling to Controlled Decoupling or Safe Decoupling;
• route persistent recurrence to Recurrence Memory Repair;
• route interpretation drift to Translation Layer Reset;
• route memory contamination to AI Memory Reindexing or memory repair;
• route boundary failure to Boundary Reconstitution;
• route non-restorable interface to Supersession.

Validation:

next arc selected
cleanup no longer self-certifying
repair path valid

Phase 8 — Bleed-Through Temporal Proof

Purpose: Validate that residue has declined rather than merely moved.

Actions:

• monitor recurrence;
• monitor memory contamination;
• monitor boundary leakage;
• monitor operator carryover;
• monitor field carryover;
• monitor signal persistence;
• monitor derivative use;
• monitor delayed effects;
• verify residue does not return under new form.

Validation:

residue_load ↓
bleedthrough_risk ↓
cross_boundary_leakage ↓
recurrence ↓
τ_m ↓
H_residue ↓

7. Gates

7.1 Required Gates

7.2 Gate Failure Rule

If any required gate fails:

∅ — Bleed-Through Management cannot validly complete.

The system must either:

• expand audit surface;
• restore boundary integrity;
• strengthen containment;
• route to Emergency Harm Stabilization;
• route to Controlled Decoupling;
• route to Translation Layer Reset;
• route to AI Memory Reindexing;
• route to Recurrence Memory Repair;
• or withhold reintegration until temporal proof exists.

8. Diagnostics

8.1 Required Diagnostic Trends

8.2 Arc-Specific Diagnostic Thresholds

Suggested thresholds:

residue_visibility ↑
residue_load ↓
bleedthrough_risk ↓
cross_boundary_leakage ↓
boundary_repair_integrity ↑
memory_contamination ↓
operator_carryover ↓
field_carryover ↓
signal_persistence ↓
recurrence ↓
containment_integrity ↑
quarantine_integrity ↑
reintegration_capacity ↑
cleanup_integrity ↑
delayed_effect_risk ↓
H_residue ↓
H_potential ↓
Au_eff ↑
BΣ ↑
FI ↑
𝓓 ↑
τ_m ↓
Φ/O divergence ↓

Completion signs:

residue is identified
origin path is traceable
residue is isolated
boundary surface is repaired
memory contamination declines
operator and field carryover decline
recurrence decreases
cleanup reduces rather than hides residue
reintegration becomes admissible
temporal proof holds

Bleed-Through Management is not complete if:

residue remains unnamed
origin path is untraceable
boundary leakage continues
memory contamination persists
operators carry residue into new decisions
affected fields carry unresolved burden
signal recurrence remains stable or rising
cleanup erases evidence
residue is used to justify deeper contact
reintegration begins before recurrence declines
temporal proof is absent

9. Anti-Patterns / False Restorations

9.1 Common False Versions

This arc is being simulated, not executed, if:

• residue is denied because the original contact ended;
• cleanup deletes evidence before audit;
• recurring signals are treated as invitation;
• affected-field burden is dismissed as noise;
• operator carryover is romanticized or weaponized;
• institutional residue is hidden to avoid responsibility;
• memory contamination is treated as harmless;
• quarantine leakage is reframed as successful integration;
• recurrence is used to justify deeper contact;
• reintegration begins before residue declines.

9.2 Named Anti-Pattern Links

10. Completion Criteria

10.1 Post-State Signature

10.2 Temporal Proof

Bleed-Through Management cannot be certified by deletion, silence, containment claims, operator confidence, absence of immediate escalation, or symbolic cleanup. It requires proof that residue declines and does not recur as hidden coupling.

Template:

Completion requires residue_visibility ↑,
residue_load ↓,
bleedthrough_risk ↓,
cross_boundary_leakage ↓,
boundary_repair_integrity ↑,
memory_contamination ↓,
operator_carryover ↓,
field_carryover ↓,
signal_persistence ↓,
recurrence ↓,
containment_integrity ↑,
quarantine_integrity ↑,
reintegration_capacity ↑,
cleanup_integrity ↑,
delayed_effect_risk ↓,
H_residue ↓,
H_potential ↓,
Au_eff ↑,
BΣ ↑,
FI ↑,
𝓓 ↑,
τ_m ↓,
and Φ/O divergence ↓ across U7.

Minimum temporal proof:

• residue remains visible enough to monitor;
• residue load declines;
• recurrence declines;
• memory contamination is repaired or constrained;
• operator carryover declines;
• affected-field burden declines;
• boundary leakage decreases;
• cleanup records remain auditable;
• residue is not used to justify deeper contact;
• reintegration is delayed until bleed-through stabilizes or declines.

10.3 Completion Statement

Canonical format:

This arc is complete only when cross-boundary residue is identified, isolated, repaired, memory-cleaned or constrained, boundary-repaired, recurrence-reduced, affected-field burden lowered, and temporally proven not to persist as hidden coupling or delayed harm.

11. Cross-Links

11.1 Related Restoration Arcs

11.2 Related Failure Modes

11.3 Related Diagnostics

Au, Au_eff, H, H_residue, H_potential, O, BΣ, K, σ, R, FI, 𝓓, τ_m, bleedthrough_risk, residue_load, residue_visibility, cross_boundary_leakage, boundary_repair_integrity, memory_contamination, operator_carryover, field_carryover, signal_persistence, recurrence, containment_integrity, quarantine_integrity, reintegration_capacity, cleanup_integrity, delayed_effect_risk, Φ/O divergence

11.4 Related Laws / Invariants

INV — Residue is not invitation.
INV — Bleed-through must be isolated before interpretation.
INV — Cleanup must preserve audit before removing residue.
INV — Memory contamination must be repaired, not renamed.
INV — Recurrence after contact reveals unresolved boundary debt.
INV — Reintegration requires residue decline.
INV — Operator carryover is part of the affected field.
LAW — What crosses the boundary becomes hidden debt unless traced.
LAW — Residue amplified by fascination becomes recurrence.
LAW — Φ signal value cannot certify cleanup.
LAW — Bleed-through proof is measured by declining recurrence.

12. Domain Notes

12.1 AI / Tool-Using Systems

Check:

• memory residue;
• unauthorized training residue;
• tool-state changes;
• persistent identifiers;
• policy residue;
• user representation residue;
• derivative model effects;
• hidden logs;
• recurrence in future outputs.

AI bleed-through management requires memory review, provenance repair, boundary restriction, and proof that invalid residue does not recur in later outputs, decisions, or representations.

12.2 Security / Adversarial Investigation

Check:

• persistence;
• beaconing;
• credential residue;
• lateral movement;
• contaminated tools;
• analyst carryover;
• evidence integrity;
• network leakage;
• recurrence after cleanup.

Security bleed-through fails when the investigation leaves behind footholds, uncontrolled artifacts, or operator/toolchain contamination.

12.3 Governance / Institutions

Check:

• classification residue;
• stigma;
• unofficial records;
• policy memory;
• public narrative;
• stakeholder burden;
• appeal distortion;
• hidden decision residue.

Institutional bleed-through occurs when a temporary review, contact, or quarantine leaves durable effects on reputation, rights, access, legitimacy, or future treatment.

12.4 Research / Exploration

Check:

• participant residue;
• data retention;
• interpretive residue;
• field alteration;
• publication effects;
• memory contamination;
• withdrawal aftereffects;
• delayed burden.

Research bleed-through is present when the study ends but its effects remain active in people, records, systems, or interpretations.

12.5 Community / Social Interfaces

Check:

• rumor residue;
• role fixation;
• identity carryover;
• expectation residue;
• unresolved obligation;
• social pressure;
• narrative recurrence;
• dignity burden.

Community bleed-through must be repaired before return, closure, or reintegration is declared.

12.6 Civilization-Scale Interface

Check:

• collective narrative residue;
• public awareness effects;
• legitimacy residue;
• proxy authority residue;
• fear or fascination loops;
• signal recurrence;
• institutional memory;
• governance capture.

Civilization-scale bleed-through requires high auditability because residue can become public myth, institutional doctrine, governance leverage, or suppressed collective burden.

13. Machine-Readable Metadata

id: "RA-B-005"
legacy_id: "RA-DEBT-04"
title: "Bleed-Through Management"
aliases:
  - "Bleed-Through"
  - "Residue Management"
  - "Cross-Boundary Residue Repair"
  - "Unknown-Domain Residue Cleanup"
family_primary: "Unknown-Domain / Interface Exploration Grammar"
families_secondary:
  - "Specialized Grammar"
  - "Boundary"
  - "Containment"
  - "Hidden Debt"
  - "Memory"
  - "Recurrence"
  - "Damping"
  - "Auditability"
  - "Interface"
  - "Security"
  - "AI Governance"
  - "Reintegration"
  - "First Contact"
  - "Civilizational"
treatment: "Specialized Grammar / Residue and Recurrence Arc"
status: "Canon-Ready"
grammar_cluster: "Unknown-Domain / Interface Exploration Grammar"
sequence_position: 4
previous_arc: "RA-B-004"
next_arc: "RA-B-006"
scope:
  - "Unknown-Domain"
  - "High-Uncertainty"
  - "Interface"
  - "Exploration"
  - "First-Contact"
  - "AI"
  - "Security"
  - "Institutional"
  - "Governance"
  - "Research"
  - "Community"
  - "Civilizational"
  - "Cross-Domain"
u_layers:
  failure_origin:
    - "often U2 boundary layer"
    - "often U3 runtime / execution layer"
    - "often U4 interpretation layer"
    - "often U5 memory / recurrence layer"
    - "often U6 institutional or field layer"
    - "often U7 trajectory layer"
  symptom_visible:
    - "U4 / U5 recurring signal, lingering narrative, memory residue, operator carryover, unexplained recurrence, persistent artifact, or delayed contact effect"
  repair_required:
    - "at or below the layer where residue, memory contamination, recurrence, or boundary leakage persists"
  validation:
    - "U5"
    - "U6"
    - "U7"
operators:
  scaffold: "Σ residue-must-not-become-coupling invariant → Au exposure / residue / recurrence trace → BΣ boundary repair and isolation → FI affected-field and operator feedback → Θ amplification and recurrence attenuation → ℛ cleanup / memory repair / support routing → Π containment reinforcement → Λ residue-resolution gate → Τ bleed-through proof"
  sequence:
    - "Σ"
    - "Au"
    - "BΣ"
    - "FI"
    - "Θ"
    - "ℛ"
    - "Π"
    - "Λ"
    - "Τ"
state_variables:
  primary:
    - "Au"
    - "Au_eff"
    - "H"
    - "H_residue"
    - "H_potential"
    - "O"
    - "BΣ"
    - "K"
    - "σ"
    - "R"
    - "FI"
  secondary:
    - "𝓓"
    - "τ_m"
    - "Φ"
diagnostics:
  - "bleedthrough_risk"
  - "residue_load"
  - "residue_visibility"
  - "cross_boundary_leakage"
  - "boundary_repair_integrity"
  - "memory_contamination"
  - "operator_carryover"
  - "field_carryover"
  - "signal_persistence"
  - "recurrence"
  - "containment_integrity"
  - "quarantine_integrity"
  - "reintegration_capacity"
  - "cleanup_integrity"
  - "delayed_effect_risk"
  - "Φ/O divergence"
gates_required:
  - "Exposure-Trace Gate"
  - "FI-Gate"
  - "HR-Gate"
  - "MS-Gate"
  - "Au-Actuation"
  - "BΣ-Gate"
  - "Containment-Gate"
  - "Memory-Gate"
  - "Recurrence-Gate"
  - "Λ-Gate"
  - "☷ᵢ"
linked_failure_modes:
  - "Bleed-Through Accumulation"
  - "Residue Persistence"
  - "Cross-Boundary Leakage"
  - "Memory Contamination"
  - "Operator Carryover"
  - "Field Carryover"
  - "Delayed Contact Effects"
  - "Containment Failure"
  - "Quarantine Failure"
  - "Contact-to-Coupling Drift"
  - "Unknown-Domain Capture"
  - "Recurrence After Contact"
  - "Silent Persistence"
  - "Cleanup Theater"
  - "Reintegration Failure"
  - "High-Risk Gate Bypass"
linked_restoration_arcs:
  - "RA-A-001"
  - "RA-A-003"
  - "RA-A-004"
  - "RA-A-005"
  - "RA-A-008"
  - "RA-A-010"
  - "RA-A-012"
  - "RA-A-014"
  - "RA-A-020"
  - "RA-A-025"
  - "RA-A-026"
  - "RA-A-039"
  - "RA-A-045"
  - "RA-A-056"
  - "RA-A-059"
  - "RA-A-073"
  - "RA-A-080"
  - "RA-B-001"
  - "RA-B-002"
  - "RA-B-003"
  - "RA-B-004"
  - "RA-B-006"
anti_patterns:
  - "Cleanup Theater"
  - "Evidence Deletion"
  - "Residue-as-Invitation"
  - "Romanticized Carryover"
  - "Field Burden Denial"
  - "Memory Laundering"
  - "Recurrence Harvesting"
  - "Containment Success Narrative"
  - "Reintegration Too Early"
  - "Residue Secrecy"
  - "Boundary Repair by Declaration"
completion_tests:
  - "residue visibility increases"
  - "residue load decreases"
  - "bleed-through risk decreases"
  - "cross-boundary leakage decreases"
  - "boundary repair integrity increases"
  - "memory contamination decreases"
  - "operator carryover decreases"
  - "field carryover decreases"
  - "signal persistence decreases"
  - "recurrence decreases"
  - "containment integrity increases"
  - "quarantine integrity increases"
  - "reintegration capacity increases"
  - "cleanup integrity increases"
  - "delayed effect risk decreases"
  - "residual hidden debt decreases"
  - "potential hidden debt decreases"
  - "effective auditability increases"
  - "boundary integrity increases"
  - "feedback integrity increases"
  - "damping increases"
  - "memory half-life decreases"
  - "Φ/O divergence decreases"
summary: "Bleed-Through Management repairs residue, recurrence, carryover, memory contamination, delayed effects, and cross-boundary leakage after probe, quarantine, or contact by identifying what crossed the boundary, isolating residual effects, preserving auditability, reducing recurrence, restoring boundary integrity, and validating containment over time."

Final Calibration Rule

Bleed-Through Management answers nine questions:

What crossed the boundary after probe, quarantine, contact, or exposure?
Where did the residue originate, and what path did it take?
Is the effect signal, residue, recurrence, contamination, carryover, coupling, or active harm?
What memory, operator, field, system, narrative, identity, or institutional surfaces are contaminated?
How is the residue isolated without deleting audit evidence?
What boundary repair prevents further leakage?
What support, cleanup, memory repair, decoupling, or stabilization route is required?
When is reintegration admissible?
How is cleanup proven over time through residue_load ↓, bleedthrough_risk ↓, cross_boundary_leakage ↓, memory_contamination ↓, recurrence ↓, H_residue ↓, and U7 proof?