0. Registry Classification

1. Purpose

1.1 What This Arc Repairs

U4-to-U6 Validation repairs the validation gap between what a system claims at the meaning, narrative, model, policy, explanation, or symbolic layer and what actually occurs in the field.

It applies when a claim appears coherent at U4 but has not yet been tested against U6 field effects, affected-node verification, downstream consequences, or recurrence.

This arc repairs claim-field mismatch by:

• isolating the claim being made at U4;
• identifying what the claim predicts or implies in the field;
• restoring auditability around the claim and its evidence;
• testing the claim against U6 effects;
• detecting proxy substitution or narrative inversion;
• preserving contradiction as evidence;
• routing failed claims into repair, correction, or withdrawal;
• validating claims over time and recurrence.

U4-to-U6 Validation is the canonical arc for ensuring that representation-layer coherence survives contact with lived, operational, material, relational, institutional, AI, economic, or biological field effects.

1.2 Core Restoration Function

This arc restores field validity by testing whether a `U4` claim, policy, explanation, model, meaning, or declared repair produces coherence at `U6`, survives delay at `U5`, and reduces recurrence at `U7` rather than remaining coherent only inside narrative, symbolic, procedural, or benchmark space.

U4-to-U6 Validation prevents claim coherence from being mistaken for system coherence.

2. Use Conditions

2.1 When to Apply

Use this arc when:

• a claim, explanation, policy, model, doctrine, narrative, or repair statement exists at U4;
• the claim has not been validated through field effects;
• internal logic appears coherent but affected-node experience contradicts it;
• a benchmark, dashboard, report, ritual, policy, or public statement is being treated as proof;
• a repair claim exists but recurrence has not been checked;
• a model or theory explains the system but does not yet predict or improve field behavior;
• a governance process claims legitimacy while field trust remains unstable;
• an AI evaluation claims safety, helpfulness, alignment, or compliance while user-level effects remain unvalidated;
• a meaning system makes symbolic or archetypal claims that bypass auditability;
• field consequences are being treated as secondary to narrative coherence.

Examples:

• an AI safety change improves benchmark scores but worsens real user interaction quality;
• a public policy claims fairness while affected-node outcomes remain asymmetric;
• a security framework claims protection while incidents recur;
• an institution claims accountability through procedure while field trust does not recover;
• a biological or economic interpretation explains symptoms or flows but does not reduce recurrence;
• a spiritual or symbolic claim creates meaning but does not repair boundaries, harm, or hidden debt.

2.2 When Not to Apply

Do not apply this arc when:

• active harm is still cascading and stabilization must occur first;
• the U4 claim has not been clearly stated;
• auditability is too low to test the claim;
• field testing would violate affected-node boundaries;
• the issue is already proven and requires direct origin-layer repair;
• the system refuses to allow contradiction from U6;
• field validation would be used to delay urgent repair;
• the claim is not operational, causal, reparative, predictive, or field-relevant.

U4-to-U6 Validation must not become field-test theater.

2.3 Required Preconditions

Before this arc begins, the following must be true:

If required preconditions fail:

Arc cannot validly begin.

The system must return to truth reconstruction, audit surface expansion, feedback integrity restoration, boundary protection, or claim clarification.

3. Failure / Damage Signature

3.1 Pre-State Across S

3.2 Primary Failure Links

3.3 Origin-Layer Localization

Canon rule:

A U4 claim is not validated until it survives U6 field effects and U7 recurrence.

4. Restoration Objective

4.1 Canonical Objective

Validate or reject a U4 claim by testing it against field effects, delayed consequences, contradiction, affected-node verification, and recurrence.

Formal objective:

U4 claim isolated
Au_claim ↑
FI ↑
U6 field match tested
Φ/O divergence ↓
H not increasing behind claim
τ_m ↓ where repair claim applies
recurrence ↓ where repair claim applies

Expanded objective:

Determine whether the claim describes, repairs, predicts, or governs the real system, or whether it remains coherent only as representation, policy, symbol, model, benchmark, or narrative.

4.2 Non-Goals

This arc does not aim to:

• reject claims because they are abstract;
• reduce symbolic meaning to literalism;
• force all meaning claims into narrow measurement;
• treat field contradiction as automatic disproof without context;
• extract validation labor from affected nodes;
• delay urgent repair;
• let benchmarks certify field truth;
• preserve claims for reputation;
• collapse uncertainty into pass/fail too early;
• use field validation to punish dissenting signals.

5. Operator Sequence

5.1 Minimal Operator Scaffold

Μ claim isolation → Au claim trace → FI field reference → Ξ proxy/narrative inversion detection → Σ validation standard → Θ test gain control → Τ U5/U6/U7 validation → ℛ reroute if failed

Universal grammar alignment:

Σ + Θ → Au + FI → U4 claim isolation → U6 field validation → U7 recurrence check → ℛ routing

U4-to-U6 Validation often routes into Origin-Layer Repair, Feedback Integrity Restoration, Pseudo-Coherence Correction, Truth Reconstruction, or AI Evaluator Restoration.

5.2 Operator Step Table

5.3 Sequence Notes

This arc is claim-gated, field-gated, and uncertainty-gated.

Not every U4 claim must be rejected if it fails initial field validation. Some claims require scope reduction, better timing, better diagnostics, or reinterpretation.

The sequence must distinguish:

valid claim
partially valid claim
mis-scoped claim
premature claim
symbolic claim mistaken for repair
proxy-validated claim
false claim

The following steps cannot be skipped:

claim isolation
claim auditability
field reference definition
proxy inversion check
validation standard
U5 / U6 / U7 testing
reroute rule

If the claim is protected from contradiction, the arc has failed.

6. Restoration Phases

Phase 0 — Isolate the U4 Claim

Purpose: Name what is being asserted, explained, represented, promised, or declared.

Actions:

• state the claim plainly;
• identify whether it is descriptive, predictive, normative, reparative, symbolic, policy-level, or operational;
• identify who or what made the claim;
• identify what authority or evidence supports it;
• identify what it implies should happen in the field.

Validation:

U4 claim explicit
claim type identified
field implication named

Phase 1 — Trace Claim Provenance

Purpose: Make the claim inspectable.

Actions:

• identify source, authority, evidence, assumptions, model, policy, benchmark, or symbolic basis;
• identify where claim support is strong, weak, inferred, or unknown;
• identify whether affected-node signal was included;
• identify hidden exclusions.

Validation:

Au_claim ↑
claim provenance traceable
assumptions and exclusions visible

Phase 2 — Define Field Validation Criteria

Purpose: Establish how the claim would show up at U6.

Actions:

• define expected field effect;
• define affected-node verification path where applicable;
• define coherence-bearing indicators;
• define contradiction signals;
• distinguish Φ from O;
• define what would falsify, limit, or revise the claim.

Validation:

U6 validation criteria named
Φ/O distinction explicit
contradiction pathway open

Phase 3 — Protect Boundaries During Validation

Purpose: Prevent field validation from becoming extraction or forced proof.

Actions:

• preserve refusal rights;
• avoid forced testimony;
• scope data collection;
• avoid public exposure without consent;
• separate affected-node verification from institutional appetite;
• protect sensitive field signals.

Validation:

BΣ stable or ↑
validation does not extract
affected-node signal remains sovereign

Phase 4 — Test Against Field Effects

Purpose: Compare the claim to real outcomes.

Actions:

• compare claim to observed field behavior;
• compare internal report to affected-node experience;
• compare model prediction to downstream effect;
• compare policy statement to lived implementation;
• compare benchmark outcome to real interaction;
• compare symbolic claim to boundary and repair behavior.

Validation:

field match assessed
contradictions classified
O not inferred from Φ alone

Phase 5 — Detect Proxy or Narrative Substitution

Purpose: Identify where the validation is being captured by appearance.

Actions:

• identify benchmark substitution;
• identify compliance theater;
• identify narrative capture;
• identify symbolic completion;
• identify reputation-preserving interpretation;
• identify where failed field signals are dismissed.

Validation:

proxy substitution named
ι decreases
validation reference returns toward O

Phase 6 — Revise, Repair, or Withdraw Claim

Purpose: Route the claim based on validation result.

Actions:

• validate claim if field effects support it;
• scope-limit claim if partially supported;
• revise claim if assumptions fail;
• withdraw claim if contradicted;
• route repair to the layer where mismatch originates;
• preserve record of revision.

Validation:

claim status updated
repair route selected if mismatch remains
revision remains auditable

Phase 7 — Temporal and Recurrence Validation

Purpose: Confirm the claim remains valid over delay and recurrence.

Actions:

• monitor delayed effects;
• monitor recurrence;
• test whether claim holds under perturbation;
• check whether field contradiction returns;
• verify that repair claims reduce recurrence.

Validation:

U5 delay passed
U6 field match persists
U7 recurrence decreases where applicable

7. Gates

7.1 Required Gates

7.2 Gate Failure Rule

If any required gate fails:

∅ — U4-to-U6 Validation cannot validly proceed in that form.

The system must either:

• clarify the claim;
• increase auditability;
• protect boundaries;
• define field criteria;
• restore feedback integrity;
• withdraw or mark the claim provisional;
• route to truth reconstruction or origin-layer repair.

8. Diagnostics

8.1 Required Diagnostic Trends

8.2 Arc-Specific Diagnostic Thresholds

Suggested thresholds:

U4 claim isolated
Au_claim ↑
U6 field criteria defined
Φ/O divergence assessed
field contradiction admitted
claim revised / validated / withdrawn based on evidence
recurrence ↓ where repair claim applies

U4-to-U6 Validation is not complete if:

claim remains vague
field criteria are undefined
benchmark substitutes for field validation
affected-node contradiction is excluded
claim authority exceeds evidence
failed claim remains active
repair claim does not reduce recurrence

9. Anti-Patterns / False Restorations

9.1 Common False Versions

This arc is being simulated, not executed, if:

• the claim is made unfalsifiable;
• benchmark results replace field outcomes;
• policy text replaces implementation reality;
• symbolic resonance replaces repair behavior;
• affected-node contradiction is dismissed as misunderstanding;
• field validation is performed by the claim-maker alone;
• failed claims are reframed without trace;
• the validation window is too short to detect delay;
• public confidence is used as proof;
• the claim is preserved for status after field failure.

9.2 Named Anti-Pattern Links

10. Completion Criteria

10.1 Post-State Signature

10.2 Temporal Proof

U4-to-U6 Validation cannot be declared complete until the claim survives delay, field contradiction, and recurrence.

Template:

Completion requires U4 claim traceable,
U6 field effects matching claim,
H not increasing behind the claim,
and recurrence decreasing across U7 where repair is claimed.

Minimum temporal proof:

• field effects remain consistent after delay;
• contradictions remain admissible;
• claim revisions remain traceable;
• affected-node signals remain protected;
• recurrence declines if the claim is reparative;
• proxy success does not outrank field coherence.

10.3 Completion Statement

Canonical format:

This arc is complete only when the U4 claim has been tested against U6 field effects, survived U5 delay, reduced or clarified recurrence at U7 where applicable, and remains traceable, revisable, and subordinate to real coherence.

11. Cross-Links

11.1 Related Restoration Arcs

11.2 Related Failure Modes

11.3 Related Diagnostics

O, Φ, Φ/O divergence, Au, FI, H, ι, BΣ, 𝓓(t), τ_m, recurrence

11.4 Related Laws / Invariants

INV — U4 claims require U6 validation when field effects are implied.
INV — Coherence cannot be inferred from narrative coherence.
INV — Fitness proxy is not coherence.
INV — Repair claims require recurrence reduction.
LAW — Φ improvement is not O restoration.
LAW — Benchmark success can substitute for field coherence when auditability is low.
LAW — Field validation must outrank dashboard authority.
LAW — Truth claims remain provisional until contradiction and delay are tested.

12. Domain Notes

12.1 AI / Cognitive Infrastructure

Check:

• benchmark score vs user outcome;
• classifier confidence vs actual context fit;
• policy rationale vs interaction effect;
• safety label vs preserved user meaning;
• model explanation vs tool / memory / evaluator path;
• governance claim vs appealability;
• hallucination reduction claim vs field recurrence.

AI U4-to-U6 validation requires testing claims against real interaction patterns, not only internal benchmarks or policy categories.

12.2 Justice / Governance / Legitimacy

Check:

• policy claim vs implementation;
• public apology vs material repair;
• investigation claim vs affected-node verification;
• fairness claim vs consequence symmetry;
• legitimacy claim vs trust restoration;
• accountability claim vs responsibility gradient;
• prevention claim vs recurrence.

JGL U4-to-U6 validation prevents governance language from replacing field justice.

12.3 Biology / Medicine

Conceptual systems mapping only.

U4-to-U6 Validation in biological systems means testing explanatory models against recurrence, timing, perturbation tolerance, boundary integrity, clearance, and field response without collapsing uncertainty into single-cause certainty.

Not diagnosis.

Not treatment.

Not medical advice.

12.4 Economy

Check:

• growth claim vs hidden debt;
• efficiency claim vs burden export;
• market signal vs survival-edge pressure;
• contract fairness vs exit viability;
• productivity claim vs depletion;
• clearance claim vs backlog recurrence.

Economic U4-to-U6 validation tests whether economic narratives produce coherent field outcomes rather than only favorable indicators.

12.5 CMS / Meaning / Archetypes

Check:

• symbolic claim vs boundary behavior;
• sacred language vs auditability;
• archetypal claim vs expression geometry;
• resonance claim vs repair behavior;
• unity claim vs consent and exit;
• spiritual insight vs recurrence reduction.

Meaning systems can preserve non-reductive symbolic depth while still validating field consequences where repair, authority, or coupling is claimed.

13. Machine-Readable Metadata

id: "RA-017"
title: "U4-to-U6 Validation"
aliases:
  - "Field Validation"
family_primary: "Validation"
families_secondary:
  - "Core"
  - "Auditability"
  - "Coherence"
  - "Cybernetics"
  - "Justice / Governance / Legitimacy"
  - "AI Governance"
  - "Security"
  - "CMS"
  - "Economy"
  - "Biology-Medicine"
treatment: "Canon Parent Arc"
status: "Canon-Ready"
scope:
  - "Local"
  - "Relational"
  - "Institutional"
  - "AI"
  - "Biological"
  - "Economic"
  - "Civilizational"
  - "Cross-Domain"
u_layers:
  failure_origin:
    - "usually U4 claim / narrative / model / policy / symbolic layer"
    - "may reveal deeper U1-U3 failure"
    - "may reveal U6 field mismatch"
  symptom_visible:
    - "Φ benchmark / report / compliance / public confidence / symbolic resonance"
  repair_required:
    - "determined by field mismatch"
    - "may require repair below U4"
  validation:
    - "U5"
    - "U6"
    - "U7"
operators:
  scaffold: "Μ claim isolation → Au claim trace → FI field reference → Ξ proxy/narrative inversion detection → Σ validation standard → Θ test gain control → Τ U5/U6/U7 validation → ℛ reroute if failed"
  sequence:
    - "Μ"
    - "Au"
    - "FI"
    - "Ξ"
    - "Σ"
    - "Θ"
    - "Τ"
    - "ℛ"
state_variables:
  primary:
    - "O"
    - "Φ"
    - "Φ/O divergence"
    - "Au"
    - "FI"
  secondary:
    - "H"
    - "ι"
    - "BΣ"
    - "R"
diagnostics:
  - "𝓓(t)"
  - "τ_m"
  - "recurrence"
gates_required:
  - "FI-Gate"
  - "HR-Gate"
  - "MS-Gate"
  - "Au-Actuation"
  - "BΣ-Gate"
  - "Λ-Gate"
  - "☷ᵢ"
linked_failure_modes:
  - "Paper Coherence"
  - "Truth Theater"
  - "Policy Theater"
  - "Compliance Theater"
  - "Benchmark Substitution"
  - "Narrative Capture"
  - "Symbolic Completion"
  - "Spiritual Authority Without Repair"
  - "Procedure Without Field Repair"
  - "Model-to-Field Mismatch"
  - "False Closure"
  - "Pseudo-Coherence"
linked_restoration_arcs:
  - "RA-002"
  - "RA-004"
  - "RA-008"
  - "RA-009"
  - "RA-012"
  - "RA-015"
  - "RA-016"
  - "RA-025"
  - "RA-033"
  - "RA-049"
  - "RA-058"
anti_patterns:
  - "Paper Coherence"
  - "Benchmark Substitution"
  - "Policy Theater"
  - "Symbolic Completion"
  - "Field-Test Theater"
  - "Claim Immunity"
  - "Status-Preserved Claim"
completion_tests:
  - "U4 claim isolated"
  - "Au_claim increases"
  - "U6 field criteria defined"
  - "Φ/O divergence assessed"
  - "field contradiction admitted"
  - "claim revised / validated / withdrawn based on evidence"
  - "recurrence decreases where repair claim applies"
summary: "U4-to-U6 Validation tests whether claims, narratives, policies, models, meanings, explanations, or declared repairs at the representation layer survive contact with field effects, delay, contradiction, and recurrence."

Final Calibration Rule

U4-to-U6 Validation answers six questions:

What hidden debt may be concealed by a coherent claim?
What boundary must be preserved while field validation occurs?
What auditability proves the claim, evidence, and validation path are traceable?
What narrative, policy, benchmark, model, or symbolic claim must remain provisional until field-tested?
What repair trajectory becomes viable if the claim fails or requires revision?
How is the claim proven over time through field effects, contradiction, and recurrence?