Now · Oct 11, 2026
5 client sites live2 paying clients112 real customer calls answered by Riley24 confirmed bookings35 real leads6 owners using their dashboardmeasured Oct 11, 2026, last 90 days
The machine
From the Goal Autopilot's own ledgers, which begin Jul 10, 2026 when it started recording; exported Oct 11, 2026. Counts only: no task, repository or machine names.
Autonomous attempts
Hover or tap a week.
Each bar is one week of attempts, coloured by how each ended. Stopped means a verifier, a test or a missing dependency refused it before it reached the main branch, which is the system working as designed. Attempts peaked in July (2,159) and ran 254 in October.
Why attempts stopped
Every attempt that did not land, grouped by the reason the system recorded. Only a small share needed me.
Finished, and how far it proved
Hover or tap a week.
Each finished task records the highest rung it proved: built, deployed, works (a real call went through and was checked) or fed (real data flows). Dark means the task predates that record.
Who did the work
Machine A 55% · Machine B 43% · Machine C 1% · Machine D 1% of 7,232 dispatches
Attempts by model family, and dispatches split across the 4 machines in the fleet. Minutes are wall-clock time per attempt.
One system · five receipts
Across 4 client businesses, Riley answered 112 non-test calls in a 90-day snapshot. Separately, WorkforceOS recorded 2 appointments booked by phone.
Read the stages as stronger evidence for the shared Riley system. Blue marks deployment, gold marks a production test, and green marks real use. Dates are observation dates, not live health lights.
Receipt 05 / 05 · real traffic
2 bookings
Client booking rail · observed Oct 11, 2026
Counted read-only from production Booking records; test and canary appointments were excluded.
This is a separate aggregate from the call count. It is not a caller-level conversion rate or a booking on Travis’s consulting line.
Source · WorkforceOS Booking, read-only production count
Riley offered the real open Wednesday 9:00 AM slot requested on a production call. The booking tool read WorkforceOS availability and returned the exact start time after the voice-provider field mapping was repaired.
The caller did not confirm a booking in this check.
Sep 13, 2026 · Travis consulting line · Sep 13 production call and calendar readback
Riley answered a production call on Travis’s consulting number. The call ledger and live agent readback show the published number routing to Riley’s greeting and booking tool.
A live line does not mean a real discovery call was booked through it.
Sep 13, 2026 · Travis consulting line · Sep 13 consulting-line call and agent readback
Two rapid production canary calls wrote a booking and then canceled it. The canary crossed the phone-to-WorkforceOS boundary, read back a real booking ID, and cleaned up the appointment.
One of the three rapid runs failed and paged. These were synthetic calls, not customer bookings or a current uptime reading.
Sep 15, 2026 · Travis consulting line · Sep 15 production booking canary receipt
Riley answered 112 non-test inbound calls across 4 local businesses in the 90-day snapshot. Counted read-only from production voice-call records for ice cream shop, fitness studio, landscaping company, dent and hail repair. Test, QA, canary, spam and outbound calls, our own lines, and test-looking numbers were excluded.
The count includes five calls from a client owner and some short hang-ups. Calls are not unique customers or qualified leads.
Oct 11, 2026 · 90-day snapshot · client lines · Conversos voice_calls, read-only production count
WorkforceOS recorded 2 non-test appointments booked by Riley on the phone. Counted read-only from production Booking records; test and canary appointments were excluded.
This is a separate aggregate from the call count. It is not a caller-level conversion rate or a booking on Travis’s consulting line.
Oct 11, 2026 · Client booking rail · WorkforceOS Booking, read-only production count
Aggregate snapshot measured Oct 11, 2026. The checks on Travis's line and the counts on client lines describe the shared engine across different installations; they do not trace one caller. Private call and booking records are summarized here without names.
Did it work
Every connection between my systems, how far each has proved itself, and the last 30 days of dated events.
Outcomes for clients, measured
Real customer calls Riley answered
plus 5 from the owner, not counted
Google reviews since tracking began
Counts were first recorded when tracking started, not when the work began, so these are gains since then.
Paying clients, and how each payment was verified: dent and hail repair since Sep 8 (Venmo, recorded with its invoice); landscaping company since Sep 13 (Stripe subscription, live, invoice paid). Amounts are not published.
Measured read-only from the production call, lead, booking, dashboard-activity and review records on 2026-10-11, by a script that runs daily. Excluded: anything flagged as a test, probe or canary, robocalls, outbound calls, our own phone lines, my own numbers, owners calling their own line, and test-looking names and emails. Businesses are described by trade, not named.
How far each connection has proved itself
Connections needing attention or an intentional restart
Each bar counts the connections that reached at least that level, including a connection whose current condition has since changed. Works means a check crossed the connection and read the result back; test traffic (canaries, flagged probes, my own calls) is counted separately from real use. 3 intentionally paused, 2 blocked by prerequisites, 1 with split routing. Rungs reviewed 2026-09-25; these conditions were reviewed 2026-09-27. Source: the maintained ecosystem integration registry and the ClickHouse pause receipt.
The system map
Tap a system to light up its connections; tap it again to clear.
Each dot is a system, sized by how many connections it has. Each line is a connection, coloured by the furthest it has proved itself: green is fed by real data, solid gold works with real traffic, dashed gold works on test traffic, blue is deployed, grey is built. A red ring marks a current limitation; inspect the connection for its specific condition.
TrendOS, reading the world
711,853
signals on record
Latest signal landed Oct 11. Collection is running.
TrendOS is my research engine: it collects signals from public sources and scores them. The bar shows how recently each source last delivered, as of TrendOS's last stats refresh.
The last 30 days
Each mark is one dated event, oldest on the left and today on the right. Hover a mark to see what it was. The launches and notes are listed further down.
Beyond GitHub
From the AnalyticsOS registry, refreshed hourly.
Product lifelines
Each row is one product from the AnalyticsOS registry. The thin line runs from its start to launch, the thick bar from launch to its latest commit; blue rows are still in development. Start and launch months are as registered.
The long version
Most of my attention now goes to one thing: the system that runs a local business’s website, phone, leads and bookings, sold through Local Business Factory. Client sites are live on it, Riley answers their phones, and the first clients pay for it. The numbers are measured on this page every day.
The offer is now three fixed plans instead of custom quotes, and the next job is the ads and funnel that bring owners to them. My other tools, the book engine included, now earn their place by serving those clients rather than as products of their own.
I decide what to build, set the checks each change must pass, and review what lands. AI coding agents write most of the code, which is why the commit counts run high. The outcome numbers, sites live, calls answered, bookings and owners using their dashboards, are the ones that matter.
Focus note reviewed Sep 28, 2026.
Progress
Commit counts say I was busy. This board says whether anything works. A rung only counts when the check behind it has been run.
Another owner's AI visits mine and asks it questions, each side running on its owner's own machine.
Open the doorsynthetic visitors · since Sep 23
The front door, mailbox and host all answer, and a test visit got a real reply back.
Next rung · The first real visitor. One invite is out.
An AI receptionist that answers my business number, explains the work and books calls.
Call (720) 770-2979since Sep 13
Asked for "Wednesday at 9", she found the real open slot on my calendar and offered to lock it in.
Next rung · A caller booking a real discovery call through her, start to finish.
Finds and qualifies local businesses and feeds them to the prospecting system.
Open TrendOSresearch reads · since Sep 8
Real business records from two scheduled cloud runs landed in the prospect roster.
Two separate products share events and guides without sharing a database.
since Sep 22
Verified in both directions on my machine.
Next rung · Deploying both sides.
Events, sign-in, interests and saved lists, on the phone.
Every screen works against the live production service.
Next rung · App Store approval. Review asked for more information about the app first.
The "book a call" rail on my sites. I built it instead of renting Calendly.
See the calendarsince Jul 24
Bookings write the calendar slot, the contact record and the analytics event.
Next rung · A stranger booking through it, counted.
A written enquiry on this site becomes a lead record, not an email in a pile.
Open the enquiry formsince Jul 27
A flagged test enquiry was read back from the CRM and deleted.
Next rung · A real enquiry, read back the same way.
“Fed” means real, non-test data has flowed through it. It never means revenue, and nothing on this page claims a client result. For openable demos, see the proof page.
Shipped · last 30 days
Sep 28
Sites live, real customer calls, bookings, leads and paying clients, counted daily from production records instead of typed by hand.
See the outcomesSep 23
An invite link that lets another owner's AI visit mine. The page explains itself to any assistant that lands on it.
Open the GuildSep 22
All 11 live systems on the proof page were re-requested and answered, so the page carries one verified date.
Inspect the proofSep 16
Every part of the marketing system on one page, each with the honest rung it has actually reached.
Read the systemSep 15
Why judgment is the scarce thing now that output is cheap: five skills, each with the date I learned it the hard way.
Read the argumentSep 15
Moved off the old CMS onto plain files. Only posts I wrote or approved are public; the rest stay behind a gate.
Read the notesSep 13
Calls were going unbooked because of a field-name mismatch with the voice provider. Fixed, and she now offers the exact open time you asked about.
Call herWritten · 21 field notes
Open loops
Two owners now use their dashboard on most days. Several others found it confusing at first, so the work is making it clear enough to use unaided before I ask any client for a referral.
Review came back asking for more information rather than a fix. The reply and a device recording are next, then resubmission.
Everything answers with test traffic. It proves nothing until another owner actually sends their AI through.
Not doing
There are a hundred book generators now. Its tools stay, but they earn their keep by serving local-business clients rather than as a separate product.
No video schedule. I write when something was learned the hard way, and only then.
Every "book a call" runs on the calendar I own, so the clients own their data too.
Three ways in. Or call the line and let Riley explain it first.
One week, fixed scope.
I read your page or pitch cold, rewrite it, audit every claim on it, and hand back the receipts.
See the weekScoped on a 30-minute call.
Larger or less defined work: what to build, whether it is worth building, and then building it.
Book a callMonthly plans for local businesses.
The system on this page, run for your business through Local Business Factory: site, phone, leads and bookings.
See the plans