Stop conditions and non-promotion rules

Stop Conditions and Nonpromotion Rules

This file defines when an intervention, biomarker, protocol layer, or protocol change should not be promoted further in this repository.

Its purpose is not to create paralysis.

Its purpose is to prevent false progression.

Aging frameworks often fail not because they never move forward, but because they keep moving forward after the evidence has stopped justifying promotion.

This file exists so the repository has explicit rules for when to stop, when to pause, when not to escalate, and when something should remain where it is.

Core Position

Not every interesting thing should move upward.

Not every signal should become structure. Not every intervention should become protocol. Not every biomarker should gain decision authority. Not every exploratory idea should become support. Not every support intervention should become core.

This repository treats nonpromotion as part of honesty, not as failure.

Sometimes the strongest move is not escalation.

Sometimes the strongest move is refusal.

Why This File Matters

The repository has already established several constraints that make explicit nonpromotion rules necessary:

the measurement problem is structural
function takes precedence when biomarkers conflict with it
the intervention hierarchy is already visible
the protocol section added structure, not false certainty
the risk section has now named biological, interpretive, translational, fit, and structural failure modes

That means the remaining question is practical:

When exactly should the repository say no?

This file answers that question.

What a Stop Condition Is

A stop condition is a point at which continued promotion, escalation, or defense of an intervention or protocol change is no longer justified.

A stop condition may appear because of:

worsening function
rising burden
unacceptable biological risk
unresolved biomarker-function conflict
poor population fit
translation weakness
support inflation
exploratory leakage
structural protocol failure

A stop condition is not always permanent. Sometimes it means stop entirely. Sometimes it means pause. Sometimes it means hold the layer exactly where it is and refuse promotion.

What matters is that the repository names the line.

What a Nonpromotion Rule Is

A nonpromotion rule is a rule that keeps something from moving upward in status even if it remains interesting.

This matters because the repository has multiple categories that can be mis-promoted:

biomarkers
interventions
support elements
combinations
exploratory ideas
protocol layers

A nonpromotion rule does not say something is worthless.

It says it has not earned the next level.

Main Stop Conditions

1. Function Worsens

This is one of the strongest stop conditions in the entire repository.

If an intervention, combination, or protocol change leads to:

lower capacity
worse recovery
more fatigue without adaptation
narrower resilience
worse physical performance
worse cognitive or daily-life function where relevant

then promotion should stop.

No molecular signal outranks this.

If function worsens, the burden of proof shifts strongly against escalation.

2. Recovery Stops Holding

This is a major stop condition, especially in protocols that depend on stress and adaptation.

If the organism is no longer restoring well enough to hold the intervention, promotion should stop.

This may show up as:

rising recovery cost
unstable sleep
accumulated fatigue
worsening tolerance for training or dietary structure
narrower stress resilience

This repository treats recovery failure as a real stop signal, not a small implementation issue.

3. Biomarkers Improve but Function Does Not

This is a stop condition for promotion, even if it is not always a stop condition for continued observation.

If biomarkers move favorably while real organismal function remains unchanged, the repository should not allow that signal alone to justify escalation.

This is one of the clearest nonpromotion rules in the whole framework.

Interesting signal may remain. Promotion does not.

4. Biological Risk Remains Too Poorly Bounded

If an intervention’s core biological risk is still too central and too unresolved, promotion should stop.

This applies especially to interventions where risk is not incidental but structurally tied to the mechanism, such as:

reprogramming-related identity destabilization
telomerase-linked malignant boundary problems
broad regenerative pressure with weak control
other interventions where failure changes the category of biological risk

These interventions may stay active in research evaluation. They do not earn protocol promotion on that basis alone.

5. Translation Remains Too Weak

If the human case remains too narrow, too pilot-scale, too disease-adjacent, too burdensome, or too biomarker-heavy, promotion should stop.

This means:

interesting preclinical signal does not justify support status
early human feasibility does not justify protocol status
disease-context evidence does not automatically justify general-aging use

Translation weakness is a real nonpromotion rule in this repository.

6. Population Fit Is Too Unclear

If the repository cannot answer basic fit questions such as:

who is this for
who is it not for
whether the logic depends on burden or disease context
whether recovery capacity can support it
whether frailty changes the sequence

then promotion should stop.

Unclear fit is not a minor issue. It is one of the fastest ways plausible logic becomes bad protocol logic.

7. Burden Exceeds Likely Value

If the added complexity, management load, recovery cost, measurement load, or implementation friction exceeds likely organismal benefit, promotion should stop.

This is especially important in support and combination logic.

A protocol becomes weaker when it gets harder to hold than to defend.

8. The Foundation Is Not Yet Stable

No upward promotion should happen while the foundation is still weak, vague, or underspecified.

This is one of the strongest structural nonpromotion rules.

If exercise, dietary pattern quality, and sleep and recovery treatment logic are not yet functioning as a real base, the protocol should not escalate into more ambitious layers.

9. Support Stops Supporting

A support intervention should not be promoted or retained if it no longer:

improves fit
reduces a bottleneck
helps the foundation hold
improves resilience or recovery
justifies its burden

Support that becomes decorative should not be promoted. It should usually be removed or kept from entering at all.

10. Exploratory Importance Is Being Mistaken for Readiness

An intervention should not be promoted simply because it is:

scientifically important
mechanistically elegant
a major frontier direction
rhetorically impressive
frequently discussed in longevity discourse

This is one of the clearest nonpromotion rules in the repository.

Scientific importance and protocol readiness are not the same thing.

Main Nonpromotion Rules

Rule 1 | No promotion on biomarker movement alone

A biomarker shift cannot, by itself, move an intervention upward in protocol status.

Rule 2 | No promotion across fit boundaries without new evidence

A signal in one population does not justify promotion into a different population unless the fit logic is strong enough to support that move.

Rule 3 | No promotion while function remains weak or unclear

If the organismal case is weak, the intervention remains below the next threshold even if the molecular case is attractive.

Rule 4 | No promotion that weakens the foundation

Nothing should be promoted if it displaces, destabilizes, or complicates the foundation layer without clear organismal gain.

Rule 5 | No promotion by tone

An intervention does not become stronger because the language around it becomes more confident, more technical, or more polished.

Rule 6 | No promotion through accumulation

A combination does not earn promotion because it contains more individually interesting parts.

Rule 7 | No promotion without a clear reason to move up

Promotion should only happen when the repository can answer:

Why this intervention? Why now? Why this layer? Why this population? Why is the next step more justified than holding where it is?

If those questions are weak, promotion is weak.

Stop Conditions by Protocol Layer

Foundation Layer

Stop escalation above the foundation when:

the foundation is not yet real enough to function as a base
recovery is not holding
function is not improving or stabilizing
added structure would mainly compensate for a weak base instead of strengthen a real one

Support Layer

Stop support-layer promotion when:

the bottleneck is not clear
the support logic is vague
the added burden exceeds benefit
the support intervention does not improve the fit of the foundation
support begins acting like decorative stacking

Exploratory Layer

Stop exploratory promotion when:

human functional evidence remains too weak
biomarker excitement is leading the conversation
risk boundaries remain unresolved
translation remains narrow
the intervention is being promoted mainly because it is ambitious or scientifically important

Exploratory status should remain real, not symbolic.

Stop Conditions by Signal Type

Biomarker signal

Do not promote when:

the biomarker is too weak for the question
the signal is interesting but not individually interpretable
the biomarker conflicts with unchanged or worse function
the signal depends on too much speculative meaning

Functional signal

Do not promote when:

the functional gain is too narrow to matter
the gain is not durable
the gain is offset by worse recovery or higher burden
the function improvement appears compensatory rather than supportive of broader organismal health

Mechanistic signal

Do not promote when:

the mechanism remains elegant but the organismal case is weak
mechanistic language is doing more work than actual outcomes
the mechanism depends on control that remains unrealistic

Nonpromotion Is Not Dismissal

This repository does not use nonpromotion as a way to erase importance.

Something can remain:

scientifically important
worth continued tracking
worthy of research attention
worthy of better measurement
worthy of clearer fit testing

and still not move upward.

This is one of the main reasons the repository can stay ambitious without becoming inflated.

Common Promotion Errors This File Prevents

Error 1 | Early signal inflation

A small or early result is treated like a threshold crossing.

Error 2 | Quiet drift upward

An intervention remains officially exploratory while informally being treated like it belongs in support or core structure.

Error 3 | Foundation compensation

A weak foundation is hidden by adding more advanced layers.

Error 4 | Burden blindness

The protocol keeps adding because each addition sounds defensible in isolation.

Error 5 | Refusal failure

The repository becomes psychologically or rhetorically unable to say no to interesting things.

This file exists to preserve that ability.

Practical Stop Questions

Before any intervention, biomarker, support logic, or combination is promoted, the repository should ask:

What exactly has improved in the organism that matters?
Is the signal strong enough for the layer being proposed?
Is function clearly better, or only more measured?
Is the population fit actually clear?
Is the added burden justified?
What risk is still unresolved?
What is the best reason not to promote this right now?

That last question is especially important.

If the repository cannot state the best reason not to promote something, it may already be drifting into automatic escalation.

Relationship to the Rest of the Repository

This file is directly constrained by:

05_PROTOCOL_DESIGN/04_decision_rules
because entry, escalation, and retention all require explicit refusal logic

05_PROTOCOL_DESIGN/07_risk_boundaries
because stop conditions are the operational form of risk boundaries

05_PROTOCOL_DESIGN/08_sequencing_and_escalation
because sequencing requires real pause points and refusal points

05_PROTOCOL_DESIGN/10_protocol_failure_modes
because protocols fail when they lose the ability not to promote

08_NOTES | Emerging Patterns
especially Pattern 6, Pattern 7, and Pattern 8, because function-first logic, visible intervention hierarchy, and the protocol section’s structural resolutions all depend on explicit nonpromotion rules

Current Assessment

Current repository assessment:

importance to protocol restraint: foundational
importance to anti-drift design: foundational
importance to honest promotion thresholds: foundational
relevance to the whole repository: cross-sectional

Open Questions

Which stop conditions should be treated as absolute across all layers, and which should remain context-dependent?
How long should interesting but weak signal be allowed to remain active before the repository becomes too promotion-tolerant?
Which interventions in the repository are most at risk of quiet upward drift?
How should the repository distinguish pause, hold, de-escalation, and full refusal more precisely as the system grows?

Status

Foundational risk file.

This file should be treated as the part of the repository that preserves the ability to say no, hold position, or refuse escalation, so that structure, restraint, and organismal reality remain stronger than momentum.