1. Research Question

When Flux Signal evaluates systemic rupture and phase-transition risk, should BTC, SPX, and GOLD all be contemporaneously fresh before a new systemic score can be produced?

More specifically, RQ-03 asks whether the Rupture and Phase layers should continue evaluating the system when one or more cross-asset inputs represent older market observations, or whether systemic evaluation should require a complete fresh cross-asset observation set.

RQ-03 is a research question, not a bug classification. Its purpose is to preserve and resolve a semantic ambiguity before changing production behavior.

2. Why Freshness Matters Here

Flux Signal contains several layers with different semantic roles. Asset-level λS readings describe structural market tension for individual assets, while Rupture and Phase attempt to describe stronger cross-asset and systemic conditions.

A systemic reading therefore carries a different claim from an individual BTC, GOLD, or SPX reading. If inputs from different market observation times are combined without an explicit freshness policy, the resulting score may appear to represent a synchronized cross-asset state even though the underlying observations were not produced contemporaneously.

This issue is particularly visible when BTC continues updating while GOLD and SPX are outside their active market windows.

3. Production Evidence — August 21, 2026

At approximately 12:35 UTC on August 21, 2026 (15:35 Türkiye time), the Rupture engine produced the following systemic observation:

Inspection of the corresponding seismograph history shows that the three MSI values available to the systemic calculation did not belong to the same observation time.

4. Reproduction of the Observed MSI Average

The three asset-level MSI observations reproduce the systemic MSI_avg exactly:

(0.0158220428 + 0.0146164171 + 0.0075049073) / 3 = 0.0126477891

The calculated result matches the rupture_history.MSI_avg value recorded for the August 21 systemic evaluation.

This provides direct behavioral evidence that the systemic calculation used the current BTC seismograph value together with older GOLD and SPX values still present in the latest-metric state.

5. What This Evidence Establishes

The August 21 observation supports the following statement:

Flux Signal produced a systemic rupture calculation using cross-asset metric observations from different points in time.

This is classified as Observed production behavior. The numerical relationship is directly visible in the historical Firebase outputs.

The observation is also consistent with the currently available Rupture / Phase implementation sources, where the systemic engines read the latest available metric documents without an explicit cross-asset timestamp-alignment or freshness gate.

6. What This Evidence Does Not Establish

The observation does not by itself demonstrate that:

• the August 21 rupture score was materially incorrect;
• an alert should have been triggered;
• the existing thresholds are incorrectly calibrated;
• the Rupture or Phase formulas themselves are invalid;
• the behavior was necessarily accidental when originally designed;
• the current Library helper source is proven to be byte-for-byte identical to the exact deployed revision responsible for the historical observation.

The evidence establishes a freshness-policy ambiguity. Classification of that ambiguity as a confirmed implementation defect requires a separate design and provenance decision.

7. Relationship to Global Risk Index

The Global Risk Index already applies an explicit freshness-aware coverage model.

Signal observations older than the accepted freshness window are excluded from the Global Risk calculation. The resulting reading then records which assets were actually eligible.

This behavior does not automatically determine the correct Rupture or Phase policy. Global Risk is capable of degrading its coverage semantics explicitly, whereas a systemic rupture or phase-transition reading represents a stronger cross-asset claim.

8. Working Direction

The current working direction is that systemic Rupture and Phase evaluation should require a complete, sufficiently fresh BTC + SPX + GOLD observation set.

Under this model, partial market coverage could remain valid for Global Risk, while insufficient cross-asset freshness would prevent the creation of a new systemic Rupture or Phase score.

Partial data may support a partial market-risk reading. Partial data should not automatically support a new systemic cross-asset claim.

If full fresh coverage is unavailable, the preferred semantic direction is NOT EVALUATED rather than a newly generated systemic score or an implicit interpretation of NO SYSTEMIC RISK.

This is a working research direction only. It is not yet recorded as implemented production behavior.

9. Phase Transition Dependency

Phase Transition is downstream of the Rupture layer. The phase score incorporates the current rupture score together with wave behavior, rupture-score gradient, and regime pressure.

For this reason, a freshness ambiguity in the Rupture layer can propagate into the Phase layer even when the Phase calculation itself is mathematically functioning as implemented.

RQ-03 therefore treats Rupture and Phase freshness as a connected policy problem rather than two unrelated implementation questions.

10. Alert-Lifecycle Implication

A future freshness policy must also define what happens when a systemic alert is already active and full fresh cross-asset coverage temporarily disappears.

Automatically resolving an alert simply because fresh confirmation is unavailable would conflate two different statements:

“Fresh evidence shows that the condition has resolved” is not the same as “Fresh evidence is currently unavailable.”

A possible future lifecycle state such as AWAITING_FRESH_COVERAGE or UNCONFIRMED remains under consideration. No lifecycle change is adopted by this research record.

11. Open Decisions

• What maximum age should qualify an input as fresh for systemic evaluation?
• Should the existing Global Risk freshness window also apply to Rupture and Phase, or should systemic freshness have its own independently justified threshold?
• Must signals_current, seismograph_metrics, and wave_metrics independently satisfy the same freshness requirement?
• How closely aligned must BTC, SPX, and GOLD timestamps be within one systemic observation?
• Should the last valid full-coverage systemic score remain visible during unavailable periods, and if so, how should its age be communicated?
• How should an already-active systemic alert behave while full fresh coverage is temporarily unavailable?
• Can the exact production deployment revision responsible for the observed August 21 behavior be independently reconstructed and verified?

12. Evidence Classification

Implemented ≠ Observed ≠ Internally Supported ≠ Externally Validated.

13. Provenance Boundary

The Firebase historical records provide direct evidence of what the production system emitted during the observed window.

Current Library source provides implementation evidence that is consistent with the behavior, but Library helper source alone is not treated as proof of the exact historical Cloud Functions deployment revision.

Deployment provenance should therefore remain a separate verification step if RQ-03 later requires an exact historical source reconstruction.

15. Evidence Sources

• seismograph_history — latest 72 documents reviewed on August 21, 2026.
• rupture_history — latest 72 documents reviewed on August 21, 2026.
• phase_transition_history — latest 72 documents reviewed on August 21, 2026.
• BTC, GOLD, and SPX signals_history and lambdaS_runs observation packages reviewed during the same investigation.
• Current Library implementation sources for the Rupture, Phase Transition, Global Risk, and alert layers.