Onboarding
How we start.
One component, your engineers, a few weeks.Then the map, the gate and the register are yours.
01 · Week by week
What happens, week by week.
Roughly four weeks from the first call to the gate running in your CI. Week one takes about two hours of the owners' time.
- Week 0
Scope one component, sign the NDA
We agree the shape and the fee. We countersign your NDA before reading a line.
- Weeks 1–2
We recover the promises
We write down what the code promises, with your engineers. They sign.
- Weeks 2–4
Worst cases, obligations, evidence, first findings
A person validates each finding before you see it.
- From week 4
The gate runs in your CI
The dashboard and reports arrive as findings are validated.
Agents do more of the crunching every month. A person stays on the line between machine and judgment.
02 · From your side
What we need from you.
Three things. Proof reads your code; it does not write it.
Two or three engineers who own the component
A few hours a week while we onboard. They know what the code is meant to do; we write it down with them.
A repository we can read
Public, or private under NDA with read-only access. Private stays private.
One person who can sign
A promise counts once someone who owns the code signs it. Anything an agent drafts waits for that signature.
03 · The artifacts
What you get, and when.
Everything lands in your repository, under your licence. The dashboard opens as soon as a person has validated the first findings.
- Weeks 1–2
- The promises, written down and signed by your engineers.
- Weeks 2–4
- A worst case and obligations for each promise: what must be true, and which test shows it.
- Weeks 2–4
- The register of known breaks. Each entry is a test that fails on your main, validated by a person.
- From week 4
- The gate in your CI. A broken promise blocks the merge.
- From week 4
- The dashboard and the reports, updated as findings are validated.
The record
What you keep when people change.
People move teams. Agents get swapped for better agents. The sentence your engineer signed stays where it is, and the gate keeps checking it.
Fig. 01 · A promise enters the record. It is still checked after the author leaves or the agent is swapped. Example, hand drawn.
04 · Fees
What it costs.
A fixed fee for the first component, then a flat subscription for the gate and the dashboard. We agree the shape before we start.
Onboarding
One fixed fee for the first component, agreed in writing before work starts. No metering while we onboard.
After onboarding
A flat subscription for the gate and the dashboard, billed month to month. You choose the cadence at the start: per release, weekly, even daily.
Fix work
Separate work, scoped when you want it and delivered as pull requests you review.
05 · Confidentiality
Private by default.
We countersign your NDA before reading a line of private code. No logos, and no names in public unless you publish them.
Open source, in the open
We read the public repository. Disclosure is on your terms, and the map can be public, as it is for jsonparser.
Read-only, on your terms
We countersign your NDA first, then read with read-only access. Nothing about the work is public unless you publish it.
Start
Start with one component.
Pick the one you would least like to be asked about. Leonid reads every request and replies within two working days.
Leonid Bugaev
founder · onboards every team himself
Explore a live map →Prefer a call? 20 minutes with Leonid →