What is built, and what it is waiting for.
Seven components take a website from invisible to bookable. Three are built and tested. Four are specified and have not been started, and none of them starts on a date. They start when a number clears a line.
01The pipeline
Seven components, in the only order they work in.
The order is not negotiable: nothing can be routed before it is verified, and nothing can be verified before it has been mapped. That is why the built parts are the ones at the front. The tracker sits outside the chain and only counts who arrives.
| Component | What it does | What exists today | Status |
|---|---|---|---|
| Scanner | Scores any site out of 100 and names what is blocking an agent. | Built and tested. Fifteen Sydney sites scored, reports published. | Scanner: Available |
| Mapper | Opens the site in a real browser and writes down every action it finds. | Built and tested. It produced both numbers in the next section. | Mapper: Available |
| Tracker | One line of script that counts the agents arriving at a site. | Built and tested. The collector is live and no site has installed it. | Tracker: Available |
| Gateway | Publishes a business’s actions where agents look for them. | Specified as doc 03’s Runtime component. No code in this repo. | Gateway: In development |
| Verifier | The owner approves each action and sets its limits before it can run. | Specified. No code in this repo, and nothing can run without it. | Verifier: In development |
| Router | Lands a completed booking in the software the business already runs. | Specified. No integration with any vendor is built, and none is a partner. | Router: In development |
| Ledger | Meters and bills per verified completed action. | Specified. Nothing is billable and there is no customer. | Ledger: In development |
02Measured, not asserted
Two numbers decide whether the rest gets built.
Both come from one run over the same fifteen sites. One clears its gate and one does not, and they are printed the same size.
- 73.3%
- Mappability. Eleven of fifteen sites produced a complete action map.
- 73.1%
- Execution success. Nineteen of twenty-six conclusive sandbox fills were accepted.
Three ratios, because one of them alone would flatter us.
The same run yields 73.1% across conclusive fills on mapped actions (19 of 26), 59.4% across all thirty-two attempts on those actions, and 76.7% across conclusive fills on every form we touched (23 of 30). All three are published so none can be quoted without the others.
03Against the gates
Where each of the four tracked numbers stands.
Mappability: clears the line.
Eleven of fifteen at a go line of 70% and a kill line of 50%. That experiment is decided and the kill condition is not triggered.
Execution success: does not.
Seventy-three against a gate of ninety. All seven failures were a CAPTCHA answer field or a consent tick, and none was our own data being rejected.
Agent traffic: unmeasured.
The collector is live and no site has installed it, so the sixty-day clock has not started. Unmeasured is not the same as zero and we will not print it as one.
Committed partners: zero.
That one is measured, and it is genuinely zero. No agency, no business, no vendor.
04How we test ourselves
We filled forms on fifteen businesses and submitted none of them.
Then audited every request that left the browser to prove it, and published the ledger per site.
- 81
- Sandbox form fills across fifteen businesses we have never spoken to.
- 629
- Submission attempts neutralised before they could leave the browser.
- 5,449
- Outbound requests audited during those runs.
- 0
- Carried a value we typed.
What that last number does and does not say.
Most of those 5,449 requests did reach those businesses, because they are the sites’ own images, fonts and scripts loading normally. The claim worth making is the narrow one: not one request carrying a value we typed reached any of them, and we submitted nothing.
05Why the other four have not started
Half the build is switched off on purpose.
The four unbuilt components are not late. They are gated, and this is the gate.
The workstreams are recorded as dormant.
Doc 06 scopes eleven workstreams and switches on six. The four behind the hosted layer are dormant until the go call, and that is written down rather than improvised.
One number decides it.
Execution success is below its gate. Building a hosted layer on top of a fill rate that misses ninety would be building on a number we do not believe yet.
No component ships to a live site without a flag.
Nothing reaches a real business except behind a per-site switch with instant rollback, and no action of any kind runs against a business that has not verified it.
Start here
The two you can use today are free.
The scan and the traffic tracker. The mapper is ours rather than yours, and the other four are not built. Start with what exists.