Build Log

Voice kernel, estimate to payment, and a system-fix campaign

• voice
• payments
• booking
• comms
• factory

• •Landed the voice prompt kernel on August 24, so every spoken line comes from one assembled prompt instead of per-situation copies.
• •Shipped the estimate-to-payment flow on August 25, behind a payment-door census gate that refuses an unaccounted charge path.
• •Shipped the technician reschedule kernel on August 25, so a technician-initiated move goes through the same atomic path as any other.
• •Ran a system-fix campaign of 16 packs and 40 agents over three days, landing it on August 26.
• •Added three technician Telegram routes on August 25, turning that channel into a one-way mirror with deep links into revenue.
• •Reached August 26 with 41 bookings this month, $4,208 collected, 166 Yelp leads, and 3,965 commits in the technician app.

Refund truth and the communications rebuild

• payments
• comms
• voice
• factory
• seo

• •Landed refund truth on August 18, making a refund a fact on the ledger with exactly three writers and no second path.
• •Shipped the communications rebuild on August 21 and deployed it August 23, replacing scattered senders with one delivery spine that records every obligation.
• •Redesigned the voice experience on August 19 and 21, then started the voice prompt kernel on August 23.
• •Landed the second isolation model for parallel agents on August 19, so a spawn is fenced by the engine rather than by convention.
• •Consolidated the escalation policy on August 20 so a finished ladder stops paging the owner, pinned by a property suite over the real engine.
• •Scaled the search corpus on August 21 and 22 on top of the fact warehouse, and closed six numbered known issues on August 18 and 23.

Model strategy, the fact warehouse, and a training mode

• dispatch
• seo
• payments
• mobile
• comms

• •Landed the model strategy program on August 10 across five branches: routing, quality, portability, a model mandate, and a second Yelp evaluation.
• •Built the fact warehouse on August 12 and 14, an ingest and aggregate path that feeds page generation from stored facts rather than from prompts.
• •Shipped the Facebook and Instagram lead inbox on August 15, and a training mode for the technician app on August 13 and 16.
• •Landed tap-to-pay reliability on August 16, so a card charge and the receipt written for it cannot disagree.
• •Ran a content harvest on August 11 across hubs, titles, and media, then closed a batch of priority regressions on August 15.
• •Answered the technician app's outstanding contract requests on August 13 through the federation plane, rather than by editing the sibling repository.

The investor surface, and one truth for communications

• admin
• comms
• infra
• seo

• •Published the investor page and the deck on August 4 and 5, generated from the same figures the rest of the system reports.
• •Landed communications truth on August 6 and its read projection on August 7, so what was sent and what is owed come from one record.
• •Closed a ten-orchestrator system review on August 4 and 5, spanning dispatch, complaints, admin contracts, and database access rules.
• •Cut the merge rebuild from about fifteen minutes to under two on August 7, after profiling found one file-by-file read was ninety percent of the time.
• •Landed database and storage access hardening on August 5, and cleared a month of remediation items on August 7.
• •Enriched the error-code corpus by brand, reshaped search traffic, and stood up a model evaluation harness on August 9.

Two migrations that share a timestamp make the second one skip silently at deploy; three such pairs were found on August 5, renamed, and a uniqueness audit was added to the blocking tier.

The federation plane and contact governance

• factory
• comms
• dispatch
• seo
• booking

• •Opened the cross-repository federation plane on July 28, so work spanning the web app and the technician app is coordinated by record rather than by hand.
• •Shipped contact governance on July 28, putting every outbound ring and message under one frequency ledger, with pacing landed August 2.
• •Landed dispatch truth on July 31, giving the AI dispatch engine one state to read and one place to write it.
• •Added a search pre-gate on July 27 that refuses to publish a page the content contract has not claimed, and started the eighth content wave.
• •Generated the documentation figures from the code itself on July 28, so a stale count in a document reds the gate instead of shipping.
• •Closed July with 52 bookings, $3,866 collected, 182 Yelp leads, and 205,600 pageviews including crawler waves, with Google Ads paused since early July.

Voice language truth and the technician web surface

• voice
• mobile
• booking
• dispatch

• •Landed voice language truth on July 21 and a rebuilt system prompt on July 22, so the phone AI answers in the caller's language.
• •Served the technician surface on the web as a proxied build of the native app on July 24, so browser and phone show identical screens.
• •Shipped the autonomy contract and completion truth on July 20, then confirmation autonomy and a second pass on call intents on July 23.
• •Overhauled technician input, opened a customer voice line, and added a web session API for the technician surface on July 21.
• •Fixed the native signature contract on July 25 and closed the field-truth and estimate programs behind it.
• •Landed contract truth on July 20, pinning the response shapes the native app reads so a field cannot be renamed out from under it.

The legacy technician portal is deleted

• mobile
• dispatch
• payments
• booking
• seo

• •Deleted the legacy web technician portal on July 18, removing 270 files and about 30,000 lines; the native app is now the only technician surface.
• •Shipped the LLM cost governor on July 19, which skips the model call when nothing has changed, alongside per-task tool scoping for the dispatcher.
• •Landed temporal truth and transition authority on July 13, so a booking date resolves through one place and a status change has one owner.
• •Shipped the suppression kernel on July 15 and the payout overhaul on July 18, then earnings truth and task lifecycle on July 19.
• •Overhauled technician authentication, opened a technician chat hub, and put a 90-day warranty into the booking flow.
• •Bounded the sitemap, sped up the technician API, and closed a July backlog of known issues on July 17.

Photo reads were returning server errors on a null record and large uploads were being rejected by the host; on July 13 the read was guarded and uploads were capped just under the platform limit.

Security hardening, the voice overhaul, and a content storm

• infra
• voice
• booking
• seo
• comms

• •Landed a five-front security program on July 7: row-level database policies, input trust, object authorization, availability limits, and payment connection hardening.
• •Shipped the voice overhaul on July 8 with a rebuilt dialing path, then hardened the link between calls and customer records on July 11.
• •Landed booking truth on July 11 and parts truth on July 12, giving the booking engine and the parts lifecycle a single authoritative state each.
• •Published about 480 agent-authored articles in one content wave on July 6, then ran a backfill storm and a measurement loop behind it.
• •Shipped consent handling on July 10 and a do-not-call suppression overhaul on July 12, so an opt-out is honored by one writer everywhere.
• •Made technician confirmation, decline, and cancel atomic, and closed the reply autonomy and inbound truth programs on July 8.

The inbound response spine and the money loop

• comms
• payments
• voice
• booking
• infra

• •Landed the inbound response spine on June 30, so every inbound message carries an obligation to answer, with a sweeper that catches the ones missed.
• •Closed the money loop across five programs: held payouts, uniform commissions, treasury completion, an agreement and integrity pass, and technician earnings.
• •Unified notifications on July 2, replacing scattered send calls with one dispatch path that every booking event goes through.
• •Shipped arrival milestone tracking, parts-driven reschedule, and an overhaul of the browser tests that run before every deploy.
• •Put the voice model catalog and API key behind one source of truth, and added a synthetic probe that calls the system and grades the result.
• •Closed June with 31 bookings, $1,291 collected, 71 Yelp leads, and traffic at 60,500 pageviews, up from 10,700 in May.

One cron dispatcher, and the operator isolation model

• infra
• factory
• booking
• seo
• dispatch

• •Replaced 100 platform cron entries with one minute-tick dispatcher on June 27, fanning out from a code registry with a claim ledger and its own dashboard.
• •Landed the operator isolation model on June 23, giving each parallel line of work its own workspace and one convention for merging it back.
• •Adopted Jujutsu as the isolation substrate on June 25 after a spike proved it, and dropped the custom versioning and merge driver it replaced.
• •Moved content pages from static generation to incremental regeneration on June 28, with a post-deploy cache warmer, so a build no longer renders everything.
• •Audited and hardened technician login twice in one week, then landed booking autonomy, coherence remediation, and resilience work on June 27.
• •Wired 21 booking capabilities into the text and dispatcher channels with a parity proof, so the same action means the same thing in every channel.

Memory platform, treasury ledger, booking reliability

• dispatch
• payments
• booking
• voice
• seo

• •Landed the AI memory platform on June 15 and 16 across 19 merges: memory cells, a knowledge graph, belief and trust scoring, customer recall, and a reflector.
• •Built the treasury in four layers, the ledger, accounts, balances, and the surfaces that read them, making the ledger the source of truth for money.
• •Hardened booking reliability across availability, voice, and reassignment, adding an accept-gated handover so a job never moves to a technician who has not agreed.
• •Shipped the estimate close engine and the capability kernel, which gives every booking field exactly one writer instead of a dozen call sites.
• •Remediated blog 404s and locked the result behind a content-integrity audit and an end-to-end crawl guard on June 17.
• •Rewrote the outbound call opening and greened the deploy gate with a four-leaf test-fix batch on June 19.

The code atlas, and 28 fixes landed without a human

• factory
• booking
• comms
• infra

• •Landed about 28 autonomous fixes on June 10 across four integration branches, closing known issues in booking dispatch, delivery safety, guards, and search surfaces.
• •Built the code atlas over four waves on June 12 and 13: a symbol producer, a reference graph, dead-code evidence, duplicate detection, and a verdict ledger.
• •Made message delivery idempotent, scrubbed phone numbers out of logs, and put refunds on the ledger as facts rather than as side effects.
• •Shipped booking auto-completion in three phases on June 13 and 14, so a finished job closes itself instead of waiting on a person.
• •Started the AI memory platform on June 14 with three substrates, giving the operators recall that survives a single conversation.

Deploy uploads started failing against the hosting file endpoint; on June 9 the prebuilt archive was split into chunks and about 1GB of unused files was stripped from the build trace.

Gates turn enforcing, and the first multi-agent program

• factory
• infra
• comms
• booking
• mobile

• •Split the audit runner into gate and advisory tiers on June 1 and flipped the law backstop to blocking, so a broken law now fails the build.
• •Ran the first multi-agent program on June 4: seven phases enforcing the contract between the web app and the technician app, each with its own parity harness.
• •Shipped an AI action auditor that reads booking status changes against a generated graph, attributes each one to an actor, and remediates stale violations.
• •Made the delivery ledger the single authority for message deduplication on June 5, retiring the parallel checks that could disagree.
• •Read customer memory by contact across the Telegram, Yelp, Thumbtack, and dispatcher loaders, so every channel sees the same history.
• •Normalized customer booking statuses on June 7 with an exhaustiveness test, so the mobile list and detail views cannot drift apart.

Telemetry everywhere, and the build engine moves out

• infra
• comms
• voice
• mobile
• factory

• •Added request telemetry and action logging to about 190 admin API routes on May 27, plus structured logging to 28 previously silent endpoints.
• •Built the communication turn ledger on May 26 and 27, recording every AI turn with intent detection, gap detection, and alerting.
• •Routed every outbound call through one pipeline on May 26 and wired 12 proactive lifecycle triggers into it, with its own analytics.
• •Gated the technician finish step on all three photo categories on May 28, and opened customer mobile endpoints for bookings, profile, and token refresh.
• •Moved the build engine into its own repository on May 30 with 55 frozen contracts, separating the factory from the product it builds.
• •Closed May with 31 bookings, $3,533 collected, and 682 commits in the technician app beside the web work.

Real calls were being filed as ghost sessions when the recording pipeline lost data, and the alerts kept re-firing; seven phases of recording resilience landed May 28 and closed the loop.

Confirmation cascade and a second cron consolidation

• booking
• infra
• comms
• seo

• •Shipped the confirmation cascade on May 18: three-tier technician assignment with an offer board, separate decline and timeout paths, and owner escalation.
• •Consolidated scheduled jobs again on May 21, folding 15 entries into 4 umbrella jobs and bringing the platform count from 100 to 89.
• •Normalized phone numbers in the database with triggers on 21 columns across 17 tables, so a contact matches regardless of formatting.
• •Backfilled FAQ structured data for 665 posts and added tables of contents, four-level breadcrumbs, and density guards to the internal auto-linker.
• •Wired a shared callback tool into the text, Yelp, chat, and dispatcher operators, so a callback request means the same thing everywhere.
• •Rebuilt the map tile source on May 21 with range-verified archives and an idle-gate monitor that checks rendering at runtime.

2,961 blog posts in one week

• seo
• mobile
• voice
• factory

• •Generated and integrated 2,961 blog posts on May 16: 1,070 symptom guides, 875 repair how-tos, and 532 error-code pages.
• •Rewrote the 532 error-code posts and every brand parts page on May 17 to remove boilerplate, one brand at a time.
• •Moved the blog to incremental static regeneration with a JSON content loader, so 5,000 pages ship without a full rebuild.
• •Shipped an inline instant-call pipeline on May 16 that answers a new Yelp, Local Services, or Thumbtack lead by phone in under three seconds.
• •Superseded the Capacitor wrapper on May 13 as the native technician app took over, and retired release version tags on May 14.
• •Added an analyst role to the build engine on May 15 with acceptance-criteria parsing, and an audit that finds parallel send paths.

Nationwide content architecture, and the app goes native

• seo
• mobile
• admin
• infra

• •Laid out a nationwide content architecture on May 4 across nine phases, adding a 55-symptom taxonomy, cost guides, and a cross-linking mesh.
• •Published city profiles for 62 cities and brand-appliance guides covering 56 entries across 16 brands.
• •Cut the technician web portal over to the native app in seven migration phases on May 8, deleting the Capacitor bridge and moving push to FCM.
• •Added server-side geofencing with automatic arrival detection on May 6, so an arrival is recorded by location rather than by a button.
• •Moved map tiles onto our own delivery network with a Cloudflare Worker and a health check, replacing the hosted fallback.
• •Shipped a live fleet map for the admin panel and an AI feedback tool that asks the customer for a rating after the job.

In-app navigation and a third lead source

• mobile
• dispatch
• seo
• comms
• payments

• •Shipped in-app navigation for technicians on April 29, with turn-by-turn routing and arrival estimates instead of handing off to Apple Maps.
• •Connected Thumbtack as a lead source on April 30 with a booking sync bridge, a job status API, and its own state machine.
• •Built a Google indexing tracker across three phases, so newly published pages are submitted daily and the outcome is recorded.
• •Consolidated owner messaging into one Golden Channel feed with a message log, inline replies, and unread markers.
• •Replaced hand-wired notification calls with a declarative table that maps each booking state change to what gets sent.
• •Closed April with the first card collections of the project, $3,916 in total.

Omnichannel waves and the map switch

• comms
• infra
• seo
• admin

• •Replaced Leaflet and Google Maps rendering with MapLibre on April 25, moving map display onto an open-source stack.
• •Consolidated scheduled jobs on April 26, folding 10 weekly cleanup jobs into one dispatcher and 6 more into two, to stay under the platform's 100-job limit.
• •Shipped six omnichannel waves, adding booking tools to text messages, an inbound email operator, a supervisor persona, and cross-channel context.
• •Opened public web chat before a booking exists, so a visitor can talk to the AI without filling in a form first.
• •Expanded the Sacramento city list to 25 cities and wrote 13 module architecture documents describing how the system fits together.

The factory: agents write the code

• factory
• voice
• dispatch
• seo
• infra

• •Moved parallel agent work from shared worktrees to full isolated clones on April 14, so agents cannot see or disturb each other.
• •Shipped the three-role orchestration model with a single deploy gate on April 18; from this point every line of code is written by agents.
• •Rebuilt the dispatcher across 10 phases and released it as v12.76.0 on April 19, the highest version number the project reached.
• •Hardened the voice engine through 16 numbered phases, adding a ready connection pool, a first-audio watchdog, echo guarding, and session resumption.
• •Built document readiness across seven phases, so estimates and invoices are produced by a queue and swept for stragglers rather than by hand.
• •Ran the multi-area rollout to 15 phases, moving service pages under area paths with redirects, sitemaps, and browser tests.

The dispatcher rewrite arrived with 23 failing tests that blocked its merge, and every one was fixed before it went in on April 19.

Tap to Pay, ads intelligence, guardrails

• payments
• mobile
• comms
• booking
• seo

• •Shipped Tap to Pay on April 8, so a technician takes card payment on the phone itself with no extra hardware.
• •Added communication guardrails across four phases: a silence policy, a pre-send gate, task lifecycle rules, and tiered autonomy for the AI.
• •Built ads intelligence in stages, adding cannibalization detection, a wasted-spend detector, and margin-aware return on ad spend.
• •Split the technician work step into photos during, photos after, remaining payment, and finish, so each stage is recorded separately.
• •Shipped the Yelp lead lifecycle engine on April 11 with nine statuses, a state machine, and booking-to-lead syncing.
• •Opened a second market by expanding into Sacramento, alongside the existing Bay Area coverage.

Ads control, analytics platform, security audit

• admin
• payments
• mobile
• infra

• •Built full Google Ads management in the admin panel, covering campaigns, ad groups, keywords, ads, extensions, audiences, and conversions.
• •Shipped the analytics platform in three waves on April 5, adding session replay, click heatmaps, AI cost tracking, and A/B testing.
• •Shipped the technician campaign orchestrator across six phases on April 5, tying ad budget to technician capacity.
• •Remediated all 67 findings from a security audit across ten phases, then hardened configuration in an eleventh.
• •Added Apple Sign In and one-time phone codes to the customer app, plus commission management for technician pay.
• •Completed the legal compliance document set required for California appliance repair across all five phases.

Mobile app wrapper and a single brand

• mobile
• admin
• payments
• booking

• •Packaged the app for the mobile app stores on March 25 and added phone-and-text sign-in for technicians the next day.
• •Removed the second brand on March 25, returning the codebase to a single-brand architecture.
• •Replaced multi-button technician status handling with one linear workflow button that walks a job from arrival to payment.
• •Shipped five customer-facing PDF document types and automatic estimate generation the moment a technician writes one.
• •Cut unchecked type casts in production code from 211 to 5.
• •Opened the Operations Hub for cross-system navigation and started a Google Ads data warehouse.

Job File hub, finer zones, self-testing calls

• booking
• dispatch
• voice
• infra
• admin

• •Shipped the Job File hub on March 21, putting a booking's estimates, work photos, and documents on one screen.
• •Built a caller bot that phones the voice AI and grades the result, so calls are tested by calls.
• •Split county service areas into 22 smaller zones so dispatch matches technicians to work closer to them.
• •Closed all 36 items on the risk register and added application performance monitoring on March 17.
• •Moved technicians to a 1099 subcontractor model with business verification, an invoice template, and electronic signatures.
• •Added post-call audio review, so every finished call is transcribed and scored without a person listening to it.

Native audio voice, quiet hours, technician portal

• voice
• comms
• booking
• admin

• •Rebuilt the voice pipeline so the model hears and speaks directly on March 11, released as v11.0.0, replacing the older transcription chain.
• •Added a quiet-hours guard on March 11 so no automated call or text goes out at a time the rules prohibit.
• •Built text-message consent tracking and opt-out enforcement, so a customer who replies STOP is suppressed everywhere.
• •Opened a technician registration portal at /join and shipped the technician portal itself across eight phases.
• •Added a messaging bridge that carries technician and customer conversations in both directions through the platform.

The AI read noon and midnight as the wrong hour, and the v10.1.0 and v10.2.0 time fixes on March 10 closed it.

Voice moved in-house, AI dispatcher arrives

• voice
• dispatch
• comms
• admin

• •Replaced the outside phone vendor with an in-house voice platform on March 2, released as v8.0.0 and completed as v9.0.0.
• •Consolidated telephony onto a single carrier, removing the two earlier providers, so every call runs through one path.
• •Built a three-tier call simulator covering 32 booking scenarios across four caller personas, so voice changes get tested before customers hear them.
• •Shipped the AI dispatcher on March 8 as v10.0.0, a coordination engine that works across phone, chat, text, and Telegram.
• •Turned owner and technician Telegram control from fixed buttons into a conversation with the dispatcher.

CRM v5, operator fleet, admin redesign

• admin
• comms
• voice
• booking

• •Merged every lead source into one CRM on February 25, released as v5.0.0 with a command center page.
• •Built AI operators for email, text message, and outbound calls on shared outreach plumbing, so one contact history serves all channels.
• •Redesigned the whole admin panel on February 26, released as v6.0.0, and added a complaints center and a unified inbox.
• •Gave the phone AI and the chat AI access to each other's conversation history, so a customer never repeats themselves.
• •Rebuilt nine analytics sections on database aggregation rather than page-level queries, covering funnels, visitors, service areas, and site performance.
• •Added text-message and occupant-contact consent disclosures to the booking form.

Second brand, AI chat, and money handling

• admin
• payments
• comms
• booking
• seo

• •Extended the platform to serve a second brand from one codebase and one deployment, with brand-aware content across every page.
• •Shipped the Mercury banking dashboard and a Stripe admin dashboard on February 18, putting both money surfaces inside the admin panel.
• •Launched an AI chat operator that can call tools, running across 21 models from several providers.
• •Added customer self-service for cancel and reschedule, then fixed 11 race conditions the new flows exposed.
• •Connected Yelp leads in both directions on February 21 and put an AI operator on the replies.
• •Shipped electronic estimate documents and technician work photos, moving job paperwork into the app.

The reschedule window crashed for some customers, and error boundaries plus defensive guards in v3.74.0 closed it two days later.

Marketing, payments, and the first phone AI

• seo
• payments
• voice
• comms
• admin

• •Wired up Google Ads conversion tracking on February 10, so ad spend could be tied to actual booking submissions.
• •Published 67 local search pages for the Bay Area on February 11 and added automatic submission of new URLs to search engines.
• •Added a phone AI through an outside vendor on February 14 that answered inbound calls and logged them.
• •Turned on Stripe Connect payments and text-message notifications for bookings on February 15.
• •Built an analytics dashboard covering nine tabs and a 27-step funnel that tracks a visitor from first click to booking.

New database and the CRM refactor

• admin
• booking
• infra

• •Moved onto a new production database and brought the admin calendar in line with customer time zones.
• •Reworked the CRM and added occupant details plus email tracking to every booking record.
• •Rebuilt sign-in around auth tokens, keeping the two customer login providers cleanly separated, released as v3.18.0.
• •Fixed duplicate time slots that appeared when a customer booked several appliances at once.

Linux migration and the first big cleanup

• infra
• booking

• •Moved development off Windows to Linux on January 27, which is where every later release was built.
• •Fixed 98 places where the same data shapes were defined twice, then cleared the resulting type errors across a series of batch fixes.
• •Rebuilt scheduling on one-hour slots, replacing the older variable-length blocks, and shipped it with migration documentation on January 31.
• •Set up the first production deployment to Vercel, including end-to-end tests and rate limiting.
• •Rotated every API key after an audit found secrets referenced in configuration files, then archived 56 obsolete documents.

Bookings covering more than one appliance stopped reserving their time slots, and the v3.5.2 fix on January 27 closed it.

Availability engine rebuilt, two thirds smaller

• booking
• infra

• •Rebuilt the availability engine from scratch and cut its code by 66 percent, released as v3.0.0 on January 20.
• •Split staff sign-in from customer sign-in, giving employees their own token-based login separate from the customer Google account flow.
• •Fixed booking times that offered slots with no technician actually free, so the calendar stopped showing hours nobody could work.

The repository opens

• booking
• admin
• infra

• •Opened the repository on January 18 with the booking platform, admin panel, customer dashboard, technician portal, and CRM already in place.
• •Imported every earlier version, v1 through v2.8, as a single commit, so the public history starts at v2.8.6 rather than at zero.
• •Separated environment secrets from the repository before any further work, keeping credentials out of version control.