CONFORM
The change uses the billing service.
Decision-aware infrastructure for software teams
Decreen turns repository evidence into human-approved engineering authority, then checks code changes against it.
Analysis runs in your execution environment. Raw source code is not uploaded.
Law
Writes to customer billing state must go through the billing service.
Change
A pull request writes billing state from another component.
VIOLATION
Code, tests, docs, and old reviews contain evidence of past decisions — and also obsolete patterns, migration residue, and shortcuts that should not be repeated.
Coding agents can imitate what exists without knowing what is canonical, what must remain compatible, what has been deliberately rejected, or which decisions are still binding.
As change volume grows, senior engineers end up reconstructing that context in review again and again.
Architecture
What exists and how it connects.
Capabilities
What the system does and where responsibility lives.
Laws
Human-approved engineering decisions. Not rules inferred automatically from existing code.
Judge
Change review against approved Laws: conform, violation, or a genuinely new decision.
Architecture
Billing service
Capability
Owns customer billing state
Law
Writes must go through the billing service
Judge
A pull request writes billing state from another component
VIOLATION
Law
All writes to customer billing state must go through the billing service.
CONFORM
The change uses the billing service.
VIOLATION
The change writes directly from another component.
NEW DECISION
The change introduces a case this law does not cover. Senior judgment is required.
Start from your local repository. No Decreen account is required to generate the first preview.
Raw source code is not uploaded.
Run this from your repository root. It is safe to re-run.
Run this in Cursor, Claude Code, or Kilo Code. Your agent reads the local repo and generates a structured architecture artifact.
Decreen turns the artifact into an interactive preview. Claim the map only if it's useful.
Unclaimed previews expire after 7 days.
Coding agents can write and review code, but every engineering team gives them a different operating environment.
Answer 16 questions about how your team provides architectural context, keeps engineering rules current, detects violations, and decides when those rules themselves should change.
You'll receive an immediate profile across four dimensions, plus recommendations based on your answers.
Describe how work usually happens today — not the process you intend to introduce.
As more engineering teams participate, you can also opt to receive an aggregate benchmark against similar organizations.
Especially for staff and principal engineers, and engineering leaders.
Check whether generated changes preserve an approved decision.
Separate current intent from historical residue.
Avoid propagating historical patterns that should not be repeated.
Find where an important rule exists but has little mechanical protection.
In an external repository, Decreen surfaced 30 candidate engineering decisions from repository evidence for human review.
Those candidates were reviewed by people before they were treated as binding.
In controlled cases where a decision had already been approved, Decreen distinguished a change that conformed, a change that violated it, and a change that required a genuinely new decision.
General accuracy across arbitrary repositories.
Free
Paid