INV-071 — Wisdom Requires Timing and Scale

1. Definition

The right pattern at the wrong time, scale, layer, or readiness level becomes incoherent.

Wisdom is not merely knowing a true pattern.

Wisdom is knowing:

when
where
how far
for whom
at what scale
at what layer
under what capacity
under what timing
under what boundary conditions
when not to apply it

A principle, tool, intervention, truth, repair, archetype, policy, technology, strategy, or symbolic reading may be structurally valid in one context and incoherent in another.

Therefore:

Wisdom requires timing and scale.

A true insight applied too early can overload the system.

A correct intervention applied at the wrong layer can miss the failure origin.

A coherent pattern scaled too quickly can amplify hidden debt.

A valid truth spoken without container can collapse capacity.

A needed repair done out of sequence can create new harm.

Wisdom is pattern recognition plus timing, scale, layer, and capacity alignment.

2. Purpose

This invariant prevents UTS from confusing correctness with wise application.

A system may know a real pattern, true principle, valid diagnosis, useful intervention, strong archetype, accurate critique, or powerful technology.

But correctness alone does not make application coherent.

The false assumption is:

If the pattern is true, applying it is coherent.

The UTS correction is:

Truth requires timing, scale, layer, and readiness to become wise action.

This invariant protects against:

premature truth
premature repair
premature scaling
premature disclosure
premature reintegration
premature intervention
premature automation
premature archetype assignment
premature governance action
premature biological challenge

It also protects against the opposite error:

delayed truth
delayed repair
delayed boundary action
delayed containment
delayed transition
delayed supersession

Wisdom is not delay by default.

Wisdom is timing coherence.

3. Constraint Statement

Canonical Form

Wisdom requires timing and scale.

Expanded Form

A pattern, principle, truth, intervention, technology, archetype, policy,
repair action, coupling, or governance decision is coherent only when its
application is matched to the right timing, scale, U-layer, capacity,
boundary condition, and readiness state.

Minimal Expression

Right pattern, wrong timing = incoherence.

Timing Form

A true thing can be mistimed.

Scale Form

A valid pattern at one scale may fail at another.

U-Layer Form

A correct repair at the wrong layer creates hidden debt.

Restoration Form

Repair must be sequenced according to capacity and failure origin.

AI Governance Form

AI capability must be deployed only when governance, appeal, audit, and restoration capacity are ready at the relevant scale.

Biological Form

Adaptive challenge must match current reserve, timing, and tolerance.

CMS / Symbolic Form

Symbolic truth must be delivered at the scale and timing the field can integrate.

4. Structural Logic

Wisdom integrates multiple dimensions:

pattern recognition
timing
scale
layer
capacity
boundary
trajectory
readiness
consequence radius
restoration pathway

A system can fail by applying a correct pattern into the wrong coordinates.

The incoherent sequence:

valid pattern identified
        ↓
timing / scale / layer not checked
        ↓
application proceeds
        ↓
capacity mismatch appears
        ↓
boundaries strain
        ↓
hidden debt accumulates
        ↓
pattern is blamed or rejected

The coherent sequence:

valid pattern identified
        ↓
timing checked
        ↓
scale checked
        ↓
U-layer localized
        ↓
capacity assessed
        ↓
boundary conditions clarified
        ↓
restoration pathway prepared
        ↓
application staged
        ↓
time validates outcome

Core insight:

Wisdom is not only pattern accuracy.
Wisdom is application accuracy.

A principle can be true and still misapplied.

A repair can be necessary and still premature.

A technology can be powerful and still not yet admissible.

A truth can be real and still require sequencing.

5. State-Vector Impact

Protected State Variables

O   — coherence
K   — compatibility
R   — restoration capacity
BΣ  — boundary integrity
Au  — auditability
µᵢ  — meaning / agent integrity
H   — hidden debt

Primary Risk Variables

ι   — inversion when correctness is mistaken for admissibility
ε   — visible failure, overload, backlash, rupture, recurrence, misfire
Φ   — accuracy, intensity, usefulness, speed, power, novelty, symbolic resonance, capability proxy

Healthy Wisdom Pattern

pattern recognized
timing aligned
scale aligned
U-layer matched
capacity sufficient
boundaries preserved
R available
H contained
O↑

Violation Pattern

pattern valid
timing wrong
scale wrong
layer wrong
capacity insufficient
BΣ strained
R overloaded
H↑
ι↑
O↓

Correctness-Admissibility Inversion

pattern truth↑
admissibility check↓
application forced
H↑
ι↑

The key inversion:

correct is mistaken for ready.

Wisdom Requirement

Before application, check:

Is it true enough?
Is it the right layer?
Is now the right time?
Is this the right scale?
Is capacity sufficient?
Are boundaries intact?
Can repair occur if wrong?
Can affected nodes receive and respond?

6. U-Layer Localization

Primary Layer

U5 — Coordination / Time

Wisdom is strongly temporal. It governs sequencing, delay, urgency, pacing, and time validation.

Scaling Layer

Cross-layer / U-scale relation

Wisdom requires translating a pattern across scale without flattening it.

Classification Layer

U4 — Classification / Metrics

A pattern may be classified correctly but applied incorrectly.

Boundary Layer

U2 — Configuration / Boundaries

Timing and scale failures often violate scope, consent, readiness, or interface boundaries.

Execution Layer

U3 — Execution

Wisdom becomes consequential when a pattern is acted upon.

Resource Layer

U1 — Power / Budgets

Capacity determines whether the system can absorb the action.

Coherence Field Layer

U6 — Coherence Field

Wisdom preserves meaning, trust, legitimacy, and field coherence by matching application to readiness.

Memory Layer

U7 — Memory / Recurrence

Wisdom learns from recurrence: when the same pattern fails repeatedly, timing or scale may be wrong.

Environment Layer

U8 — Environment / Forcing

External pressure can force premature action, premature disclosure, premature scaling, or delayed repair.

Common Failure Pattern

U4 correct classification
        ↓
U5 timing skipped
        ↓
U1 capacity insufficient
        ↓
U2 boundaries strained
        ↓
U3 action misfires
        ↓
U6 trust / meaning declines
        ↓
U7 recurrence teaches resistance
        ↓
H↑

Common Misdiagnosis

Wisdom failure is often misdiagnosed as:

• the principle was wrong
• the truth was wrong
• the person resisted
• the system was immature
• poor communication
• bad implementation
• insufficient effort
• lack of courage
• lack of clarity
• lack of belief
• unlucky timing only
• unavoidable backlash

The deeper issue may be:

The pattern was applied at the wrong time, scale, layer, or capacity state.

7. Violation Signatures

7.1 True Pattern, Wrong Timing

A valid truth, diagnosis, or intervention is delivered before the system can integrate it.

truth↑
capacity↓
integration failure↑

7.2 Correct Repair, Wrong Layer

The repair targets the visible symptom layer instead of the origin layer.

repair effort↑
origin unchanged
H↑

This links directly to repair-locality invariants.

7.3 Valid Principle, Wrong Scale

A principle valid at one scale is applied mechanically at another scale.

principle validity↑
scale translation↓
O↓

Example:

individual boundary logic applied directly to institutional governance

without translation.

7.4 Technology Deployed Before Governance

A tool or AI capability is released before audit, appeal, rollback, and restoration systems are ready.

capability↑
governance capacity↓
H↑

7.5 Disclosure Without Container

Truth is exposed without support, sequencing, or repair pathway.

truth exposure↑
capacity / R↓
field destabilization↑

Truth remains important, but container matters.

7.6 Delay Becomes Avoidance

The system invokes timing to avoid necessary action.

delay↑
repair↓
H↑

Wisdom is not endless postponement.

7.7 Archetype Activated at Wrong Moment

A system invokes Protector when Witness is needed, Judge when Healer is needed, or Visionary when Builder is needed.

archetype intensity↑
context mismatch↑
O↓

7.8 Biological Challenge Too Early

Training, exposure, diet change, medication, detox, or stress challenge is introduced before reserve and tolerance are restored.

adaptive challenge↑
reserve↓
recurrence↑

7.9 Governance Action Before Truth Reception

An institution acts before affected-node truth, causality, or responsibility gradient is mapped.

authority action↑
truth reception↓
legitimacy debt↑

7.10 Scaling Before Validation

A process is expanded before time, recurrence, repair capacity, and affected-node truth validate it.

scale↑
validation↓
H↑↑

8. Related Failure Modes

Primary related failure modes:

• Wisdom Timing Failure
• Correct Pattern / Wrong Timing
• Correct Repair / Wrong Layer
• Scale Translation Failure
• Premature Disclosure
• Premature Intervention
• Premature Scaling
• Premature AI Deployment
• Premature Reintegration
• Delayed Repair
• Avoidance Framed as Wisdom
• Capacity Mismatch
• Readiness Misread
• Archetype Timing Failure
• Technology-Governance Gap
• Truth Without Container
• Biological Over-Challenge
• Governance Action Before Truth
• Principle Misapplication
• Hidden Debt Accumulation
• Restoration Bypass
• Meaning Collapse
• Legitimacy Debt

9. Related Restoration Arcs

Primary restoration arcs:

• Timing Recalibration
• Scale Re-Translation
• U-Layer Re-Localization
• Capacity Assessment
• Staged Application
• Paced Integration
• Restoration Sequencing
• Truth Container Creation
• Boundary Reconstitution
• Delayed Action Review
• Premature Action Repair
• AI Deployment Re-Sequencing
• Biological Load Recalibration
• Archetype Role Reassignment
• Governance Truth Reception
• Affected-Node Capacity Restoration
• Recurrence Review
• Temporal Validation
• Meaning Reintegration
• Canon Context Repair

Restoration Requirement

Misapplied wisdom must be repaired by recalibrating timing, scale, and layer.

Minimal sequence:

Identify applied pattern
        ↓
Determine intended function
        ↓
Assess timing, scale, layer, and capacity mismatch
        ↓
Repair burden caused by misapplication
        ↓
Re-sequence application
        ↓
Adjust scale or scope
        ↓
Restore boundary and affected-node truth
        ↓
Validate over time

10. Domain Expressions

AI

AI systems often fail wisdom through premature deployment or overbroad application.

Examples:

model capability exists
        ↓
tool is deployed broadly
        ↓
governance and repair are not ready

AI wisdom requires asking:

Is the model capable?
Is the context compatible?
Is the deployment scale appropriate?
Is appeal ready?
Is rollback ready?
Is memory governed?
Is affected-node truth available?
Is restoration capacity sufficient?

Capability is not readiness.

AI Governance

AI governance requires timing and scale discipline.

A governance control may be valid but mistimed:

• too early and it blocks useful emergence
• too late and hidden debt accumulates
• too broad and it over-constrains
• too narrow and it misses systemic risk
• too opaque and it loses legitimacy
• too public without repair and it creates panic
• too private without audit and it creates capture

Governance wisdom means matching intervention to consequence radius, uncertainty, and repair capacity.

Security

Security requires timing and scale.

Examples:

patch before root cause understood
disclose vulnerability before containment
delay disclosure until users remain exposed
overreact to low-risk event
underreact to high-risk signal
lock down system so hard that function collapses

Security wisdom requires:

• containment timing
• disclosure timing
• patch timing
• access restoration timing
• proportional response
• recurrence tracking

Governance / JGL

Governance action must be sequenced.

Examples:

punishment before causality
policy before truth
public statement before evidence
reintegration before repair
emergency power without sunset
reform before implementation capacity

Wisdom in governance requires:

truth
timing
responsibility gradient
capacity
repair
scale
legitimacy validation

A good policy at the wrong time or scale can create legitimacy debt.

Economy

Economic wisdom requires timing and scale in:

growth
investment
automation
labor transition
debt restructuring
market expansion
supply-chain change
rate changes
platform rules

A good innovation deployed too quickly can destroy slack.

A necessary transition without support can export burden.

Economic wisdom asks:

Who bears the timing cost?
Who has capacity?
What hidden debt moves?
What repair capacity exists?

Biology / Medicine

Biological wisdom depends heavily on timing and dose.

Examples:

exercise before recovery
detox before stabilization
medication escalation before tolerance
exposure before reserve
diet change before digestion support
therapy before nervous-system capacity

A biologically valid intervention can become incoherent if applied before the system can absorb it.

Recovery requires:

stabilize
reduce load
restore reserve
then challenge gradually

CMS / Meaning

Meaning wisdom requires timing.

A symbolic truth can be real but mistimed.

Examples:

deep symbolic interpretation before grounding in context
archetype assignment before consent
ritual before repair
unity before differentiation
forgiveness before boundary restoration
truth disclosure before capacity

Meaning must be delivered at the scale and timing the field can integrate.

Principles / Archetypes

Principles require timing and scale.

Examples:

truth without timing becomes weaponized disclosure
justice without sequence becomes punishment
love without boundary becomes fusion
sovereignty without context becomes abandonment
wisdom without action becomes avoidance
protection without humility becomes control

Archetypes also require timing:

Protector when Witness is needed = control
Judge when Healer is needed = punishment
Healer when Boundary is needed = fusion
Visionary when Builder is needed = abstraction

Relationships / Couplings

Relational wisdom requires timing:

hard truth before trust container
repair request before capacity
closeness before boundary repair
commitment before compatibility
space before explanation
explanation before listening
forgiveness before recurrence change

A relational action may be loving in one moment and incoherent in another.

Timing is part of care.

Project / Knowledge Systems

UTS project work requires wisdom in sequencing:

draft before canon
overview before detail
registry before spec sheets
crosswalk before expansion
deduplication before publication
handoff before context overflow
classification before canonization

A correct concept may still be premature if the surrounding module structure is not ready.

Wisdom protects canon integrity.

11. Scaling Behavior

As systems scale, timing and scale errors become more expensive.

Scale increases:

affected-node count
consequence radius
repair burden
coordination complexity
public visibility
recurrence propagation
cascade risk

Therefore:

Scale↑ ⇒ timing precision and scale discipline↑

Scaling Risk Pattern

valid pattern
        ↓
scaled without timing / capacity validation
        ↓
hidden debt multiplies
        ↓
repair becomes harder

Valid Scaling Pattern

pattern validated locally
        ↓
scope staged
        ↓
capacity assessed
        ↓
affected-node truth received
        ↓
restoration capacity scaled
        ↓
time validates broader use

High-Risk Applications

High-risk wisdom failures occur in:

• AI deployment
• governance reform
• security disclosure
• medical intervention
• public truth release
• symbolic initiation
• economic restructuring
• relationship reintegration
• institutional accountability
• canon publication

Relation to INV-068 and INV-069

INV-068 states:

Principles are constraint fields, not beliefs.

INV-069 states:

Archetypes are constraint geometries, not identities.

INV-071 adds:

Even valid principles and archetypes require correct timing, scale, layer, and capacity.

Together:

truthful pattern + wrong application = incoherence.

12. Canonical Examples

Example 1 — Truth Too Early

A person or institution reveals a difficult truth before the receiving system has capacity, context, or repair path.

truth↑
container↓
H↑

Truth was real; timing was incoherent.

Example 2 — AI Tool Deployment

A model can use external tools effectively in tests, but deployment occurs before rollback, audit, and appeal are ready.

capability↑
readiness↓
H↑

Capability was mistaken for wisdom.

Example 3 — Policy Reform Before Logistics

A governance reform is directionally correct but implemented before staff, training, appeal, and affected-node support exist.

reform correctness↑
logistics↓
legitimacy debt↑

Good reform becomes incoherent through timing failure.

Example 4 — Biological Training Load

An athlete increases training because the method is valid, but recovery reserve is low.

valid method
wrong capacity
injury↑

The intervention was not wrong; timing was.

Example 5 — Protector Archetype Misapplied

A person responds with protection when the situation needs listening.

Protector activation↑
Witness need unmet
BΣ strain↑

Archetype timing failed.

Example 6 — Economic Automation

A company automates jobs before transition support, retraining, or community repair exists.

technology Φ↑
support R↓
externalized H↑

Automation may be useful, but deployment timing created debt.

Example 7 — UTS Spec Sheet Before Overview

A detailed spec is written before the registry overview or definitions are stable.

detail↑
architecture readiness↓
canon drift↑

Correct content appears in the wrong sequence.

13. Anti-Patterns

Anti-Pattern 1 — “It Is True, So Say It Now”

Truth still requires timing, container, and repair path.

Anti-Pattern 2 — “It Works Here, So Scale It Everywhere”

Scale translation is required.

Anti-Pattern 3 — “The Tool Works, So Deploy It”

Capability is not readiness.

Anti-Pattern 4 — “The Principle Is Valid, So Apply It Directly”

Principles require context translation.

Anti-Pattern 5 — “Delay Is Always Cowardice”

Delay can be wisdom or avoidance; diagnose which.

Anti-Pattern 6 — “Urgency Overrides Sequence”

Urgency may change sequence but does not erase sequence debt.

Anti-Pattern 7 — “The System Will Adapt”

Adaptation requires capacity.

Anti-Pattern 8 — “A Strong Intervention Solves Faster”

Strong intervention can overload the system.

Anti-Pattern 9 — “The Archetype Fits, So Use It”

Archetype fit still requires timing, capacity, and consent.

Anti-Pattern 10 — “Wisdom Means Waiting”

Wisdom means timing coherence, not indefinite delay.

14. Related Laws

This invariant connects strongly to:

• Wisdom Requires Timing and Scale Law
• Time Validates Law
• Repair Must Match Failure Origin Law
• Restoration Sequencing Law
• Integration Must Be Paced by Capacity Law
• Scale Accelerates Dominant Trajectory Law
• Premature Scaling Law
• Premature Disclosure Law
• Capability Is Not Readiness Law
• Principle Misapplication Law
• Archetype Timing Law
• Hidden Debt Return Law
• Boundary Integrity Law
• Capacity Before Demand Law
• Temporal Compression Law

15. Related Scaling Rules

Related scaling rules:

• Timing Precision Must Scale With Consequence Radius
• Application Scale Must Follow Validation Scale
• Capacity Must Precede Intervention
• Truth Delivery Must Match Integration Capacity
• Technology Deployment Must Follow Governance Readiness
• Policy Reform Must Match Implementation Capacity
• Biological Challenge Must Match Repair Reserve
• Archetype Activation Must Match Context
• Principle Application Must Translate Across Scale
• Repair Sequence Must Match Failure Origin
• Delay Must Be Audited for Avoidance
• Urgency Must Not Erase Restoration Debt
• When Timing Cannot Be Validated, Scope Must Shrink

16. Related Gates

Relevant gates:

• Wisdom Timing Gate
• Scale Translation Gate
• U-Layer Localization Gate
• Capacity Gate
• Integration Capacity Gate
• Restoration Sequencing Gate
• Truth Container Gate
• Boundary Integrity Gate
• Affected-Node Truth Gate
• AI Deployment Readiness Gate
• Governance Logistics Gate
• Biological Reserve Gate
• Archetype Timing Gate
• Principle Application Gate
• Premature Scaling Gate
• Temporal Validation Gate
• High Risk Gate
• Public-Impact Gate
• Canon Readiness Gate

Gate Logic

An application fails the wisdom gate when:

the pattern is valid but timing is wrong

or when:

scale translation is missing

or when:

repair targets the wrong U-layer

or when:

capacity is insufficient for integration

or when:

truth is delivered without container or repair path

or when:

technology is deployed before governance readiness

or when:

delay is used to avoid necessary repair

Gate failure returns:

∅

Meaning:

application is not currently admissible under timing / scale / capacity conditions

The coherent response may be:

delay
stage
reduce scope
translate scale
restore capacity
localize layer
prepare container
sequence repair
validate over time

17. Related Operators

18. Machine-Readable Summary

id: UTS-INV-071
name: Wisdom Requires Timing and Scale
registry: UTS Invariants Registry
category: Wisdom Invariant / Timing Invariant / Scale Invariant / Application Invariant
status: Draft-Integrated
version: 0.1

definition: >
  The right pattern at the wrong time, scale, layer, or readiness level becomes
  incoherent. Wisdom is not merely knowing a true pattern. Wisdom is knowing
  when, where, how far, for whom, at what scale, at what layer, under what
  capacity, under what timing, under what boundary conditions, and when not to
  apply it.

constraint: >
  A pattern, principle, truth, intervention, technology, archetype, policy,
  repair action, coupling, or governance decision is coherent only when its
  application is matched to the right timing, scale, U-layer, capacity,
  boundary condition, and readiness state.

canonical_form:
  - "Wisdom requires timing and scale"
  - "Right pattern, wrong timing equals incoherence"
  - "A true thing can be mistimed"
  - "A valid pattern at one scale may fail at another"
  - "Correct is not the same as ready"
  - "Wisdom is application accuracy, not only pattern accuracy"
  - "Truthful pattern plus wrong application equals incoherence"

protects:
  - timing_coherence
  - scale_translation
  - U_layer_localization
  - capacity_alignment
  - boundary_integrity
  - restoration_sequence
  - affected_node_readiness
  - principle_application
  - archetype_application
  - deployment_readiness

state_vector_effects_when_preserved:
  O: "stable_or_increasing_because_application_matches_context"
  H: "contained_because_timing_scale_and_layer_are_aligned"
  ε: "visible_misfires_are_reduced_or_repaired"
  ι: "decreases_because_correctness_is_not_misread_as_admissibility"
  Au: "preserved_through_explicit_timing_scale_and_layer_checks"
  µᵢ: "preserved_because_meaning_is_integrated_at_appropriate_readiness"
  BΣ: "preserved_because_application_respects_scope_capacity_and_boundaries"
  K: "increases_between_pattern_and_context"
  R: "available_for_error_or_misapplication"
  Φ: "accuracy_intensity_capability_or_symbolic_resonance_not_misread_as_wisdom"

state_vector_effects_when_violated:
  O: "decreases_as_valid_pattern_misapplies"
  H: "increases_through_mistimed_or_misscaled_action"
  ε: "appears_as_overload_backlash_rupture_failure_or_recurrence"
  ι: "increases_when_truth_correctness_or_capability_is_misread_as_readiness"
  Au: "decreases_when_timing_and_scale_checks_are_skipped"
  µᵢ: "degrades_when_meaning_is_forced_before_integration_capacity"
  BΣ: "decreases_when_application_overruns_scope_or_boundary"
  K: "declines_between_pattern_and_context"
  R: "overloaded_by_premature_or_misscaled_action"
  Φ: "may_rise_through_accuracy_power_truth_intensity_or_novelty_while_O_declines"

primary_u_layer: U5
classification_layer: U4
boundary_layer: U2
execution_layer: U3
resource_layer: U1
field_layer: U6
memory_layer: U7
environment_layer: U8

violation_signatures:
  - true_pattern_wrong_timing
  - correct_repair_wrong_layer
  - valid_principle_wrong_scale
  - technology_deployed_before_governance
  - disclosure_without_container
  - delay_becomes_avoidance
  - archetype_activated_at_wrong_moment
  - biological_challenge_too_early
  - governance_action_before_truth_reception
  - scaling_before_validation

related_failure_modes:
  - Wisdom Timing Failure
  - Correct Pattern Wrong Timing
  - Correct Repair Wrong Layer
  - Scale Translation Failure
  - Premature Disclosure
  - Premature Intervention
  - Premature Scaling
  - Premature AI Deployment
  - Premature Reintegration
  - Delayed Repair
  - Avoidance Framed As Wisdom
  - Capacity Mismatch
  - Readiness Misread
  - Archetype Timing Failure
  - Technology Governance Gap
  - Truth Without Container
  - Biological Over Challenge
  - Governance Action Before Truth
  - Principle Misapplication
  - Hidden Debt Accumulation
  - Restoration Bypass
  - Meaning Collapse
  - Legitimacy Debt

related_restoration_arcs:
  - Timing Recalibration
  - Scale Re Translation
  - U Layer Re Localization
  - Capacity Assessment
  - Staged Application
  - Paced Integration
  - Restoration Sequencing
  - Truth Container Creation
  - Boundary Reconstitution
  - Delayed Action Review
  - Premature Action Repair
  - AI Deployment Re Sequencing
  - Biological Load Recalibration
  - Archetype Role Reassignment
  - Governance Truth Reception
  - Affected Node Capacity Restoration
  - Recurrence Review
  - Temporal Validation
  - Meaning Reintegration
  - Canon Context Repair

related_laws:
  - Wisdom Requires Timing And Scale Law
  - Time Validates Law
  - Repair Must Match Failure Origin Law
  - Restoration Sequencing Law
  - Integration Must Be Paced By Capacity Law
  - Scale Accelerates Dominant Trajectory Law
  - Premature Scaling Law
  - Premature Disclosure Law
  - Capability Is Not Readiness Law
  - Principle Misapplication Law
  - Archetype Timing Law
  - Hidden Debt Return Law
  - Boundary Integrity Law
  - Capacity Before Demand Law
  - Temporal Compression Law

related_scaling_rules:
  - Timing Precision Must Scale With Consequence Radius
  - Application Scale Must Follow Validation Scale
  - Capacity Must Precede Intervention
  - Truth Delivery Must Match Integration Capacity
  - Technology Deployment Must Follow Governance Readiness
  - Policy Reform Must Match Implementation Capacity
  - Biological Challenge Must Match Repair Reserve
  - Archetype Activation Must Match Context
  - Principle Application Must Translate Across Scale
  - Repair Sequence Must Match Failure Origin
  - Delay Must Be Audited For Avoidance
  - Urgency Must Not Erase Restoration Debt
  - When Timing Cannot Be Validated Scope Must Shrink

related_gates:
  - Wisdom Timing Gate
  - Scale Translation Gate
  - U Layer Localization Gate
  - Capacity Gate
  - Integration Capacity Gate
  - Restoration Sequencing Gate
  - Truth Container Gate
  - Boundary Integrity Gate
  - Affected Node Truth Gate
  - AI Deployment Readiness Gate
  - Governance Logistics Gate
  - Biological Reserve Gate
  - Archetype Timing Gate
  - Principle Application Gate
  - Premature Scaling Gate
  - Temporal Validation Gate
  - High Risk Gate
  - Public Impact Gate
  - Canon Readiness Gate

19. Compact Canon Statement

UTS-INV-071 states that wisdom requires timing and scale. The right pattern at the wrong time, scale, U-layer, or readiness level becomes incoherent. Wisdom is not merely knowing a true pattern; it is knowing when, where, how far, for whom, at what layer, under what capacity, and when not to apply it. Correctness is not readiness. Capability is not admissibility. Truth requires timing, container, and repair path to become wise action.

20. Short Reference Version

UTS-INV-071 — Wisdom Requires Timing and Scale

Right pattern, wrong timing = incoherence.

Wisdom is not only knowing what is true.
Wisdom is knowing:

when
where
how far
for whom
at what scale
at what layer
under what capacity
under what boundary conditions
when not to apply it

Violation pattern:

pattern valid
timing wrong
scale wrong
layer wrong
capacity insufficient
BΣ strained
R overloaded
H↑
ι↑
O↓

Core rule:

Correct is not the same as ready.
Capability is not admissibility.
Truthful pattern + wrong application = incoherence.