npm install -g @nodesify/astria. This is the release the project is fully astria: the binary, the npm package, the .astria/ graph directory, the environment variables, the skill files. Same idea that inspired it, new engine throughout.
@nodesify/graphify?1.0 is a rebrand, not a rewrite of your data. Install the new package and run once:
astria migrate # renames .graphify/ -> .astria/ and the global store
astria install # refreshes AI-tool skills/hooks (also cleans the old graphify entries)
GRAPHIFY_* environment variables keep working; ASTRIA_* takes precedence.
hyperedges produced without an LLM: community participate_in groups and shares_reference literal groups. They flow into graph.json, the report, the wiki, HTML hulls, and explain. Graphify's hyperedges are LLM-produced; ours are local and reproducible.~/.astria/global.db: global add/remove/list/path, repo-tag prefixed merging that unifies external symbols across repos, same_type_as type edges, and cross-repo call resolution that fails closed on ambiguity.diagnose (read-only health report), save-result/reflect curated memory (.astria/memory/ → graph nodes → LESSONS.md) alongside automatic learned edges, build-time validation, a JSONL query log, and always-on instruction blocks in AGENTS.md/CLAUDE.md..mcp.json/mcp_servers.json/claude_desktop_config.json (env names only, never values), add --scip, add --postgres (read-only), and transcript sidecars in .astria/transcripts/.add <url> validates every redirect hop, blocks loopback/private/link-local addresses (IPv4 and IPv6), and slugifies downloaded filenames so a hostile URL cannot write outside raw/. The HTML export renders labels as text, never interpolates HTML.The docs site now ships per-release versions: 1.0.0 is the default, 0.8.0 stays available as an archive, and Next tracks what is landing after 1.0.0. See the docs — and benchmarks for how every number is measured and reproduced.
astria is developed at Nodesify/astria — issues, the worked examples, and the head-to-head benchmark data all live in the repo. It is built by Nodesify.
]]>npm install -g @nodesify/graphify. The graph now exports itself as documentation, adds a local semantic layer, and keeps learning from how you use it.
Highlights:
wiki / run --wiki: an agent-crawlable wiki (index.md + one article per community and god node, relative markdown links that GitHub and Obsidian both navigate). update regenerates it, so it never drifts stale.wiki --format obsidian: per-node notes with frontmatter tags and [[wikilinks]], community overviews, and a graphify.canvas. On this repo: 2,040 notes, 5,000 canvas edges.run --embed downloads a small local model once (~90 MB, then offline forever — no API key) and adds similar_to edges plus embedding-backed query recall. Communities on this repo consolidated 401 → 194.learned edges; the graph compounds in value the more you use it.export --format cypher writes an idempotent MERGE script for cypher-shell.The unreleased Next docs version already covers what is landing after 0.8.0: the deterministic hypergraph, the cross-repo global graph, graph health diagnostics, and offline-first ingest (SCIP indexes, Postgres introspection, MCP configs). See the docs — and benchmarks for how every number above is measured and reproduced.