recalllisted

# Recall & context — priming **Canonical spec:** `docs/domains/recall.md` — read it for the full pipeline order, all invariants, key files, and gotchas. Terms of record: `UBIQUITOUS_LANGUAGE.md` § Retrieval & context loading. Design rationale: `docs/specs/CoreSpec.md`. Two ranked surfaces, deliberately not unified: **Recall** (hybrid query → fused → policy → budgeted → cached) and **Context** (L0 identity + L1 dense-packed one-liners, <600 tokens). **writepath** defines trust; this domain only multiplies by it. ## Core invariants (get these right) - **`RecallScoring.Fuse` is the only home of the ranking math, and production policy stays outside it** — trust, ROI, layer de-boost, and quarantine are applied after `Fuse` because the benchmark calls `Fuse` directly. - **Every field that changes the result set belongs in `RecallCache.ComputeKey`** — including the rounded alpha bucket and *both expansion flags*. A missing filter serves another query's cached results; this has bitten three times. - **Resolve alpha before `TryGet`** (it's part of the key), and **`Set` drops the write** if any tracked scope generation moved during the query. That is the coherence guarantee. - **`FunctionalStage.None` is a wildcard** — the filter is `Stage == requested OR Stage == None`. Filter clauses need explicit `AndAlso()`; RavenDB's default would widen them. - **Three arms, and α blends only two of them.** α is lexical-vs-vector; the abstraction arm adds `β·normAbs` on top. An a