Pass 3 of 3 · Deep dive of PHAROSPass 1 · OverviewPass 2 · How it works
Code Observatory / Index
Indexer
Brings the index in line with one commit, by blob SHA.
Source audited
PHAROS at 975a38dMIT license
How it works
Tracked files are compared with the index by Git blob SHA. New and changed files are parsed and embedded; unchanged files only move their commit pointer.
The repository's last commit is written after everything else succeeds. A failed run leaves the previous index searchable.
Source evidence
- Index one commit
backend/app/codeintel/indexer.py:185–241The last commit is written only after every step succeeds, so a failed run leaves the previous index searchable. - Diff by blob SHA
backend/app/codeintel/indexer.py:245–289Only new and changed files are parsed and embedded. Unchanged files just move their commit pointer.
Claims this supports
PHAROS indexes committed code using AST-aware chunks and incremental blob-SHA checks.
