You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Use case: architecture rules checked over history #28
Add a use case: architecture and layering rules written as Datalog, checked against the module graph at every commit.
The idea
Store the module or package dependency graph per commit. Write rules such as "UI code may not depend on the database layer, directly or through any chain." Tools like ArchUnit check this for one snapshot. With history, you can also see when a rule was first broken and how the graph drifted.
Questions it answers
Which forbidden dependency paths exist right now?
At which commit did each violation first appear?
How has coupling between two areas grown over the last year?
Why Minigraf fits
"Directly or through any chain" is reachability, which recursive rules handle well.
Valid time per commit gives the history without storing full copies of the graph by hand.
Suggested content
The idea, compared briefly with snapshot-only tools
A fact schema (module, depends-on, layer)
A recursive rule that finds forbidden paths
A query for the first commit where a violation appeared
Notes
This is an idea for others to build. There is no official tool.
Activity