Nobody can say how much of the codebase the team still understands.
The system moves, the tests pass, and fewer people can explain how it works. New hires feel it first. So does every new agent session — it onboards from zero, every single time.
The code grew faster than anyone’s understanding of it.
More than half of merged code is now written by AI. It arrives faster than anyone reads it — and the people who could explain the old code are stretched thinner every quarter.
of merged code is AI-authored
Nearly doubled in a year. The half of the codebase nobody wrote is the half nobody can explain to the next hire.
code churn roughly doubled
Since AI assistants arrived. And copy-pasted code now exceeds refactored code for the first time.
use it — trust it
84% of developers use or plan to use AI. Only 33% trust its accuracy. Your new hire inherits both numbers on day one.
“Comprehension debt is the growing gap between how much code exists in your system and how much of it any human being genuinely understands.”
Give day one a source of truth.
Onboarding is slow because the truth about your codebase lives in a few senior heads. Timo writes it down, keeps it verified, and commits it to your git — so a new person reads instead of interrupting.
Docs a new hire can trust
Timo Docs where every claim cites file:line — or says it’s a gap. No wiki archaeology, no guessing which page is still true. If the docs don’t know, they say so.
Timo Memory & Docs →Memory that answers “why is it like this?”
Timo Memory holds the actual history: the decisions, the bugs, the reasons behind the weird parts. The questions that used to cost a senior engineer an afternoon get answered from the record.
How memory works →Ask Timo, get cited answers
A new developer asks about the codebase and gets an answer with file:line sources — and “TBD” instead of a guesswhen the answer isn’t known. Confidence you can check.
Ask it something →The same install onboards humans and agents. A new developer and a new agent session read the same truth.
Onboarding speed is on the scoreboard — honestly.
We don’t promise a number we haven’t measured at your company. We measure it.
Time to a new developer’s first independently merged PR
It’s one of the five outcomes on the scoreboard, with a baseline, a target, an owner, and a next action — like every metric Timo tracks.
Before the next new hire’s start date.
1 · Scan
Run the Agent-Readiness Scan on a repo. Read-only. It shows exactly where a newcomer — human or agent — will get lost, and what to fix first.
2 · Install — as a PR
Timo writes memory and docs into your repos as a pull request your team reviews. Your seniors correct it once, in review — instead of repeating it to every new person.
3 · Hand over the docs
The next new hire starts with cited docs, the history behind the decisions, and a place to ask questions that answers with sources. So does every agent session they open.
See what your next hire would be walking into.
Scan a repo in five minutes. Read-only, free, and the report shows where understanding is thinnest.