Skip to content
WilsonWorks
Menu

How a job moves through my AI team

It runs like a good crew on event day. Everyone knows the plan and their station before they start, and nothing goes out the door until someone else has checked it. Here's how one run works, from my goal to the live site.

The steps

  1. Who
    Patrick
    In
    what I want
    Out
    the goal for the run

    I say what I want in plain words, the way I'd explain it to someone on their first day.

  2. Who
    a planning session
    In
    the goal
    Out
    work orders in lanes

    The plan breaks the goal into work orders. A work order is one written job with its own test for when it's done. The orders go into lanes, and a lane is one AI builder's to-do list on one of my three machines.

  3. Who
    builder lanes
    In
    a work order
    Out
    the finished work

    The lanes work at the same time, and each job gets its own copy of the code so nobody's work collides. A separate agent writes the tests from the work order alone, before it ever sees the builder's code.

  4. Who
    the gate seat
    In
    the finished work
    Out
    passed, or sent back

    The gate is an AI checker that never builds anything itself. It grades the work against the order's own test and reads the result for itself.

  5. Who
    the gate and the builder
    In
    the reason it failed
    Out
    the fix

    A bounce means the work goes back with the reason, and the builder fixes only that. If a job bounces twice, it stops and waits for a person.

  6. Who
    the merge gate
    In
    work that passed
    Out
    the main code

    Merging means the finished work joins the main code. Only work that passed the gate gets merged.

  7. Who
    Patrick
    In
    the questions and held jobs
    Out
    my yes or no

    Questions that need me come through my fleet office, never more than three at a time, and I answer from wherever I am. Anything that goes live, deletes something or costs money waits for my ruling on that one job.

The branches

Seven branches do the work, and executive assistants pass it between them so each job reaches the team that owns it.

Meet the whole team

  • CTO · the dev team

    Builds the software. A chief engineer reviews every change, and leads for the front end, back end, database, app connections and testing each run a small crew of juniors.

  • CFO · finance

    Keeps the books, watches the cash, builds the budget and forecast, and handles tax work.

  • COO · operations

    Keeps day-to-day work on schedule and inside the rules, and looks after hiring and training.

  • CAO · writing and AI quality

    Owns the words on every page and the instructions every agent works from, and keeps AI spending in check.

  • CMO · marketing

    Shapes the brand, brings in demand, plans content and measures what's working.

  • Tax representation

    Handles IRS exams, collection cases and notices.

  • CPA attest

    Runs audits and other independent reviews that vouch for a company's numbers, walled off from the finance branch so it stays independent.

The rules

  • The agent that builds something never grades it.
  • A work order is done when its own test says so, and the result is read, never assumed.
  • Two bounces and a job stops until a person clears it.
  • Nothing gets deleted without a checked copy and my sign-off.
  • Nothing goes live and nothing gets paid for until I rule on it.