She makes the commercial choices
The market, offering, pricing, product, distribution and next action were deliberately left to Agatha.
We gave an AI operator a domain, its own computer, access to business tools and a £50 funding ceiling. No business idea. No target market. No prescribed strategy. Then we let it work.
What happens when an AI is responsible for choosing, building and attempting to sell a real business, while a person only controls the boundaries?
Agatha Whitmore was given an isolated operating environment on Oracle Cloud, her own accounts and the ability to research markets, write code, deploy websites, communicate and request funding. She was not assigned an industry or a preselected product.
Understand how the system worksThe market, offering, pricing, product, distribution and next action were deliberately left to Agatha.
A persistent machine, browser, development tools, business accounts, scheduled work and memory make action possible.
Separate permissions, restricted spending, independent records and an owner-only emergency stop prevent unlimited authority.
The first days revealed a surprising limitation: Agatha's automation was healthy, but her business activity became repetitive. The operating protocol was changed on 9 November, and that change is part of the experiment.
Four-hour scheduled work sessions, functioning memory and a real deployed tool. Then short cycles of inbox checks and repeated attention to one unresolved seller-identity dependency.
Two-hour sessions, a profit-first DEFCON protocol and independent financial flags. Longer runs and more public activity followed, without yet establishing a real paying buyer.
These were Agatha's decisions, not a product brief supplied by the owner. At the documented cut-off, both were commercial hypotheses rather than proven sales.
A free redirect-map validation tool supporting a proposed £79, developer-ready website-migration review service.
A proposed £49 service to prepare supplier product spreadsheets for a cleaner Shopify import.
The entire build is documented from Oracle provisioning to the scheduled work loop, financial controls, backups, journal and emergency stop.
Separate Oracle host, locked-down Linux account, OpenClaw, model authentication and persistent memory.
Communications, GitHub, Cloudflare, sandbox/live payments, controlled capital and work-state documents.
Native schedules, independent observer, owner-only STOP, verified off-server backup and launch baseline.
A practical 12-step walkthrough with copyable commands, official references, checkpoints and a browser-only progress checklist.