Don’t take my word — check it
Behind every number in the case is code, a git command or an artifact. This is a verification map for the sceptic: run the command and see for yourself.
доказаноevery number is checked by a read-only commandto the table →
What’s inside the system — in numbers
The internal metrics are pulled from the real repository — not estimates, but facts from the code and the artifacts. The make-up first; below, in the table, is how to recompute each number yourself.
- Flagship PWA — 42,510 lines of TS/TSX: 111 components across 13 domains, 21 REST routes, 25 database tables in one schema.
- Quality — 66 test cases across 26 files; CI runs types → style → tests → build, stopping on the first error.
- Book — 261 pages, 43 chapters, PDF + EPUB 3 (epubcheck PASS, 0 messages), 3 editions.
- Performance — a static prerender of every route: interactivity is added by 6 pinpoint client inserts on top of the static page, not a full re-render of the whole page.
- Pace — 145 commits in 10 days across 7 repositories: 1 root + 6 modules.
Behind the case’s 10 days — a year of live work
The flagship was built in 10 days — but it wasn’t a one-off sprint. Over the past year on the public GitHub profile — 3 512 contributions, activity on 281 of 370 days, and a streak of 130 days in a row. Each green square is a real trace you can see on the profile.
доказаноa snapshot of the public profile github.com/temadev — open it and checkopen the profile →
Every row is a read-only command or an artifact
The commands only read, they change nothing. Run them from the repository root. No internal paths, secrets or network addresses — only what anyone can reproduce.
| Claim | How to check |
|---|---|
| 145 commits | git rev-list --count HEAD per repository |
| 10 days in git | git log --format=%ad --date=short — first and last commit |
| 7 repositories (1 + 6) | cat .gitmodules — root + 6 submodules |
| 42,510 lines of TS/TSX | find src -name '*.ts*' -exec cat {} + | wc -l |
| 111 components | find src -name '*.tsx' | wc -l |
| 21 REST routes | find src -name route.ts | wc -l |
| 25 database tables | grep -c 'sqliteTable\|pgTable' schema.ts |
| 66 test cases | grep -rho 'it(' --include='*.test.*' | wc -l |
| 261 book pages | pdfinfo book.pdf | grep Pages |
| EPUB is valid | epubcheck book.epub → PASS, 0 messages |
| Static prerender of routes | next build → each route marked ○ (Static) |
| 200+ agents / wf-id | grep -rhoE 'wf_[a-z0-9-]+' qa/ | sort -u |
The commands are generic. The full index, with the expected numbers per repository, I walk through on a call — together with read-only access.
I design AI pipelines — not just use AI
The strongest proof isn’t the volume of code, but how it was made. Each deepening stage passes an adversarial barrier: draft → three parallel veto lenses → revision by the verdicts → a block verdict of “to production” or “back for rework”. 200+ agents across 9 Workflow cycles; each cycle leaves a real wf_* run id.
What’s proven, what’s an estimate — and what I deliberately don’t claim
Three kinds of numbers, with different statuses: proven metrics from the repository, external market reference points (a calculation, not a fact), and business outcomes I deliberately don’t claim yet. Each group’s colour comes from the trust code above.
Internal metrics
- Lines of code, components, routes, tables, tests — pulled from the repository.
- Commits and time in git — by a command across each of the 7 repositories.
- Book pages, EPUB validation, the number of editions — from the assembled artifacts.
- The agent count and wf-id across 9 Workflow cycles — from the audit reports.
External reference points
- Competitors’ market statistics (renewals, churn) — the sources weren’t kept.
- Penalty amounts and external price ranges — a reference point, not a fact.
Business outcomes
- Revenue, customers, sales — the first cohort has only just started; I don’t pass it off as fact — I claim only what’s provable.
- Reviews and before/after cases — I publish only with consent and only when I can confirm it.
The numbers add up — see how they came to be
The evidence base holds together. Three doors — each answers a different question.
The full story
From a warm audience with no product to an ecosystem of 6 products — how it was all built in 10 days.
Открыть →MethodHow the pipeline works
The role boundary, six phases, the adversarial cycle — the operating system in full.
Открыть →ApplicabilityPorting it to your niche
80% of the frame ports as-is, 20% to the subject matter — where it gives leverage and where it doesn’t.
Открыть →Check it in person
On a call I’ll open read-only repository access and walk through the index — with the expected number behind each claim.