alt Hacker NewsThe codebase ADRs are very interesting; you can view the process of building the database, in the order in which it happened.
Looks like they took many design decisions from neo4j, and started (-ish) with an ontology that describes the graph's design itself (rather than describing _a_ graph).
You also get to see some technical decisions, like WAL etc. Very SDDish.
There's even a cookbook example using the relate ADRs to analyze the codebase decisions using relate itself: https://relatedb.ai/cookbook/codebase-context-graph/
Like a context graph for your codebase. Code analysis for agents is one use case I think makes a lot of sense for relate.