use case

Backlinks

code-associated specification files are just a part of the documentation context graph

For example, you can have a code-associated specification file, but for the graph to be complete, you should also have associated use cases that role up to design principles, persona needs, etc. Put that context right in the repo. If it's a documentation context graph, it needn't cause context rot because progressive disclosure is a fundamental aspect of graphs.

see in context
not every detail is described in an ERD

Often it is pretty broad strokes. For a web app, it might describe screens, some use cases, maybe some key choices related to the underlying data model.

see in context