Back to the room

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

Code Observatory / Recorded run

What the blob check does with a mismatch

The same pointer through the same call, three times. Only the expected SHA changes.

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

PHAROS at 975a38dMIT license

Three outcomes

Expected SHAValueStatusCode returnedVerified
The SHA recorded at index timec9f05cf7bfresolvedyesyes
The recorded SHA with its first hex digit changed09f05cf7bfunavailable:content_mismatchnono
No SHA on recordnoneresolvedyesno

The last row is the check's limit: without a recorded SHA there is nothing to compare, so the source is returned marked unverified.

How this was recorded

Transport
In-process call to resolve_sources; bytes fetched from raw.githubusercontent.com
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, 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.

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

    Source verifiedLedger

    Integrity checking is not semantic code correctness or security certification.