CARL Builder · Request access
Spec-first.
Drift-aware.
Agent-native.
CARL is a proprietary, free-to-read readiness standard with guided tooling. It reads your repository, scores its agent-readiness across eight pillars, and surfaces exactly what to fix first — measured, not guessed. Tell us about your codebase and we'll measure it before any outreach.
Intake
We don't open CARL on every repo. Tell us about yours and we'll measure first.
The process
What happens after you submit.
Four phases, end-to-end. Nothing is automated past the acknowledgement — every step below is a real human reading your submission and writing back.
Phase · 01
IntakeSubmission lands.
Your form posts to a single Cloudflare Worker route. We persist the lead, a human reviews it, and you get a short automated follow-up email sequence (every email has an unsubscribe link).
Phase · 02
ReviewHumans read it.
A maintainer reviews the submission alongside your public GitHub org. We decide whether CARL is a fit for the repository before a person replies.
Phase · 03
ReplyWe write back.
You receive a real reply from a human — usually within a couple of business days. If we don't think CARL fits yet, we say so plainly and tell you what we'd want to see first.
Phase · 04
ScanScanner runs.
If we move forward, we schedule a CARL scan against your repository, walk you through the agent-readiness score, and hand off the working set the next AI session should pick up.