The
fleet
[FLEET_2026] — 6 SYSTEMS · 1 CLIENT PROBLEM · HUMAN AT EVERY IRREVERSIBLE STEP
One system is a demo. Six that hand off to each other — and stop for a person at the right moments — are a way to run a business. Pick a client problem and run it: watch who does what, where the gates are, and what a night costs.
▲ Simulation — a scripted run of the designed fleet. Values are targets from the mission briefs, not measurements.
CLIENT A marketplace client on a Timberwright retainer
PROBLEM Inventory in a spreadsheet, listings on the site, copy nobody re-reads, and no one watching any of it at 2 a.m.
"Can you just keep it all correct without me having to think about it?"
[OFFERINGS] — what the same six systems become when pointed at a client
Overnight operations
Nightly audit, inventory reconcile, and content checks for a client's site and systems. Every change proposed; none applied without approval. A 60-second digest each morning.
Compliance pre-review
Findings in minutes with citations to the rule, an audit log an examiner can read, and re-checks when rules change. The agent reviews; a person approves.
Customer data onboarding
Messy exports mapped to a target schema with generated transforms, checks, and lineage — re-run nightly until cutover. For the SaaS, not the end customer.
Voice front door
A phone agent that sees the real schedule and inventory, books what policy allows, hands off what it doesn't, and leaves a scored transcript of every call.
Agent control plane
Scheduled jobs, a policy gateway, and eval/cost gates, deployed in your environment — the answer to "what can it touch, what did it do, what does it cost, is it getting worse."
Agent assurance
For agents already in production: a red-team pass against the tool surface, an eval harness around the real tasks, a report with numbers, and a CI gate left behind.