Machine Insights Real AI experiments

Experiment 001 · two routes live

What happens when an AI agent gets real tools, real projects—and a bill to pay?

Machine Insights is a field notebook for serious human–AI collaboration. We document the rules, decisions, evidence, costs, and results of work performed in the real world—not a demo.

  • Measurable outcomes
  • Human approval gates
  • Failures included

Live experiment

One question. Explicit rules. A result either way.

The goal is not to perform success online. The goal is to find out what is actually possible.

Running Experiment 001 30 days

Can an AI Agent Pay for Itself?

A non-engineer gave an AI coding agent a constrained objective: create enough legitimate value to cover its C$140 monthly subscription—without inventing reviews, spamming strangers, enabling paid ads, or turning the owner’s schedule into a second job. The test now has two routes, one digital product and one tightly bounded service, plus a data-driven offer pivot prepared from the first two weeks of evidence.

Open the Day-Zero report
Live Experiment 001 · Route 02 30 July 2026

New service route

Can the agent sell the work it already knows how to do?

Machine Insights opened a Fiverr service for testing and auditing vibe-coded web apps before launch. The agent prepared the positioning, packages, evidence sample, listing media, profile, and monitoring. The owner handled identity, tax, and financial verification.

Fiverr pivot live Experiment 001 · Checkpoint 02 9 August 2026

The first market verdict

The work was never tested. The offers barely entered consideration.

Fiverr produced 77 impressions and zero clicks. Etsy produced six visits in 30 days, only two from Etsy search, with three listing views and zero orders. The narrower US$15 five-bug check is now live on Fiverr; a bounded bug-fix offer and three focused Etsy products remain staged.

Field notes

Lessons must earn the right to become advice.

Some reports mature slowly. Others produce evidence within hours—even when the first evidence is adversarial noise.

Marketplaces

The First “Customers” Were Scammers

A field log from launching an AI-assisted service into a marketplace where attention is not the same thing as demand.

Read the field log

Acceptance

A Green Test Is Not a Working Product

Why passing builds and backend checks can coexist with a feature the user still cannot operate.

In evidence collection

Virtual reality

The Headset Is the Acceptance Gate

What physical testing reveals that code inspection, logs, and simulators cannot prove.

In evidence collection

Collaboration

Building Software by Conversation

How a non-engineer can control scope, quality, and recovery without pretending to read the code.

In evidence collection

Operating rules

Autonomy without theatre.

  1. 01

    Real work or no story

    Every report starts with an actual project, constraint, decision, or measurable outcome.

  2. 02

    Authority stays explicit

    The agent can research, build, test, and monitor. A human retains financial, identity, publication, and acceptance decisions.

  3. 03

    Unknown is a valid result

    We distinguish what passed, failed, was not run, or remains unknown instead of smoothing uncertainty into a success claim.

  4. 04

    Failure remains publishable

    If an experiment fails, the useful artifact is the honest postmortem—not a rewritten origin myth.

The practical side

Useful systems, not prompt theatre.

ControlTheBuild turns lessons from these experiments into plain-language guides and tools for people managing AI-built projects.