Back to the room

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

Code Observatory / Serve

Source verification

Code is read at the indexed commit and compared with its Git blob SHA before it is returned.

Recorded run

PHAROS at 975a38dMIT license

How it works

PHAROS stores pointers instead of source. To answer, it fetches the file at the pinned commit, hashes the whole file the way Git does and compares that with the SHA recorded at index time.

A mismatch withholds the code and reports why. Cached bytes pass through the same comparison.

Recorded runs through it

  1. A question reaches verified sourceOne question, asked the way an assistant asks it: a real MCP call, a real dense search, and five files fetched from GitHub and checked against their Git blobs.
  2. What the blob check does with a mismatchThe same pointer through the same call, three times. Only the expected SHA changes.

Source evidence

Claims this supports

  • Source context is checked against the indexed Git blob SHA.

    Source verifiedLedger

    Integrity checking is not semantic code correctness or security certification.

  • In a recorded run at commit 975a38d, a question sent through native MCP returned five chunks, each fetched from GitHub and matched against its indexed Git blob.

    Recorded runLedger

    One local run with a question chosen by the author. Not a benchmark and not the deployed service.

  • In a recorded run, changing the expected blob SHA made PHAROS withhold the source and report a content mismatch.

    Recorded runLedger

    With no SHA on record, source is returned marked unverified.