@goodbones/oxlint and @goodbones/cli turn architecture policy into one manifest of your repository —
import boundaries, export sites, member vocabularies and file taxonomy, all resolved to real
files and enforced by oxlint.
One manifest, not a rule list
A tree keyed by path pattern, where everything the architecture says about a part of the repository is written at that part of the repository — its imports, its importers, its members, the siblings it owes, the children it admits.
Real resolution
Every pattern is matched against a resolved file path, through your tsconfig
paths and your workspace links. A rule about @/modules/user is a rule about the
file that specifier actually names.
Tight by default
A folder admits only the children it lists; a file may import only what it or an ancestor
allows. Laxity is opted into by name — reset, unrestricted, layout: open — so widening is
a sentence someone wrote, and grep is the adoption backlog.
Every rule proves itself
Each compiled rule carries a probe generated from its own node path, and the plugin refuses to load if any rule fails it. A rule that has drifted into matching nothing is a load-time error, not something a separate script might notice later.
A ratchet, not a suppression list
The baseline records violations a repository carries while it adopts a rule, keyed by a line-independent fingerprint. Fix one and the build fails until its entry is gone, so the floor only ever rises.
Two ways to ask
An oxlint plugin for the editor and CI, and a CLI that evaluates the same policy with no linter in the loop. Both answer to the same core, so an alpha plugin API is not a single point of failure.