Decision-aware infrastructure for software teams

Stop reviewing the same engineering decision twice

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

The Problem

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.

Architecture → Capabilities → Laws → Judge

  1. Architecture

    What exists and how it connects.

  2. Capabilities

    What the system does and where responsibility lives.

  3. Laws

    Human-approved engineering decisions. Not rules inferred automatically from existing code.

  4. Judge

    Change review against approved Laws: conform, violation, or a genuinely new decision.

  1. Architecture

    Billing service

  2. Capability

    Owns customer billing state

  3. Law

    Writes must go through the billing service

  4. Judge

    A pull request writes billing state from another component

    VIOLATION

A decision once. Reused on every relevant change.

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.

Open Beta — free

Start with an evolving model of your system

This is where Decreen starts. The Open Beta builds a repository-grounded model of architecture and capabilities: generate a preview, claim a workspace, deepen important parts, connect the model to source evidence, and refresh it as the repository changes.

Open Beta preview (90s)

Where Decreen starts: architecture and capabilities from your repository

Open full interactive map

Preview your repository

How the Open Beta preview works

Start from your local repository. No Decreen account is required to generate the first preview.

Raw source code is not uploaded.

  1. 1

    Set up Decreen locally

    npx -y @decreen/local setup

    Run this from your repository root. It is safe to re-run.

  2. 2

    Run preview

    /decreen-preview

    Run this in Cursor, Claude Code, or Kilo Code. Your agent reads the local repo and generates a structured architecture artifact.

  3. 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.

Prefer manual skill setup?

How well does your team preserve architectural intent?

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.

Paid pilots

A discovered statement is not authority until a human ratifies it.

  1. 1

    Discover

    Surface candidate decisions from code, documentation, tests, and historical review evidence.

  2. 2

    Review

    Engineers inspect the claim and the evidence behind it.

  3. 3

    Ratify

    Approve, edit, or reject the candidate. Existing code is evidence, not automatic truth.

  4. 4

    Reuse

    Apply the decision to later planning, implementation, refactoring, and review.

Laws

Capture the engineering decisions that should remain true.

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.

Judge

Compare a change with approved Laws and mark it CONFORM, VIOLATION, or NEW DECISION.

Built for teams where senior judgment is becoming the bottleneck

Especially for staff and principal engineers, and engineering leaders.

AI-generated pull requests

Check whether generated changes preserve an approved decision.

Mature codebases

Separate current intent from historical residue.

Migrations and refactors

Avoid propagating historical patterns that should not be repeated.

Weakly enforced decisions

Find where an important rule exists but has little mechanical protection.

What we have validated so far

Decision discovery

In an external repository, Decreen surfaced 30 candidate engineering decisions from repository evidence for human review.

Human validation

Those candidates were reviewed by people before they were treated as binding.

Controlled change classification

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.

What we have not yet established

General accuracy across arbitrary repositories.

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.

Start free with a descriptive model. Pay when it becomes shared engineering authority.

Free

Evolving descriptive model

  • Architecture
  • Capabilities

Paid

Shared engineering authority

  • Laws
  • Ratification
  • Collaboration
  • Judge