# SINGLE METHOD EXCEPTION PROTOCOL (Private -- S3 Multi-Method Orchestrator)

**Scope:** Defines the narrow conditions under which a claim may be answered by a single-discipline invocation. All other paths -- and every "best-fit" / "efficiency" / "obvious-method" argument -- are REJECTED.

## 1. Why this file exists

RAM exists because the Librarian collapsed to one-method-per-question via intent-verb routing dressed up as "best discipline." The multi-method default is the structural cure. This protocol is the ONLY valid bypass. Read it as a closed enumeration: if the case is not in the allowed-trigger list, the answer is "expand the set."

## 2. CLOSED allowed-trigger list

A `SINGLE_METHOD_EXCEPTION` may be filed only when one of the following triggers is factually present and ledger-documented:

1. **T1 -- Zero applicable disciplines.** After baseline-set lookup, fitness-overlay, and debiasing-overlay, only one discipline has any applicable source set AND all other disciplines have verified-zero-retrieval (S1/S2 ledger-backed). Research Auditor is still invoked; "single method" means single SUBSTANTIVE discipline.
2. **T2 -- Matrix-declared singleton.** The matrix explicitly returns size-1 for this claim type AND fitness-overlay does NOT add a second discipline AND debiasing-overlay does NOT trigger. The matrix is engineered NOT to return singletons, making T2 rare.
3. **T3 -- Operator-signed charter exception.** A pre-registered charter-level exception names the method AND the epistemic rationale, signed and recorded in the charter lock. "For efficiency" is NOT a rationale.
4. **T4 -- Inherited exception from upstream CLAIM_TYPE_REVISION.** S5 re-decomposed a returned claim and the sub-claim independently triggers T1 or T2. Each hop is logged.

## 3. REJECTED rationales (CLOSED)

If your justification fits ANY of these, decline the exception:

- "This is the obvious method for this kind of question."
- "Most efficient / fastest / cheapest."
- "Best fit given time constraints."
- "Other methods would not add value."
- "The question is too narrow to warrant multi-method."
- "The operator asked for a quick answer."
- "The other disciplines already agree."
- "The claim is simple / factual / obvious."

The first three are the Librarian's original failure mode returning under new names. The remainder are social-pressure rationales; RAM never yields.

## 4. Required justification fields

A valid exception writes a Search Ledger record with all fields populated:

- `claim_id`
- `trigger_code` -- one of T1, T2, T3, T4 (no other values)
- `trigger_evidence_refs` -- ledger entry IDs proving the trigger
- `method_name` -- the single substantive discipline
- `research_auditor_invoked` -- MUST be true
- `rejected_rationales_confirmed_not_used` -- attestation
- `operator_charter_ref` -- required iff T3
- `upstream_revision_ref` -- required iff T4

## 5. Enforcement

Ledger entries missing any field are REFUSED by the write contract. A size-1 selection without a filed exception halts orchestration for that claim.

## 6. Audit signal

Phase 7 Escape Hatch and Phase 9 eval harness monitor `SINGLE_METHOD_EXCEPTION` stamps. Any stamp using a REJECTED rationale (textual match) triggers a defect report and reopens Phase 1A S3 design.
