# Sensitivity Tests And Result Lenses

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

## Generated Result Outputs

When summarizing The Signal's numerical outputs, report the named outputs separately: Strict Audit Calculation, Audit Guardrail 75% Ceiling Stress-Test, Guided Staged Path, Guided 90% Carry-Cap Sensitivity, and Full Signal Diagnostic. Do not collapse them into one number.

1. Strict Audit Calculation
   - Current generated `StrictAuditCalculation`: log10 `0.352594`, percent `69.250948`.
   - This is the primary hostile/fair audit lens: skeptical priors, rival-positive pressure, dependency/cluster caps, source limitations, and no arbitrary global confidence ceiling.

2. Audit Guardrail 75% Ceiling Stress-Test
   - Current generated `AuditGuardrail75CeilingStressTest`: log10 `0.283574`, percent `65.767567`.
   - This visibly retains the former 75% global ceiling as a conservative stress-test, not as the main fair audit posterior.

3. Guided Staged Path Result
   - Current generated `GuidedStagedPathV1`: log10 `1.437221`, percent `96.474732`.
   - This is the fair intended staged calculation: dependency-capped, transfer-weighted, rival-aware, and without a final confidence ceiling.

4. Guided 90% Carry-Cap Sensitivity
   - Current generated `Guided90CarryCapSensitivity`: log10 `1.023093`, percent `91.339078`.
   - This preserves the older 90% carried-prior ceiling as an audit comparison, not as the main Guided Staged Path.

5. 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 Strict Audit Calculation or the Audit Guardrail 75% Ceiling Stress-Test. It must be reported as its own diagnostic.

## Audit Cap Sensitivity

- `Strict Audit Calculation`: log10 `0.352594`, percent `69.250948`
- `Audit Guardrail: 75% Ceiling Stress-Test`: log10 `0.283574`, percent `65.767567`
- `85% Audit Cap Sensitivity`: log10 `0.352594`, percent `69.250948`
- `90% Audit Cap Sensitivity`: log10 `0.352594`, percent `69.250948`
- `No Global Audit Ceiling`: log10 `0.352594`, percent `69.250948`

## Caveats

- The Full Signal Diagnostic is diagnostic, full-strength, uncapped, and upper-bound. It is not proof, certainty, salvation, the Strict Audit Calculation, or the 75% guardrail stress-test.
- The Audit Guardrail 75% conditioned-prior ceiling is a conservative stress-test lens. It is not a row-level dependency cap and is not the main fair audit posterior.
- Do not collapse the generated outputs 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.
- A lower result is not automatically fairer, and a higher result is not automatically inflated. Fairness means each constraint corresponds to a real uncertainty, dependency, source limitation, or rival pressure.
- See `docs/result_lens_methodology.md` for result-lens categories.
- See `docs/methodology_strict_logic_defense.md` for the strict logic defense of hypotheses, evidence rows, Bayes factors, dependency caps, transfer weights, confidence ceilings, fairness, and live objections.

## 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`, `data/runtime/diagnostics/source_contamination_diagnostic.json`, and the public `/data/runtime/current_release.json` manifest 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.
