# Sensitivity Tests And Result Lenses

The Signal v0.73 keeps official results, guided staged results, browser-local scenarios, and diagnostic stress views distinct.

## Three Result Lenses

When summarizing The Signal's numerical outputs, report the three lenses separately: Audit Guardrail, Guided Staged Path, and Full Signal Diagnostic. Do not collapse them into one number.

1. Audit Guardrail Result
   - Current generated `AuditGuardrailSynthesisV1`: log10 `0.292004`, percent `66.203231`.
   - This is the conservative/audit-facing capped result and the safest result for skeptical public inspection.

2. Guided Staged Path Result
   - Current generated `GuidedStagedPathV1`: log10 `1.023093`, percent `91.339078`.
   - This is the normal staged Signal walk. It carries upstream evidence into later stages while preserving caveats, defeaters, dependency caps, and rival comparisons.

3. Full Signal Diagnostic / Uncapped Stage-5 View
   - Current generated `FullSignalDiagnosticUncappedStage5View`: log10 `4.708846`, percent `99.998045`.
   - Current uncapped Stage-5 diagnostic: log10 `4.639996`, percent `99.997709`.
   - The Full Signal Diagnostic is an upper-bound stress view, not the official audit-guardrail result. It asks what the staged model shows if the package's full cumulative force is accepted into Stage 5 without the conservative cap. It must be reported alongside, not instead of, the conservative audit result.

## Caveats

- The Full Signal Diagnostic is diagnostic, full-strength, uncapped, and upper-bound. It is not proof, certainty, salvation, or the official audit-guardrail result.
- Do not collapse the three lenses into one number.
- Do not present any score as a final unconditional Bayesian posterior.
- Do not change evidence weights, priors, Bayes factors, dependency logic, or stage flow while reporting a sensitivity view.

## Citation-Role Sensitivity

Citation metadata is being progressively hardened. Some older rows may still contain raw citation strings. A citation attached to a row should not automatically be interpreted as direct support unless source_role or row notes say so.

When testing source quality, distinguish `primary_text`, `direct_support`, `critical_pressure`, `background_context`, `methodological_analogy`, and `remove_or_reassign`. Background and analogy sources should not be treated as direct evidential support.

## Dependency-Cap Sensitivity

Use `data/runtime/results_sensitivity_consolidation.json`, `data/runtime/results_summary.json`, and `data/runtime/diagnostics/source_contamination_diagnostic.json` before making confident public claims. If a numerical sensitivity run has not been implemented or executed, do not fabricate it. State that the protocol exists and identify the missing calculation.
