Clarity
Open source ↗
A software design tool for AI-native developers and coding agents. Review design impact before commit.
Comprehension · Verification · Remediation
Most of the code
you’ll touch this year,
you didn’t write.
Methodology and tools for that. Since 2019.
Writing code is industrialized.
The rest should be too.
Even before AI did the writing, comprehension, evolution, verification, and remediation were most of the job. AI multiplies the volume, not the hours. Better models alone don’t close the gap — now more than ever, each demands purpose-built methods and tools. We’ve been building them since 2019.
Four kinds of work.
One loop.
Every codebase lives in a loop: change, build, run, repeat. Four kinds of work keep that loop reliable: comprehension grounds the work; evolution adds capability; verification audits every change; remediation fixes decay.
AI changed the craft. Our response: mechanize what AI hasn’t reached, direct what it has.
01
Mechanized Comprehension
Understand systems through tools that surface structure, trace behavior, and mine commit history — at scale.
02
Mechanized Verification
Verify structure and behavior separately, continuously and deterministically — on every change.
03
Mechanized Remediation
Diagnose architectural drift, decay, and tech debt; remediate with provably safe transformations without risky rewrites.
04
Directed Evolution
Specify the intent; evolve software toward it through purpose-built harnesses for coding agents.
Three dimensions cut across all four: source, granularity, representation.
Vary the source.
Vary the granularity.
Vary the representation.
Line-by-line reading no longer scales. Every kind of work varies along three dimensions to keep up with systems that evolve faster than anyone can read them.
Source.
Where you look: code, version control history, documentation.
Granularity.
How much you see at once: from a single line of code to the entire system’s design.
Representation.
The most suitable form for the information: text, tables, charts, graphs, and more.
Each kind of work needs its own tools. Some are open source. The rest are available through consulting engagements.
Tools we ship.
Some of the tools embodying our methodology are open source. Each one built to solve a problem manual approaches couldn’t.
Eureka
Open source ↗
Visualizes the structure of large Kotlin and Java classes as interactive graphs. A 3,000-line class on one screen, updating in real-time.
Verification · Remediation
Terrain
Open source ↗
Renders a git repository as a zoomable sunburst of its directory structure, sized by lines of code. The whole codebase on one screen, at every zoom level.
Comprehension
Cardbox
Open source ↗
Structural analysis of Android codebases through graph queries via jQAssistant.
Comprehension
Timelapse
Open source ↗
Leverages Git history to reveal tribal knowledge. Every codebase has a story in its version control. Timelapse makes it legible.
Comprehension
| Tool | What it does | Pillars |
|---|---|---|
Clarity Open source ↗ | A software design tool for AI-native developers and coding agents. Review design impact before commit. | |
Eureka Open source ↗ | Visualizes the structure of large Kotlin and Java classes as interactive graphs. A 3,000-line class on one screen, updating in real-time. | |
Terrain Open source ↗ | Renders a git repository as a zoomable sunburst of its directory structure, sized by lines of code. The whole codebase on one screen, at every zoom level. | |
Cardbox Open source ↗ | Structural analysis of Android codebases through graph queries via jQAssistant. | |
Timelapse Open source ↗ | Leverages Git history to reveal tribal knowledge. Every codebase has a story in its version control. Timelapse makes it legible. |