11 packages, one database,
and the rules that hold them apart.
The full package graph, the dependency rules as the tests that enforce them, and who owns which files.
Real imports. Hover to see them, click to see what each owns.
No auth → billing, no executions → billing, core → nothing — the dependency-direction test fails the build otherwise.
Enforced by tests,
not by a style guide.
Break a rule and read the assertion the real test emits. 15 suites run on every commit alongside the unit and real-database tests.
Four kinds of file. Four owners.
Versioned on npm as @intelligo-dev/*. Services, schema, migrations. Upgraded with SemVer; never edited in place.
What intelligo create writes: the composition root, plans, i18n routing. Hashed in intelligo.manifest.json so doctor and upgrade --check know what you changed.
What shadcn add writes from the registry. Yours from the first commit; re-install to take an update.
Prompts, tools, knowledge, evals — in your AI framework. Intelligo has no import into it.
Ready to try it? Three commands and the app runs against a stub model.