CONFORM
The change uses the billing service.
Stop reviewing the same engineering decision twice
Decreen makes engineering decisions reusable for humans and coding agents.
Decision
Writes to customer billing state must go through the billing service.
Change
A pull request writes billing state from another component.
Your repository contains history. It does not automatically explain intent.
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.
A decision that is only written down is not applied when an agent opens the next change.
Architecture, capabilities, Laws, Judge
Repository evidence produces a descriptive model: architecture and capabilities. Decisions found in that evidence are candidates. A candidate becomes a Law only when an engineer ratifies it. Judge checks later changes against ratified Laws.
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 ratified Laws: conform, violation, or a decision the Law does not cover.
Architecture
Billing service
Capabilities
Owns customer billing state
Law
Writes must go through the billing service
Judge
A pull request writes billing state from another component
VIOLATION
Conform, violation, or a new decision.
Law
All writes to customer billing state must go through 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.
From descriptive model to engineering authority
Open Beta
Descriptive model
Architecture and capabilities recovered from the repository.
Decision-review pilot
Shared engineering authority
Ratified Laws. Judge on later changes.
Decision-review pilot
Run Decreen on one real repository.
One repository is the evaluation: whether candidate decisions can be ratified and reused on later agent changes.
A discovered statement is not authority until a human ratifies it.
1
Discover
Surface candidate decisions from code, documentation, tests, and historical review evidence.
2
Review
Engineers inspect the claim and the evidence behind it.
3
Ratify
Approve, edit, or reject the candidate. Existing code is evidence, not automatic truth.
4
Reuse
Apply the decision to later planning, implementation, refactoring, and review.
Collaboration
Share approved decisions across the team instead of keeping them in individual memory.
Enforcement evidence
See which tests, boundaries, types, or mechanisms actually protect a decision.
Where the current workflow loses engineering decisions
Sixteen questions: architectural context given to agents, whether rules stay current, how violations are detected, and when a rule itself should change.
Describe how work usually happens today — not the process you intend to introduce.
Open Beta
Run it from the local repository.
No Decreen account is required to generate the first preview. Raw source code is not uploaded.
Open Beta preview (90s)
Where Decreen starts: architecture and capabilities from your repository
- 1
Set up Decreen locally
Run this from your repository root. It is safe to re-run.
- 2
Run preview
Run this in Cursor, Claude Code, or Kilo Code. Your agent reads the local repo and generates a structured architecture artifact.
- 3
Open your temporary map
Decreen turns the artifact into an interactive preview. Claim the map only if it's useful.
Unclaimed previews expire after 7 days.
What Decreen does not do
- Existing code is not automatically treated as correct.
- AI does not silently create authority.
- Decreen does not autonomously approve or block merges.
- Not every Law is mechanically enforceable.
- Analysis runs in your execution environment. Raw source code is not uploaded.