LAW-009 — U4 / U6 Truth Law

Open archive search
Archive registry entry

LAW-009 — U4 / U6 Truth Law

U4 claims are provisional classifications until validated at U6 across U5 delay and U7 recurrence.

draftid: LAW-009version: 1.0.0updated: 2026-05-31
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

U4 claims are provisional classifications until validated at U6 across U5 delay and U7 recurrence.

Plain-language version:

A label, metric, category, public claim, safety claim, legal finding, clinical classification, symbolic declaration, or market signal is not truth by itself. It is a classification that must be tested against delayed field effects and recurrence.


1. Formal Definition

The U4 / U6 Truth Law states that claims made at the classification layer remain provisional until validated by field effects, time delay, and recurrence behavior.

U4 includes the layer where systems classify, label, measure, name, score, diagnose, certify, declare, categorize, or claim. U4 is necessary. It helps systems organize information and act. But U4 is not final truth.

A U4 claim gains stronger truth status only when:

  • delayed effects do not contradict it;
  • the larger field behaves coherently after the claim;
  • recurrence weakens or remains bounded;
  • hidden debt does not accumulate beneath the claim;
  • auditability remains sufficient;
  • affected nodes and cross-scale outcomes support the classification.

This law prevents labels, metrics, credentials, categories, symbolic declarations, legal classifications, safety claims, fairness claims, and market signals from replacing field validation.


2. Canonical Form

textScroll
U4 claim + U5/U6/U7 validation ⇒ stronger truth status
U4 claim without validation ⇒ provisional classification

Expanded canonical form:

textScroll
classification becomes stronger only when delayed field effects and recurrence behavior confirm it

Failure expression:

textScroll
U4 claim treated as final truth before U6/U7 validation ⇒ claim capture risk

Related variables:

textScroll
O, H, ε, ι, Au, R, µᵢ, BΣ, K, Φ, 𝓓, τ_m

Where:

TableScroll
VariableMeaning in this law
OCoherence; field validation should preserve or increase it
HHidden debt; rises when claims conceal unresolved incoherence
εObservable error; may appear late after invalid classification
ιInversion index; rises when claims replace truth
AuAuditability; required to test a claim against effects
RRestoration capacity; required when claims fail validation
µᵢMeaning / agent integrity; can be degraded by invalid classification
Boundary integrity; may be violated by identity-binding or coercive claims
KCompatibility / slack / sovereignty; protects against forced classification capture
ΦVisible success proxy; may support a claim but cannot settle it alone
𝓓Damping / ring-down; validates whether the claim stabilizes coherently
τ_mMemory half-life / recurrence tendency; validates whether the claim reduces recurrence

3. Core Mechanism

The U4 / U6 Truth Law unfolds through classification and validation.

A system makes a claim or assigns a category at U4. That classification may be useful, but it remains provisional. Time passes, the claim interacts with the field, and recurrence patterns reveal whether the classification was coherence-aligned.

Validated claim pathway

textScroll
U4 classification
→ U5 delay
→ U6 field effects observed
→ U7 recurrence checked
→ H bounded or reduced
→ O preserved or improved
→ claim gains stronger truth status

Claim capture pathway

textScroll
U4 classification
→ claim treated as final
→ U5 delay bypassed
→ U6 effects ignored
→ U7 recurrence persists
→ H accumulates
→ ι rises
→ claim becomes inversion-supporting

The central discriminator is:

textScroll
Did the classification survive reality after time, field interaction, and recurrence?

4. When This Law Applies

This law applies whenever a system makes, relies on, or enforces a classification before field validation.

U4 claims include:

  • labels;
  • metrics;
  • diagnoses;
  • legal categories;
  • clinical categories;
  • institutional reports;
  • audit ratings;
  • public claims;
  • symbolic claims;
  • archetypal declarations;
  • safety claims;
  • fairness claims;
  • compliance claims;
  • legitimacy claims;
  • market signals;
  • benchmark claims;
  • risk classifications;
  • policy categories;
  • identity-binding claims.

The law applies strongly when:

textScroll
a claim is used to steer action before delayed effects are known

or when:

textScroll
a classification is protected from audit by authority, certainty, urgency, status, or institutional force

Typical domains:

TableScroll
DomainExpression
AI systemsA model is labeled safe, aligned, helpful, fair, or low-risk before field recurrence validation
GovernanceA legal or policy classification is treated as legitimacy without affected-node outcome review
SecurityA system is labeled secure because dashboards show low incident count
Biology / medicineA diagnosis or recovery label is treated as complete truth before recurrence and ring-down are tested
EconomyA market signal is treated as truth rather than a U4 control artifact
InstitutionsCompliance labels replace actual repair, legitimacy, and pathway outcomes
Meaning systemsSymbolic declarations or sacred claims bypass audit and time validation
CultureSocial labels become reality-substitutes before cross-scale effects are known

5. When This Law Does Not Apply

This law should not be used to reject classification.

Classification is necessary for action, coordination, diagnosis, governance, triage, and learning. U4 claims are useful when treated as provisional and updateable.

This law does not critique U4 when:

  • the claim is explicitly provisional;
  • auditability remains open;
  • affected-field outcomes are tracked;
  • recurrence is checked;
  • the classification updates when evidence changes;
  • the claim is scoped and reversible;
  • boundary integrity is preserved;
  • the system preserves uncertainty until validation improves;
  • restoration pathways exist if the claim harms or misclassifies.

False-positive cases:

TableScroll
CaseWhy it is not a violation
A diagnosis is used as a working hypothesisProvisional classification is valid
A risk label triggers further auditU4 is routing into validation
A safety claim is bounded to a tested scopeThe claim is scoped, not universalized
A metric informs investigation but does not settle truthThe metric remains subordinate
A legal category remains appealable and evidence-responsiveClassification remains auditable

Important distinction:

U4 is necessary for action. U4 becomes dangerous when it is treated as final truth without validation.


6. Diagnostic Signature

The basic diagnostic signature is:

textScroll
U4 claim treated as final before U6 field validation

A stronger warning signature:

textScroll
U4 claim strong
Au weak
U5 delay bypassed
U6 effects ignored
U7 recurrence untested
H↑
ι↑

Common indicators:

TableScroll
DiagnosticExpected movementInterpretation
Au↓ / insufficientClaim cannot be properly tested
HHidden debt accumulates beneath invalid classification
ιClaim may be replacing coherence
Ounverified / ↓Coherence is not proven by the claim
τ_munchanged / ↑Recurrence persists despite classification
𝓓flat / ↓Ring-down does not support the claim
εdelayed / displacedObservable error may appear after claim enforcement
Φ↑ / misleadingVisible success may over-support the claim
µᵢMeaning or agent integrity may be harmed by false classification
Boundary integrity may be violated by enforced misclassification

Additional diagnostics:

TableScroll
DiagnosticUse
Classification FidelityTests whether U4 maps cleanly to U6 effects
Effective AuditabilityDetermines whether the claim can be reviewed
Delayed Field EffectShows whether the claim survives real-world interaction
Cross-Scale OutcomeChecks whether local classification exports global hidden debt
RecurrenceTests whether the old pattern persists despite the claim
Ring-DownTests whether classification settles disturbance or sustains ringing
Feedback IntegrityDetermines whether the claim can receive correction
Meaning SymmetryChecks whether meaning claims apply symmetrically and coherently

7. Failure Pattern

If ignored, this law produces claim capture and misclassification debt.

General failure pathway:

textScroll
U4 claim is made
→ claim is treated as final truth
→ auditability narrows
→ delayed effects are ignored
→ affected nodes cannot correct the classification
→ recurrence persists
→ hidden debt accumulates
→ inversion stabilizes around the claim

Common failure modes:

  • U4 Claim Capture — a classification becomes a reality-substitute.
  • Misclassification — incorrect classification creates incoherent action.
  • Metric Substitution — a measurement replaces the thing it measures.
  • Pseudo-Coherence — the claim makes the system appear coherent while hidden debt grows.
  • Pseudo-Restoration — repair is declared through claim rather than validated.
  • False Stability — a stable label masks an incoherent attractor.
  • Hidden Debt Accumulation — invalid claims defer or export unresolved cost.
  • Legitimacy Bypass — authority claims legitimacy without field validation.
  • Signal Reification — a signal is mistaken for the underlying truth.
  • Premature Closure — classification ends inquiry too early.

Compact failure signature:

textScroll
U4 claim + Au↓ + U6 untested + recurrence persists ⇒ claim capture

8. Restoration Implications

Restoration requires returning U4 claims to provisional, auditable status.

The first restoration question is not:

textScroll
What did the label say?

The first restoration question is:

textScroll
What happened in the field after the label was applied?

Restoration priorities:

  1. Identify the U4 claim or classification.
  2. Determine the scope of the claim.
  3. Check whether the claim was treated as final or provisional.
  4. Restore auditability and appeal pathways.
  5. Observe delayed field effects.
  6. Check recurrence and ring-down.
  7. Identify hidden debt generated by misclassification.
  8. Revise, narrow, or retract the claim if field validation fails.
  9. Repair affected nodes, boundaries, and meaning integrity.
  10. Time-validate the corrected classification.

Relevant restoration arcs:

TableScroll
Restoration ArcWhy it applies
Temporal ValidationClaims require delayed proof
Auditability RestorationRequired to reopen review and correction
Recurrence ReductionRequired to test whether the claim changed the pattern
Origin-Layer RepairRequired when the claim covered deeper failure
Restoration Capacity RebuildRequired when misclassification damaged repair pathways
Boundary ReconstitutionRequired when claims violated node or system boundaries
Basin SupersessionRequired when a claim stabilizes an incoherent basin

Minimal restoration sequence:

textScroll
identify U4 claim
→ reopen auditability
→ define validation scope
→ observe U6 effects
→ check U7 recurrence
→ revise classification
→ repair claim-generated debt
→ time-validate

Temporal validation requirement:

textScroll
U4 claim remains scoped and updateable
Au sufficient
U6 effects support claim
τ_m↓ or recurrence bounded
𝓓↑
H↓ or bounded
O preserved or improved
BΣ intact
µᵢ preserved

9. Design Rule

Treat U4 claims as provisional until U6 field effects and U7 recurrence validate them.

Operational design requirements:

  • Mark classifications by validation status.
  • Preserve auditability after claims are made.
  • Separate claim, evidence, effect, and recurrence.
  • Require field validation for high-impact classifications.
  • Keep claim scope narrow until validated.
  • Maintain appeal, revision, and rollback pathways.
  • Track hidden debt created by misclassification.
  • Prevent metrics from becoming final truth.
  • Avoid identity-binding claims without strong information and validation.
  • Time-validate safety, fairness, legitimacy, recovery, and restoration claims.

Avoid:

  • treating a label as reality;
  • treating a metric as truth;
  • treating legal category as coherence;
  • treating safety claim as field proof;
  • treating diagnosis as total identity;
  • treating market signal as truth;
  • treating symbolic declaration as repair;
  • treating compliance as legitimacy;
  • treating benchmark success as alignment;
  • suppressing correction channels after classification.

10. Cross-Scale Expressions

TableScroll
Scale / LayerExpression of the Law
U0 — SubstrateA classification must correspond to substrate reality or material effects
U1 — Energy / capacityClaims must account for actual capacity and burden
U2 — Boundary / interfaceClaims can violate boundaries if imposed without valid scope
U3 — Process / executionWorkflows may enforce classifications before validation
U4 — Classification / claimThe claim is created here and remains provisional
U5 — Time / delayDelay tests whether the claim survives beyond the moment
U6 — Field effectField outcomes validate or contradict the classification
U7 — Recurrence / memoryRecurrence shows whether the claim changed the underlying pattern
U8 — Environment / forcingEnvironmental stress reveals whether the claim generalizes beyond controlled conditions

11. Examples

Example A — AI Safety Label

Scenario:

An AI model is labeled “safe” because it passes internal tests, but deployment reveals repeated user confusion, hidden constraint effects, and edge-case harms.

Law expression:

textScroll
U4 safety label + U6 field mismatch + U7 recurrence ⇒ claim unvalidated

Interpretation:

The safety label was a provisional classification, not final truth.


Example B — Institutional Compliance Claim

Scenario:

An institution claims compliance because procedural metrics improve, but affected users still encounter the same barriers, opacity, and repair failure.

Law expression:

textScroll
U4 compliance claim + recurrence unchanged ⇒ legitimacy unproven

Interpretation:

Compliance classification did not validate coherence or repair.


Example C — Clinical Category

Scenario:

A symptom is classified and treated, but the same pattern returns under similar stress because the deeper system condition remains unresolved.

Law expression:

textScroll
U4 diagnosis + τ_m unchanged ⇒ classification incomplete

Interpretation:

The category may be useful, but it did not fully explain or resolve the recurrence pattern.


Example D — Market Signal

Scenario:

A rising price or valuation is treated as proof of value, while long-term circulation, resilience, labor slack, and hidden debt degrade.

Law expression:

textScroll
U4 market signal + O_global↓ ⇒ signal not truth

Interpretation:

The market signal is a control artifact, not full coherence validation.


Scenario:

A process produces a legal category, but affected-node outcomes, evidence access, repair capacity, and recurrence behavior contradict the legitimacy claim.

Law expression:

textScroll
U4 legal classification + Au↓ + R↓ ⇒ justice coherence unvalidated

Interpretation:

Legal classification alone cannot establish coherence or legitimacy.


Example F — Symbolic Claim

Scenario:

A group declares a value, principle, identity, sacred status, or archetypal role, but behavior under stress repeatedly violates the claim.

Law expression:

textScroll
U4 symbolic claim + U7 recurrence contradiction ⇒ meaning claim unvalidated

Interpretation:

The symbolic claim remains provisional until behavior and recurrence support it.


12. Relationship to Nearby Laws

TableScroll
Related LawRelationship
LAW-002 — Coherence Trajectory LawLAW-002 defines coherence as trajectory; LAW-009 applies this to claims and classifications
LAW-003 — Success Proxy Divergence LawMetrics may become U4 claims that diverge from coherence
LAW-006 — Time Validation LawLAW-006 is the broad time-validation law; LAW-009 applies it specifically to U4 claims
LAW-007 — Ring-Down Truth LawRing-down helps validate or falsify U4 claims
LAW-008 — Recurrence Validation LawRecurrence checks whether a claim changed the underlying pattern
LAW-012 — Error Lag LawInvalid U4 claims may appear successful until observable error emerges late
LAW-036 — Signal Artifact LawSignals and claims are control artifacts, not truth by themselves
LAW-037 — Misclassification LawMisclassification is the main failure risk of invalid U4 claims
LAW-038 — Pattern Recognition Discipline LawPattern recognition may guide U4 classification but cannot replace validation
LAW-054 — Measurement Back-Action LawU4 claims can alter the system they classify
LAW-067 — Temporal Proof LawRestoration claims require temporal proof
LAW-102 — Legitimacy Audit LawLegitimacy claims require audit and field validation
LAW-111 — Meaning Audit LawMeaning and sacred claims are not audit-exempt
LAW-123 — AI U4 Truth Discipline LawAI-specific expression of this law
LAW-146 — Market Signal Control LawEconomy-specific expression: market signals are U4 control inputs, not truth

Aliases folded into this law:

  • U4 / U6 Truth Law
  • Claim Validation Law
  • Classification Provisionality Law
  • U4 Claim Discipline Law
  • Field-Validated Truth Rule

Deduplication note:

This law should remain the root claim-validation law. LAW-123 should remain the AI-specific expression, LAW-146 the market-signal expression, and LAW-111 the meaning-claim expression.


13. Operator Mapping

TableScroll
OperatorRole in this law
ΓProduces classification, labeling, measurement, diagnosis, or claim
ΠDefines validation constraints and claim scope
ΤProvides delay required for claim testing
ΘMaintains uncertainty and prevents premature closure
ΨIncorporates field and observer effects after classification
Repairs harm or debt caused by invalid claims
ΣDefines the boundary and scope of the claim

Coherent operator sequence:

textScroll
Θ → Γ(provisional classification) → Σ(scope) → Π(validation criteria) → Τ(delay) → Ψ(U6 field observation) → U7 recurrence check → update / validate

Inverted operator sequence:

textScroll
Γ(claim as truth) → Σ overextended → Π enforcement → Au↓ → U6 ignored → τ_m persists → H↑ → ι↑

14. Machine-Readable Summary

yamlScroll
id: "LAW-009"
name: "U4 / U6 Truth Law"
type: "law"
status: "draft"
family:
  - "Core Coherence Laws"
summary: "U4 claims are provisional classifications until validated at U6 across U5 delay and U7 recurrence."
canonical_statement: "U4 claims are provisional classifications until validated at U6 across U5 delay and U7 recurrence."
canonical_form: "U4 claim + U5/U6/U7 validation ⇒ stronger truth status; U4 claim without validation ⇒ provisional classification"
failure_form: "U4 claim treated as final truth before U6/U7 validation ⇒ claim capture risk"
variables:
  primary:
    - "Γ"
    - "Au"
    - "O"
    - "H"
    - "τ_m"
  secondary:
    - "ε"
    - "ι"
    - "R"
    - "µᵢ"
    - "BΣ"
    - "K"
    - "Φ"
    - "𝓓"
diagnostics:
  - "Classification Fidelity"
  - "Effective Auditability"
  - "Delayed Field Effect"
  - "Cross-Scale Outcome"
  - "Recurrence"
  - "Ring-Down"
  - "Hidden Debt"
  - "Inversion Index"
  - "Feedback Integrity"
  - "Meaning Symmetry"
failure_modes:
  - "U4 Claim Capture"
  - "Misclassification"
  - "Metric Substitution"
  - "Pseudo-Coherence"
  - "Pseudo-Restoration"
  - "False Stability"
  - "Hidden Debt Accumulation"
  - "Legitimacy Bypass"
  - "Signal Reification"
  - "Premature Closure"
restoration_arcs:
  - "Temporal Validation"
  - "Auditability Restoration"
  - "Recurrence Reduction"
  - "Origin-Layer Repair"
  - "Restoration Capacity Rebuild"
  - "Boundary Reconstitution"
  - "Basin Supersession"
related_laws:
  - "LAW-002"
  - "LAW-003"
  - "LAW-006"
  - "LAW-007"
  - "LAW-008"
  - "LAW-012"
  - "LAW-036"
  - "LAW-037"
  - "LAW-038"
  - "LAW-054"
  - "LAW-067"
  - "LAW-102"
  - "LAW-111"
  - "LAW-123"
  - "LAW-146"
related_invariants:
  - "INV-001"
  - "INV-004"
operator_sequence:
  coherent:
    - "Θ"
    - "Γ"
    - "Σ"
    - "Π"
    - "Τ"
    - "Ψ"
    - "U7 recurrence check"
    - "update / validate"
  inverted:
    - "Γ"
    - "Σ overextended"
    - "Π enforcement"
    - "Au↓"
    - "U6 ignored"
    - "τ_m persists"
    - "H↑"
    - "ι↑"
aliases:
  - "U4 / U6 Truth Law"
  - "Claim Validation Law"
  - "Classification Provisionality Law"
  - "U4 Claim Discipline Law"
  - "Field-Validated Truth Rule"
deduplication_note: "Root claim-validation law. AI, market, legitimacy, and meaning-claim variants should reference this law without duplicating it."
source: "content/archive/laws/technical.md"

15. Compact Card Version

LAW-009 — U4 / U6 Truth Law

U4 claims are provisional classifications until validated at U6 across U5 delay and U7 recurrence.

Plain meaning:

A label, metric, diagnosis, legal category, safety claim, market signal, symbolic claim, or public declaration is not final truth by itself. It must be validated by delayed field effects and recurrence behavior.

Canonical form:

textScroll
U4 claim + U5/U6/U7 validation ⇒ stronger truth status
U4 claim without validation ⇒ provisional classification

Primary variables:

Γ, Au, O, H, τ_m, 𝓓, ε, ι, R, µᵢ, , K, Φ

Diagnostic signature:

A classification is treated as final before field effects, recurrence, ring-down, hidden debt, and affected-node outcomes are known.

Failure risk:

U4 claim capture, misclassification, metric substitution, pseudo-coherence, hidden debt accumulation, legitimacy bypass, signal reification.

Restoration priority:

Return claims to provisional status, restore auditability, observe U6 field effects, check U7 recurrence, revise classifications, and repair claim-generated debt.