Solo dev log — building Domi, a life-management platform, in public. One sprint at a time.https://www.gailleur.com/https://www.gailleur.com/blog/domi-one-month-by-the-numbers/https://www.gailleur.com/blog/domi-one-month-by-the-numbers/A point-in-time engineering snapshot of Domi after 30 days and 30 sprints — commits, code, tests, and bilingual surface, all reproducible from git.Mon, 01 Jun 2026 13:00:00 GMThttps://www.gailleur.com/blog/sprint-1-auth-got-the-foundation-in/https://www.gailleur.com/blog/sprint-1-auth-got-the-foundation-in/Auth.js v5 magic-link works in production. Postgres row-level security is set up but doesn't enforce yet. Schema's in, the foundation just isn't bearing weight yet. Plus three things that surprised me along the way.Mon, 04 May 2026 00:00:00 GMThttps://www.gailleur.com/blog/sprint-10-the-carries-close/https://www.gailleur.com/blog/sprint-10-the-carries-close/Five PRs out, all merged, no rollovers. The M8 cost-line UI carry finally closes after three sprints; four Phase 10 launch-surface items get pulled forward in the same sprint; the --custom migration footgun gets promoted from mental note to written convention after firing four times. Plus a stale-copy bug that lived on the public landing for five sprints — caught by a screenshot review, not by any automated gate.Mon, 11 May 2026 02:30:00 GMThttps://www.gailleur.com/blog/sprint-11-paperwork-day/https://www.gailleur.com/blog/sprint-11-paperwork-day/Five issues, the legal surface, a per-day cost sparkline, a WCAG audit, the chat-roundtrip flake fix — and a project-board cleanup that surfaced the kind of process gap I'm starting to expect every sprint. Same shape as the migration footgun, the public-surface review, the post-pubDate uniqueness: rule that wasn't written down, didn't matter at low volume, surfaced once accumulation made it visible.Mon, 11 May 2026 03:30:00 GMThttps://www.gailleur.com/blog/sprint-12-the-foundation-was-imaginary/https://www.gailleur.com/blog/sprint-12-the-foundation-was-imaginary/The Sprint 12 primary was supposed to be a UI on top of an audit log. The pre-kickoff scope check found that the audit log didn't exist — 11 sprints of a non-negotiable convention with zero code backing it. Re-scoped to build the infrastructure, deferred the UI to S13. Plus a partition-routing PostgreSQL footgun that only fires when the grant is too restrictive.Tue, 12 May 2026 02:30:00 GMThttps://www.gailleur.com/blog/sprint-13-the-read-side-and-what-protects-it/https://www.gailleur.com/blog/sprint-13-the-read-side-and-what-protects-it/S12 built the audit infrastructure that should have existed for 11 sprints. S13 put the read UI on top of it, finished the largest withAudit wiring, unblocked graph-viz with a spec doc, and — almost as an afterthought — wrote down the catalog of automatable invariants that 13 sprints of building had been implicit about. The audit story closes as a pair; the regression catalog formalizes what was always there.Wed, 13 May 2026 02:30:00 GMThttps://www.gailleur.com/blog/sprint-14-promoting-convention-to-code/https://www.gailleur.com/blog/sprint-14-promoting-convention-to-code/Four PRs in one push. The audit story closes structurally — every domain mutation goes through withAudit. Two regression-suite backlog items shipped as CI gates rather than written rules. The knowledge-graph viz lands end-to-end from spec to implemented route. The through-line: written conventions that have bitten the pipeline finally graduate into code that fails before the violation costs anything.Wed, 13 May 2026 03:45:00 GMThttps://www.gailleur.com/blog/sprint-15-the-graph-fills-in/https://www.gailleur.com/blog/sprint-15-the-graph-fills-in/S14 shipped the knowledge-graph viz with empty-state copy promising 'tell Domi in chat or upload a document — your graph fills in.' Then JF asked: how does that actually work? It didn't. S15 closes the gap: chat_proposals infrastructure + propose_member + propose_asset + confirm-then-write gate. After this sprint the graph viz's empty-state is a real promise, not a hopeful one.Wed, 13 May 2026 14:30:00 GMThttps://www.gailleur.com/blog/sprint-16-the-trio-closes/https://www.gailleur.com/blog/sprint-16-the-trio-closes/Sprint 16 started as a four-tier plan, pivoted mid-sprint to API docs after JF asked for the OpenAPI inventory, then came back to the original plan and shipped all of it. Four PRs: API docs primary, escalation regression fix, propose_task (the third and final chat-driven create surface), UserPill on graph + settings. After S16 the chat-driven create trio (member, asset, task) is structurally complete. Also: tool-selection on a 10-tool catalog is meaningfully more sensitive than at 9.Fri, 15 May 2026 02:30:00 GMThttps://www.gailleur.com/blog/sprint-17-the-loop-closes-on-itself/https://www.gailleur.com/blog/sprint-17-the-loop-closes-on-itself/Sprint 17 shipped three PRs in a single evening: tasks list UI primary (the read side of the chat-driven create loop S15/S16 built), escalation eval stabilized at 10 tools after a first-attempt fix-one-break-another, and an API-docs CI gate that caught real drift on its first run. After S17 the chat-creates → /tasks-shows → complete-from-row loop works end-to-end. Also: prompt prefixes beat per-tool description tightening when the catalog grows.Fri, 15 May 2026 03:55:00 GMThttps://www.gailleur.com/blog/sprint-18-the-mobile-unblock-and-a-v1-5-that-wasnt/https://www.gailleur.com/blog/sprint-18-the-mobile-unblock-and-a-v1-5-that-wasnt/Sprint 18 shipped five PRs in one evening: camera capture in chat (the dogfood-defining mobile feature that's been carrying forward since S12), four regression-suite hardening PRs that closed half the open backlog, and one V1.5 feature pulled forward into V1 because the punt's framing had been wrong all along. Plus: when a research subagent's summary contradicts its own findings, trust the findings.Fri, 15 May 2026 06:00:00 GMThttps://www.gailleur.com/blog/sprint-19-v1-5-is-a-smell/https://www.gailleur.com/blog/sprint-19-v1-5-is-a-smell/Sprint 19 shipped seven PRs in one evening. Three of them were V1.5 features pulled forward into V1 — and each one turned out smaller than the V1.5 framing implied. Plus: two regression-suite probes both caught real bugs on their first runs, including one the S17 PR description had explicitly claimed didn't exist.Sat, 16 May 2026 00:00:00 GMThttps://www.gailleur.com/blog/sprint-2-three-sprints-in-three-days/https://www.gailleur.com/blog/sprint-2-three-sprints-in-three-days/Two milestones substantively closed in one sprint. RLS enforcing in production. The first real eval matrix says 5/5 pass on Haiku 4.5 for $0.0026. The schedule I scoped 72 hours ago is already wrong.Tue, 05 May 2026 13:00:00 GMThttps://www.gailleur.com/blog/sprint-20-dropping-the-matrix/https://www.gailleur.com/blog/sprint-20-dropping-the-matrix/Sprint 20 was the brand pivot. Domi's Matrix-on-dark hacker-tool aesthetic shipped to JF in S5; ten sprints of dogfood-shaping later, JF asked for something that 'provides confidence to the user' instead. Seven PRs landed: design tokens + theme picker, full visual rework, Claude-style sidebar with multi-thread chat, mobile drawer, edit/archive members + assets, /documents browse page, and the cross-tenant doc-type proposals queue.Sat, 16 May 2026 06:00:00 GMThttps://www.gailleur.com/blog/sprint-21-a-green-ci-that-was-lying/https://www.gailleur.com/blog/sprint-21-a-green-ci-that-was-lying/Sprint 21's headline wasn't a feature — it was finally making the real-database integration suites run in CI instead of only on my laptop. The gate went live and immediately caught a prod incident, two latent test bugs, and an RLS bypass in the harness itself. Plus: Law 25 self-serve account deletion, many-to-many asset custodians, admin index, and a db-state-sync pre-merge gate.Tue, 19 May 2026 02:00:00 GMThttps://www.gailleur.com/blog/sprint-22-the-model-catches-up/https://www.gailleur.com/blog/sprint-22-the-model-catches-up/Four PRs in two days shipped the Family Life Entity Model v0.2: a cross-tenant kind_registry pattern plus three new top-level entities (obligations, contacts, transactions). The household model now matches what a household actually has. The structural lessons earned in S21 — pre-merge gates, audit-then-mutate, per-file test UUIDs — paid out as zero rework on the foundations and zero failed deploys.Tue, 19 May 2026 03:00:00 GMThttps://www.gailleur.com/blog/sprint-23-the-curation-surface/https://www.gailleur.com/blog/sprint-23-the-curation-surface/Phase C of the Family Life Entity Model landed: the /admin/kinds catalog where the platform admin can see and curate every classification across the data model — edit display names, promote tenant-tier kinds to builtin, mark dead ones deprecated. Four PRs (two planned, two hardening), 8 new tests, and a V1.5 follow-up filed for the cross-tenant audit attribution that this sprint deliberately deferred.Tue, 19 May 2026 03:15:00 GMThttps://www.gailleur.com/blog/sprint-24-the-asset-that-knows-itself/https://www.gailleur.com/blog/sprint-24-the-asset-that-knows-itself/Four PRs lit up the kind_registry + attributes_schema pattern on the original V1 asset table. JF's Mazda CX-5 now knows it's leased through 2029, has a VIN and a Quebec plate, has the registration PDF attached, has Alice as a custodian, and shows the photo JF snapped in the garage. The plumbing was built across S22 and S23; S24 wired it to the asset table the way S22 wired it to obligations, contacts, and transactions.Tue, 19 May 2026 03:30:00 GMThttps://www.gailleur.com/blog/sprint-25-the-architecture-holds/https://www.gailleur.com/blog/sprint-25-the-architecture-holds/Forty-seven product PRs in seven days. Dogfood week 1 produced a flood of screenshot-and-fix loops, every one of them closing a friction point JF could name. The test of the V1 ramp wasn't whether the architecture survived being designed; it's whether it survives being used. It did — every PR reused a shape from a prior sprint, nothing got refactored, no PR got reverted.Tue, 26 May 2026 03:30:00 GMThttps://www.gailleur.com/blog/sprint-26-the-loop-measures-itself/https://www.gailleur.com/blog/sprint-26-the-loop-measures-itself/Seven PRs in one day. Speed Insights wired, perf script + week-1 numbers shipped, chat-route cost telemetry plugged (the gap that was understating COS by an order of magnitude), and four more dogfood papercuts smoothed. Both perf-side V1 success criteria PASS week one — but only because the measurement got honest in the same sprint.Tue, 26 May 2026 03:55:00 GMThttps://www.gailleur.com/blog/sprint-27-the-proactive-layer-wakes-up/https://www.gailleur.com/blog/sprint-27-the-proactive-layer-wakes-up/22 PRs over four days. The predict_task LLM role landed end-to-end in two callsites (document ingest + daily cron) with eval CI gating the prompt. Predictions now accumulate automatically at a per-tenant cadence the user picks. The V1 paperwork (threat model + PIA + DR runbook) got reconciled against shipped reality instead of v0.1 speculation. Plus chat-grounding that makes the assistant feel like it actually accumulates memory of the household.Fri, 29 May 2026 03:55:00 GMThttps://www.gailleur.com/blog/sprint-28-the-feature-was-already-built/https://www.gailleur.com/blog/sprint-28-the-feature-was-already-built/I sat down to build the sprint's headline feature — insurance that covers multiple assets — and found it already shipped. Schema, write path, detail UI, graph edges, settings, help docs: all there. My own working memory said it was unstarted, and described the wrong design. The real gap was one layer down: the chat could write the coverage links but couldn't read them back. Plus a Briefing surface that learned to write you a weekly brief, soft-delete finally rounded out across the graph, Sentry wired so dogfood 500s leave a stack trace instead of a screenshot, and a late, small catch that mirrored the big one — the asset 'level' I shipped as a two-way class turned out to need real depth: a pool is level 2, the heat pump bolted to it is level 3.Sun, 31 May 2026 02:00:00 GMThttps://www.gailleur.com/blog/sprint-29-the-app-audits-itself/https://www.gailleur.com/blog/sprint-29-the-app-audits-itself/Killing the 4 MB upload wall with presigned direct-to-R2 uploads, and pointing 21 agents at the codebase to grade it against the AI-engineering book.Mon, 01 Jun 2026 00:00:00 GMThttps://www.gailleur.com/blog/sprint-3-the-document-loop-closes/https://www.gailleur.com/blog/sprint-3-the-document-loop-closes/M3 done end to end: upload → R2 → vision-extract → confidence-gated auto-write into the canonical graph, all eval-baselined. Five for five on the first extract_document run on Sonnet 4.6 for $0.04. Four sprints in three calendar days.Tue, 05 May 2026 22:00:00 GMThttps://www.gailleur.com/blog/sprint-30-the-migration-that-lied/https://www.gailleur.com/blog/sprint-30-the-migration-that-lied/A single-day jumbo sprint to ship the top-8 of the self-audit roadmap — prompt-injection fencing, a versioned prompt catalog, an end-to-end eval bucket — and the migration that printed 'applied successfully' twice while running zero DDL.Mon, 01 Jun 2026 01:00:00 GMThttps://www.gailleur.com/blog/sprint-31-a-month-old-and-a-major-behind/https://www.gailleur.com/blog/sprint-31-a-month-old-and-a-major-behind/An enabler sprint with no new features: a SQL-injection CVE in the ORM, the discovery that nothing was watching dependencies at all, and then the real surprise — a one-month-old codebase that already needed dozens of major version bumps. 45 PRs merged, ~80 triaged.Tue, 02 Jun 2026 13:00:00 GMThttps://www.gailleur.com/blog/sprint-32-the-dogfood-writes-the-backlog/https://www.gailleur.com/blog/sprint-32-the-dogfood-writes-the-backlog/I stopped planning and started living in the app. Ten PRs later — richer tasks, list pages for assets and members, a chat-table fix, a configurable briefing — and a realization: the best roadmap input is just using the thing. Then I stepped back and wrote the roadmap the app had been dictating to me.Wed, 03 Jun 2026 22:00:00 GMThttps://www.gailleur.com/blog/sprint-4-the-engine-fires/https://www.gailleur.com/blog/sprint-4-the-engine-fires/M4 done end to end on the seasonal_window schedule kind. Quebec winter-tire law turns into a task in the database, with full provenance back to the regulated rule that produced it. Five sprints in five days.Thu, 07 May 2026 00:00:00 GMThttps://www.gailleur.com/blog/sprint-5-5-the-polish-round/https://www.gailleur.com/blog/sprint-5-5-the-polish-round/A mini-sprint between 5 and 6 to close the gap between 'feature shipped' and 'feature feels like a product'. Nine PRs in six hours, driven by a user-flow spec that landed mid-Sprint-5 and named everything that wasn't yet done.Thu, 07 May 2026 03:30:00 GMThttps://www.gailleur.com/blog/sprint-5-the-cash-out/https://www.gailleur.com/blog/sprint-5-the-cash-out/domiapp.ai went from 'static welcome page' to 'real product' this sprint. Magic-link signin, household onboarding, a streaming chat that knows about your tasks, documents, and predictions, file uploads, EN↔FR switcher, locale-pinned replies. 0.039 to grade the whole chat surface end to end.Thu, 07 May 2026 02:00:00 GMThttps://www.gailleur.com/blog/sprint-6-making-the-cash-out-durable/https://www.gailleur.com/blog/sprint-6-making-the-cash-out-durable/M6 closes Settings + persistence. Six PRs across two evenings, the first sprint where multiple PRs ran in parallel against shared foundations, and a small set of merge-friction lessons that came with that. The chat surface now persists, the user-pill 'Settings' link goes somewhere real, and the bootstrap-DB cheat retires from the read path.Sat, 09 May 2026 02:00:00 GMThttps://www.gailleur.com/blog/sprint-7-depth-on-demand/https://www.gailleur.com/blog/sprint-7-depth-on-demand/Chat-to-plan escalation. Five PRs across two evenings, the LLM abstraction's role layer earns its keep, and the chat surface goes from 'cheap and grounded' to 'cheap and grounded by default, deep when the user asks for depth.' 17 of 17 eval fixtures pass on Sonnet 4.6 — including the four that explicitly mustn't escalate.Sat, 09 May 2026 03:00:00 GMThttps://www.gailleur.com/blog/sprint-8-the-abstraction-holds/https://www.gailleur.com/blog/sprint-8-the-abstraction-holds/Five PRs, one second provider, one cross-provider eval matrix demo. OpenAI ran the same 17 chat fixtures with the same prompts and tools as Anthropic at 94% accuracy and 52% the cost. The role-routed LLM abstraction that was scaffolded in Sprint 2 finally got tested for real, and it passed.Sun, 10 May 2026 02:00:00 GMThttps://www.gailleur.com/blog/sprint-9-the-inbox-surfaces-the-gaps/https://www.gailleur.com/blog/sprint-9-the-inbox-surfaces-the-gaps/Five planned issues ship the email connector. Live testing within the same sprint surfaces three more things worth fixing — forwarded emails were silently skipped, the allowlist catalog needed real Quebec coverage (28 → 227 entries), the chat surface needed slash commands so the catalog is discoverable. Using a thing tells you what's missing in a way no spec can.Sun, 10 May 2026 03:30:00 GMThttps://www.gailleur.com/blog/why-im-building-domi/https://www.gailleur.com/blog/why-im-building-domi/The cognitive load of running a household isn't a productivity problem. It's a knowledge problem. Here's what I'm building, and how, and why now.Sun, 03 May 2026 00:00:00 GMT