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 SHA | Value | Status | Code returned | Verified |
|---|---|---|---|---|
| The SHA recorded at index time | c9f05cf7bf | resolved | yes | yes |
| The recorded SHA with its first hex digit changed | 09f05cf7bf | unavailable:content_mismatch | no | no |
| No SHA on record | none | resolved | yes | no |
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.
With no SHA on record, source is returned marked unverified.
Source context is checked against the indexed Git blob SHA.
Integrity checking is not semantic code correctness or security certification.
