Back to the room

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

Code Observatory / Index

Call graph

Resolves a call only when one target is defensible.

Recorded run

PHAROS at 975a38dMIT license

How it works

A name resolves within its own file first, then through imports, then if it is unique in the repository. A wrong edge misleads an assistant; a missing one only loses recall.

Indexing this commit resolved 6,977 calls and left 17,764 unresolved and 2,888 ambiguous.

Recorded runs through it

  1. Who calls this, and what does it call?An assistant asks where one function lives and what touches it. A real MCP call finds the definition, then reads the resolved call graph around it.

Source evidence

Claims this supports

  • Call/import graph resolution is conservative; ambiguous calls remain unresolved.

    Source verifiedLedger

  • Indexing PHAROS at commit 975a38d resolved 6,977 calls and left 17,764 unresolved and 2,888 ambiguous.

    Recorded runLedger

    Most unresolved calls reach the standard library or dependencies. PHAROS leaves them unlinked by design.

  • In a recorded run at commit 975a38d, find_symbol resolved _resolve_one to one definition with four callees and one caller.

    Recorded runLedger

    One symbol chosen by the author. The graph holds resolved edges only.