Pawsitively, Aternex's first product, reached its first production deploy 12.5 hours after its first commit; over its first four days it merged 158 pull requests, none with a failing check, and its six production projects are held to 100% line and branch coverage.
Pawsitively, multi-tenant software for dog daycare, boarding and training businesses that Aternex designed, built and runs without a client brief, with AI assistance. A .NET 10 and Blazor application on PostgreSQL 18, released by GitHub Actions to a self-hosted machine.
Replay the first four days
A new product, from first commit to production
240 commits in four days, and the first production deploy on the first day.
Each bar is one day's commits on main, New York time; the axis runs to 88, the busiest day.
| Value | Method | Recorded | Scope |
|---|---|---|---|
| 12 h 33 min | git log: first commit 2026-10-17 09:13 UTC; gh run list for the deploy workflow: first run, successful, started 2026-10-17 21:45 UTC | 2026-10-20 | From the first commit in the repository to the first successful production deploy |
| 240 commits and 158 merged pull requests | git rev-list --count on main and gh pr list --state merged; 88, 60, 55 and 37 commits on 17, 18, 19 and 20 October (New York time); 210 of the 240 commits are co-authored with Claude | 2026-10-20 | The whole history, which begins on 2026-10-17 with no earlier work |
| 0 merged pull requests with a failing check; 158 of 159 deploys succeeded, 63 s at the median | gh pr list --state merged with each pull request's check results; gh run list for the deploy workflow, run start to finish | 2026-10-20 | Every merged pull request and every deploy to 2026-10-21 01:09 UTC; main now requires eight checks, added over the first day |
| 3,186 test methods; 100% line and branch coverage | 2,743 [Fact] and 443 [Theory] attributes across 753 test files; scripts/coverage.py fails any of the six production assemblies below 100% line and branch coverage, on every pull request | 2026-10-20 | The six production projects: Domain, Application, Contracts, Infrastructure, Server and Web; browser-only start-up code and generated code are excluded |
| 48,179 lines of tests for 33,332 lines of production code | Raw line counts of the C# and Razor files under tests/ and src/, blank lines included | 2026-10-20 | The whole repository at commit c04602f1 |
| 98 / 100 / 100 / 100 on mobile; 100 in every category on desktop | Lighthouse 12.6.1 with simulated throttling, three runs each, in the Lighthouse workflow against the production build: performance, accessibility, best practices and SEO; largest paint 2.4 s on mobile and 0.54 s on desktop, blocking time 0 ms, layout shift 0 | 2026-10-21 | The public home page, first view |
Dates are when each figure was recorded for this site; the work itself is dated in the setting above.
What this does not prove
Pawsitively is in evaluation: sign-up starts a 30-day evaluation, no payment is collected, and no customer has paid yet. It runs on one self-hosted machine and off-machine backups are not yet active. The speed came from one engineer working with AI coding agents under strict automated gates; it is not a measure of what a team would take. Coverage shows every line and branch ran under a test, not that the tests describe the right behaviour. The Lighthouse runs use the production build on the CI machine, not the live site, and cover the public pages; the signed-in workspace loads a WebAssembly application and is slower to become interactive.