Skip to main content
Version: 1.0.0

The .astria directory

Everything astria produces lives in plain files, so it is inspectable, backup-able, and disposable. Running astria run <path> creates:

<repo>/
.astriaignore # (optional, repo root) gitignore-syntax exclusion list
.astria/
db.sqlite # The graph database — the source of truth
graph.json # Full graph export (nodes, edges, hyperedges, communities)
graph_report.md # Markdown report: hub nodes, communities, surprising connections
wiki/ # (after `wiki` / `run --wiki`) markdown wiki: index.md + articles
memory/ # (after `save-result`) curated Q/A docs, ingested as graph nodes
reflections/ # (after `reflect`) LESSONS.md outcome aggregation
transcripts/ # (optional) drop .txt/.md here; ingested as document nodes
raw/ # (after `add <url>`) downloaded papers/pages/images

Plus, outside the repo:

~/.astria/global.db # Cross-repo global graph store (`global add`, `run --global`)
~/.astria-embed-cache/ # Local embedding model (~90 MB, downloaded once; override with ASTRIA_EMBED_CACHE_DIR)

Inside db.sqlite​

The database is plain SQLite — open it with any SQLite client. Tables:

TableContents
nodes / edgesThe graph (see Graph model)
hyperedgesN-ary groups (participate_in, shares_reference)
communitiesCluster assignments, labels, cohesion
file_manifestEvery detected file and its hash — powers incremental update
extraction_cachePer-file extraction results, keyed by content hash — unchanged files are not re-extracted
pipeline_runsRun history (when, what stage, how long)
query_history / query_pairsQuery log and the (seed, discovered) pairs that feed learned edge promotion
node_embeddingsVectors from run --embed
_metaSchema version and build metadata (what status reads)

Version control​

.astria/ is safe to gitignore (the default posture — rebuild any time with astria run .), but nothing stops you from committing parts of it: the wiki/ export is plain markdown that renders on GitHub, and graph_report.md reads well as repo documentation. raw/ (downloads) and db.sqlite (binary) are the usual ones to exclude.

Maintenance​

  • Reset — delete .astria/ and re-run astria run .. Nothing outside the directory is mutated (the global store and embed cache are separate).
  • Stale? — astria status reports graph health and last-build time; astria update rebuilds incrementally from the file manifest.
  • Suspect the data? — astria diagnose is a read-only health check (dangling edges, duplicates, stubs).
  • Pre-1.0 layout? — astria migrate renames .graphify/ → .astria/, .graphifyignore → .astriaignore, and moves the old global store.