Back to the room

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

Code Observatory / Recorded run

A missing embedder: degrade with a warning, or refuse

No embedder at all. Auto degrades and says so. Asking for a mode that cannot run is refused.

RECORDED Captured from a real run on November 2, 2026. Nothing is running now.

PHAROS at 975a38dMIT license

Degrade, or refuse

RequestedResultWhat PHAROS said
autoUsed keyworddense retrieval unavailable (no embedding backend configured (EMBEDDING_BACKEND=none)); used keyword retrieval only
denseRefused: ModeUnavailableno embedding backend configured (EMBEDDING_BACKEND=none)
hybridRefused: ModeUnavailableno embedding backend configured (EMBEDDING_BACKEND=none)
graphRefused: ModeUnavailableno embedding backend configured (EMBEDDING_BACKEND=none)

How this was recorded

Transport
In-process Retriever with embedder None, as EMBEDDING_BACKEND=none configures it
Index
Indexed from GitHub at this commit through the production path: PostgreSQL, pgvector HNSW and ONNX embeddings.
Database
PostgreSQL 17.11 with pgvector 0.8.7
Embedding model
granite-embedding-english-r2-int8
Where
Local Mac, loopback only; not the deployed service

Claims this supports

  • 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

  • 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.