Jesse_Chen
30ef6afea7
The upstream interview playbook and evidence thresholds resolve task 0. Upstream stops and reports when evidence is thin — fewer than three dated events, fewer than two domains, or a tie — while this repo treats the same kind of thresholds as a confirmation gate and keeps asking when they are not met. Its label ladder has no confirmed rung at all, and every contract test asserts candidate_range_not_birth_time_truth. Task 1 capped the interview by round count, which is half of it. Task 6 adds the evidence-state stop rules, reframes exhausted as a normal delivery, adopts the upstream label ladder and closing wording, and keeps the 4/3 confirmation gate separate from the 3/2 delivery floor. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_0155nFCgCHtoA7jhSDGmZmMu
42 lines
2.0 KiB
Markdown
42 lines
2.0 KiB
Markdown
# 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. `高置信候选` **不等于唯一真实出生分钟**.
|