Arch-Engine extracts structural relationships directly from source code and enables enforcement of architectural rules via policy packs — automatically, deterministically.
npm install @arch-engine/clinpx arch-engine doctorDetected authority boundary crossing:
frontend → database mutation layer
Suggested policy:
enforce service isolation boundaryArch-Engine converts source structure into enforceable architecture diagnostics in a deterministic pipeline.
Routes, services, modules and dependencies become structural input
A deterministic topology is built directly from real relationships
Domain-aware analyzers enrich structure with execution meaning
Architecture rules evaluate authority, contracts and journeys
Actionable findings surface before drift reaches production
Software architecture is discussed in reviews and documented in wikis. It is rarely enforced systemically by tooling.
Dependencies cross boundaries silently.
Small changes create unexpected blast radius.
Architectural rules exist only as convention.
Teams discover structural problems in production because nothing surfaces them earlier.
This is not another linting tool.
It does not check code style or find bugs.
Arch-Engine operates one level above — on the structural relationships between packages, modules, and boundaries. It makes your architecture visible and enforceable through policy packs as a first-class part of your development workflow.
Arch-Engine reads your repository and extracts the structural relationships between every package, module, and boundary.
With that structure extracted, teams can:
No annotations required. No build changes. One install. Works alongside existing tooling.
Run one command to inspect your architecture. Reports structural confidence, connectivity coverage, and policy readiness — instantly.
npx arch-engine doctor✔ Topology extracted successfully
✔ Workspace type resolved as: single (highest confidence)
✔ Packages detected: 1 / 1 expected
✔ Connected nodes: 1
✔ Coverage: 100%
✔ Connectivity: 100%
✔ Confidence: HIGH (Structured single workspace extraction)
✔ Authority crossings observed: 0Safe diagnostic runtime. No source files modified. No dependencies mutated. Creates a local .arch-engine/ context directory on first run.
No network requests. Fully offline execution by default. Sub-second execution on typical small and mid-sized workspaces.
Run instantly without installation using npx.
Policy packs are optional. The engine runs without them.
Policy packs encode architecture rules as enforceable constraints. Define them once. The engine enforces them on every run. Examples: boundary protection, dependency drift detection, API contract alignment validation.
Adapters let Arch-Engine understand how your project is structured — npm, pnpm, and Yarn workspaces — monorepo, single-package, or multi-workspace. No configuration required for supported workspace types.
Adapters are read-only and never modify your project.
Available now. Stable CLI runtime. MIT licensed.
Scoped npm packages on the public registry. Stable public API surface.
Topology extraction in a single command.
Automatic project structure discovery.
Composable architecture rule enforcement.
npm install @arch-engine/cliZero configuration required. Instant diagnostic.