Architecture Boundaries as Tests

Your import rules, enforced in CI

Point this CLI at any Python repo and a YAML contract — it walks every .py file's AST and fails the build on the exact line that breaks your rule.

Buy the kit — $15 Try the demo ↓

Interactive demo

Python file (paste any snippet)

Contract (YAML rules)

Boundary folder name

Filename (for context)

Paste code above and click Check.

How it works

Step 1 — Write a contract.yaml

Declare your boundaries. Example: ui must not import db, jobs may only import shared. Plain YAML, checked into your repo.

Step 2 — Wire it into CI

One command: python arch_check.py . contract.yaml. Exit 0 = clean. Exit 1 = violations with exact file:line. Exit 2 = config error. Drop it into your GitHub Actions or pre-commit hook.

Step 3 — The build fails before the drift does

No more "I thought ui wasn't supposed to touch db" code-review comments. The rule is in the repo; the check is automatic.

Arch Boundaries Kit

$15

One-time · instant download

Single-file Python CLI (zero runtime deps beyond PyYAML)
Full fixture suite — clean, dirty, init-violation, syntax-error, unicode-error
contract.yaml template for a typical layered-arch repo
GitHub Actions workflow snippet
README with pre-commit hook example

Buy now — $15