Graphtia documentation · concept
Revisions
Keep graph observations aligned with the source being read.
An observation belongs to a source state
A revision identifies the code state described by an index or result. Keeping that identity attached to an observation helps prevent a reviewer from treating old relationships as facts about a changed implementation.
Indexed source and current disk source
Explorer can display current disk content while referring to an indexed source range. The notice above the source panel is meaningful: opening a file does not, by itself, prove that its present contents match the index. The captured build explicitly tells the reader when content match has not been verified.
A practical currentness check
Read the project’s reported state before starting a review.
Check source and view notices when opening an entity.
After editing, rescan or refresh the index as indicated by the project state.
Repeat the query and attach the resulting revision to the review evidence.
A revision is not an approval
Matching revisions make two observations easier to compare. They do not establish that a change is correct or that every runtime effect is represented. Conversely, a mismatch does not prove a defect; it means the observations should not silently be treated as the same state.
Read current source and indexed evidence separately
A short local edit can make an earlier source range unreliable. In this capture, validation.ts was shortened after indexing. The file panel shows the current contents and LINE ONLY, while the inspector still describes the earlier indexed range. The notice explicitly says that content matching has not been verified.
Refresh or rescan the project, confirm the new indexed revision and repeat the query before using the old range as evidence. A current-file view is useful for orientation; it is not a guarantee that the graph and that file belong to the same source state.