About Decreen
Engineering teams keep making decisions. Their systems rarely remember them.
Modern software repositories contain traces of past decisions everywhere: in code, tests, documentation, pull requests, migrations, and review comments.
But those traces are not the same as authority.
Old code may reflect an abandoned approach. A test may enforce only part of a constraint. A review comment may contain an important decision that was never made explicit.
As coding agents increase the volume and speed of change, this distinction matters more.
Decreen exists to make engineering intent durable.
What we believe
Evidence is not authority
Repositories contain evidence of engineering decisions, not automatic truth. Decreen can surface candidate decisions from that evidence. Engineers decide what is actually authoritative.
Architecture is the grounding layer
Engineering decisions do not exist in isolation. They govern components, capabilities, boundaries, data ownership, workflows, and interfaces. That is why Decreen starts by building an evolving model of the system itself.
Human judgment should be reused, not repeatedly reconstructed
Once an engineering decision has been approved, future changes should not require senior engineers to rediscover it from scratch. Decreen makes that judgment reusable by humans and coding agents.
New decisions should remain visible
Not every change should be forced into an existing rule.
This is a genuinely new decision.
That is where senior engineering judgment belongs.
What we are building
Decreen connects four layers:
Architecture → Capabilities → Laws → Change
- Architecture describes what exists.
- Capabilities describe what the system is responsible for.
- Laws capture approved engineering intent.
- Change review checks whether new work preserves that intent — or requires a new decision.
Today Decreen recovers the architecture and capabilities of a repository, surfaces candidate decisions for your engineers to approve, and judges pull requests against the approved ones.
Our aim
Not to automate engineering judgment.
To preserve the judgment teams have already exercised — and direct human attention to the places where a new decision is actually needed.
Who is behind it
Alina Powała, co-founder of Decreen
PhD in Computer Science (multi-agent systems). Building software since 2008.
LinkedIn