Back to the room

Pass 3 of 3 · Deep dive of PHAROSPass 1 · OverviewPass 2 · How it works

Code Observatory / Serve

Retriever

Keyword, dense, hybrid and graph modes, with the mode used always reported.

Recorded run

PHAROS at 975a38dMIT license

How it works

Auto is dense when dense can run, and hybrid when the caller passes hints. If embeddings are unavailable it falls back to keyword and says so. An explicit mode that cannot run is refused.

Hybrid is reciprocal rank fusion of keyword and dense, with a boost for an exact symbol name. Tests, docs and examples are down-ranked unless the question asks for them.

Recorded runs through it

  1. Hints turn auto into hybridThe same question with two guessed identifiers. Auto becomes hybrid, and the function that actually does the check moves from fifth to first.
  2. A missing embedder: degrade with a warning, or refuseNo embedder at all. Auto degrades and says so. Asking for a mode that cannot run is refused.

Source evidence

Claims this supports

  • PHAROS supports keyword, dense, hybrid and graph retrieval; auto prefers dense, hybrid with hints, keyword fallback with warnings.

    Source verifiedLedger

    Explicit unavailable semantic modes fail; auto can degrade with a warning. Repository scope is a filter the caller chooses; a call naming no repository searches the whole index.

  • In a recorded run with no embedder, auto used keyword retrieval with a warning, and explicit dense, hybrid and graph modes were refused.

    Recorded runLedger

  • Reported nDCG@10 improved 0.394 to 0.697 and 0.463 to 0.726 on two locked held-out sets totaling 101 questions.

    ReportedLedger

    Seven repositories and languages, single annotator, CPU. Read from project documentation; not reproduced for this site.