Axiom Refract

Alpha — by invitation

Architectural analysis that shows how a codebase actually fits together — and shows its work. Every finding carries the file, the line, and the evidence it was drawn from.

What it does

Dependency graph

A persisted, queryable graph of entities and relationships across nine languages — built from real ASTs, not filename heuristics.

Single points of failure

Which modules everything else leans on, ranked by measured in-degree and blast radius rather than intuition.

Wiring defects

Code that was built but never wired in, configuration declared but never read, and components that claim a dependency nothing satisfies.

Evidence, not assertions

Every relationship is anchored to a source span. Findings can be traced back to the syntax that produced them.

Agent-callable

A first-class MCP surface, so an AI agent can ask structural questions about a repository instead of grepping for them.

Scan-to-scan diffs

Architectural delta between two commits — what actually changed in the structure, separate from what changed in the text.

Recently shipped

▸ Canonical graph persistence
Entities, relationships and evidence are stored and queryable, with source spans on every edge.
▸ Real AST symbol extraction
Functions, classes, traits and their visibility — parsed, not inferred from file extensions.
▸ Call-edge analysis with recorded basis
Every call edge records how it was resolved, so a confident edge and a guessed one are never confused.
▸ Built-but-not-wired detection
Finds components that exist, compile, and pass tests while nothing in production ever calls them.
▸ Corpus classification
Separates source from fixtures and generated output, so a percentage means what a reader assumes it means.

In build

◇ Cross-repository topology
How separate services actually connect, resolved across repository boundaries rather than one repo at a time.
◇ Coverage-aware reporting
Every result states what the instrument was able to examine, so a partial scan can never read as a complete one.
◇ Runtime governance layer
Comparing designed architecture against deployed and observed reality, with the drift scored and evidenced.

Why "by invitation." Axiom is being built against its own codebase first. We publish what it can do once it has been measured — not before. If a capability is listed above, it has run.