# Evidence Thresholds

## Labels

- `blocked`: required input, route, or event evidence is missing.
- `user_history_verification_required`: dates are too sparse or imprecise.
- `parameter_sensitive`: small changes in the candidate grid materially alter the lead.
- `manual_pattern_consensus`: standalone conversation evidence points to one interval, but no external calculator/audit was executed.
- `single_adapter_support`: one user-supplied adapter supports the leading interval.
- `multi_adapter_consensus`: multiple executed adapters support the same interval; this is still not birth-time truth.

## Standalone Cap

In `standalone_core`, the highest allowed label is `manual_pattern_consensus`.
Never label `高置信候选` unless the current user actually provided and executed additional audit adapters.

## Minimum Standalone Gate

To move beyond `blocked`, require all of the following:

- one valid route: `range`, `block`, or `unknown`
- at least three dated events
- at least two domains
- no unresolved tie for first place
- the explicit boundary `不等于唯一真实出生分钟`

Use `medium` only when there are at least five dated events across at least two domains and the lead interval is clearly ahead.
Use `low` when the evidence points somewhere but remains shallow or fragile.

## Optional Enhanced Gate

Use `高置信候选` only when all are visible and actually executed in the current user's environment:

- at least five dated events across at least two domains
- a clear leading interval without a material tie
- adapter status table with raw-result references
- if used, separate visibility for `Vimshottari + Narayana`
- if used, separate visibility for `Functional Benefic/Malefic`, relevant vargas, MEVG, Real Case Calibration, and holdout
- no decisive conflict from any executed adapter

Any blocked, conflicting, or missing raw-evidence item caps the output at `manual_pattern_consensus`, `medium`, `low`, `parameter_sensitive`, or `blocked` as appropriate. `高置信候选` **不等于唯一真实出生分钟**.