Skip to main content

From source files to an agent answer: Astria's evidence pipeline

· 3 min read

An agent asking who calls save needs more than a plausible name match. It needs the intended declaration, a source location, the evidence behind each relationship, and an indication of whether the graph still matches the repository. Astria 1.4.0 makes those boundaries explicit across extraction, resolution, storage, retrieval, and MCP delivery.

astria 1.1.0: evidence you can trust — no phantom files, gates that can actually fail

· 4 min read

1.1.0 fixes a class of quiet dishonesty in the graph. A node that exists because no file defined the name was borrowing whichever file happened to reference it first — so unresolved globals looked like real code locations. That single mistake surfaced as invented file-to-file dependencies, import "cycles" between unrelated crates, and an explain output that named a file which did not own the symbol. Install or upgrade with npm install -g @nodesify/astria.

astria 1.0.12: the trust release — proven graphs, gates that verify coverage, MCP over HTTP

· 3 min read

1.0.12 is the largest release since 1.0: MCP over HTTP with multi-project serving, first-class Azure/Bedrock/Kimi backends, 42 registered languages, and Whisper transcription — then hardened by a 42-finding project review and a follow-up pass that makes every "your graph is fresh" claim provable instead of assumed. Install or upgrade with npm install -g @nodesify/astria.

astria 1.0.11: the hardening release — safe migrations, an installer that can't wipe your configs

· 2 min read

1.0.11 lands everything from a full-repo audit: crash-proof database migrations, an installer that refuses to touch configs it can't parse, ownership rules for everything install writes, a native loader that fails cleanly, and bounded protocol decoding. It also carries the 1.0.10 distribution follow-ups (working Homebrew binary, plugin-bundled MCP server, registry name gates). Install or upgrade with npm install -g @nodesify/astria.