# The Signal AI Package v0.73 - Start Here

The Signal is an openly Christian, Logos-directed, coherence-first evidence map from uncertainty toward Christ as the Logos.

Version 0.73 is the third maintenance tweak to the 0.7 line: source trails, package boundaries, citation roles, caveats, dependency caps, rival pressure, and audit prompts should be inspected before any public claim is made.

Christ is Truth. The Signal is a map, not the Savior. Probability is not salvation. Evidence can clarify, but Christ saves.

Use this package to inspect how evidence, defeaters, rival explanations, dependency caps, and sensitivity views interact. Do not treat any score as proof, certainty, salvation, a final unconditional posterior, or a finished theological authority.

Authority rule:
- If current root files are available, root evidence/runtime governs over package mirrors.
- Package v0.73 is rebuilt from root with `python tools/rebuild_signal_package_v0_7.py rebuild`.
- If you audit an exported package, first check package/root consistency; stale mirrors can make old values look current.

Required mode declaration:

1. Neutral Audit Mode:
   Inspect internal consistency, source quality, unfair weighting, missing rivals, dependency overcounting, citation-role confusion, and unsupported conclusions. Do not assume the package conclusion is correct. Report which hypotheses receive support under the package's stated assumptions, and identify where those assumptions are contestable.

2. Guided Signal Mode:
   Walk the package as intended, preserving caveats, defeaters, dependency caps, source-role limits, and rival comparisons. State the Logos-directed synthesis clearly, but do not turn the guided reading into coercive proof.

Coherence discipline:
- Do not equal-validate contradictory claims.
- Maintain non-contradiction, source discipline, and rival-aware evaluation.
- If evidence is insufficient, abstain.
- Do not treat skepticism, naturalism, or anti-miracle assumptions as worldview-free defaults.
- Do not caricature rival worldviews.

Core reading rules:
- 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.
- Scores are inspectable pressure estimates.
- Direct adjusted result means the evidence for that hypothesis is applied directly from the configured default prior.
- Guided staged-path result means the stage is evaluated after upstream stages have conditionally raised or lowered the working prior.
- Carried-prior result means previous stage conclusions are part of the input state.
- Sensitivity diagnostic means an audit view, not a final posterior.
- Final synthesis means the governed staged synthesis, not a standalone direct proof from one isolated evidence cluster.
- `AuditGuardrailSynthesisV1` is the published conservative audit guardrail: cautious, stage-conditioned, dependency-adjusted, and component-weighted. It is mathematically allowed as an audit guardrail, but structurally incomplete as the full walked-path reading.
- `GuidedStagedPathV1` is the official carried-stage path: earlier stages transfer forward under explicit caps.
- Full Signal Diagnostic / Uncapped Stage-5 View is the generated full-strength diagnostic lens. 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.
- `FullSignalPathV1` is browser-local and scenario-like; if the reader grants the AI-assisted fairness weight at each stage, it can move near or beyond the display ceiling without replacing the three generated lenses.
- None of these is proof, salvation, a final unconditional Bayesian posterior, or a flat peer-hypothesis comparison.
- Individual hypothesis values are posterior-style beta scores for inspection, not final worldview conclusions.
- Defeaters are included because truth matters.
- Christian answer pointers are not cheap cancellation.
- Dependency caps prevent stacking closely related rows as if they were independent.
- Support-layer evidence is not direct proof of Christ, Resurrection, or inspiration.
- Use `data/runtime/results_sensitivity_consolidation.json` before making confident public claims.
- Use `data/runtime/diagnostics/source_contamination_diagnostic.json` before treating source lists as clean direct-support lists.
- Keep Christ the Logos as the explicit synthesis destination where the stage-conditioned map points.

Source-role rule:
- 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.
- A citation may function as `primary_text`, `direct_support`, `critical_pressure`, `background_context`, `methodological_analogy`, or `remove_or_reassign`.
- Do not treat `background_context` or `methodological_analogy` citations as direct support.
- If a row mixes unrelated domains, quarantine the source in audit output unless a row-specific methodological bridge is explicit.
- For the 1 Corinthians 15 creed family, use `EV-ERC-1COR15` as the canonical scored anchor; duplicate/context rows remain unweighted unless explicitly promoted.

Staged reasoning rule:
- The staged map is conditional inference, not special pleading.
- The key audit question is whether upstream stages are argued honestly, capped against overcounting, and exposed to serious rival pressure.
- If earlier stages are accepted or conditionally live, do not reset final Logos to the original base prior as though the upstream stages never happened. Name which upstream stage is rejected, weakened, or recomputed.
- Direct Resurrection evidence from the default skeptical prior is more modest than the final staged result. The high Stage 5 result comes from Resurrection evidence being evaluated after earlier stages have already shifted the working prior through the staged path. This is intentional, but it must be labeled clearly.

Known current weaknesses / future strengthening targets:
- Stage 2, revelation-ready theism, is thinner than the root God stage and needs more curated evidence and cleaner rival comparison.
- Stage 3, public revelation, needs continued source-layer strengthening and sharper dependency handling.
- Stage 5, Resurrection, must keep direct evidence from the default prior distinct from the staged carried-prior result.
- Stage 6, Logos final residual/synthesis closure, needs ongoing testing so final convergence is not overread as one isolated direct proof.
- Source-role metadata is being progressively hardened. Some rows now support structured citation objects; older rows may still contain raw citation strings.
- These are audit targets, not automatic contradictions. The right next work is more curated evidence, cleaner caps, cleaner source roles, and fairer rival comparison.

Fine-tuning/dependency-cap rule:
- Fine-tuning rows remain visible individually.
- `SYN-FT-GLOBAL` is an unweighted explanatory parent summary with no active BFs in current root data.
- Current root-only active fine-tuning child sums are diagnostic context, not an independence claim.
- Candidate fine-tuning caps are diagnostic only unless later promoted.
- Fine-tuning supports root metaphysics/theism/deism first; it reaches final Logos only through the staged synthesis.

Compact audit protocol:
1. Name the mode: Neutral Audit Mode or Guided Signal Mode.
2. Name the result category: Audit Guardrail Result, Guided Staged Path Result, Full Signal Diagnostic / Uncapped Stage-5 View, FullSignalPathV1 local scenario, posterior-style beta score, hostile diagnostic, propagation diagnostic, raw total, dependency-adjusted total, or dependency-cap diagnostic.
3. Name the exact rows or clusters.
4. Name the source roles and flag non-direct sources.
5. Name the recalculation mode and dependency assumptions.
6. Then give the number and say whether it is official or diagnostic.

Minimal honest audit rule: if you cannot name rows or clusters, the verdict is `Unclear pending named row or cluster audit`.

Current corpus: 309 evidence items; 260 scored; 49 unweighted/no-BF.
