Skip to content
onemanopsJoin the Skool community
onemanops — pipeline floor · night shift
A 3D factory floor at night: the Course Builder pipeline as a lane of machines — green status lamps on running stations, red lamps at the human gates — with six more pipeline lanes receding into the dark.

A 3D map of 7 real pipelines — Course Builder, YouTube Factory, Website Dev, Instagram Growth, Competitor Watch, Deep Research, Research Wiki — totalling 50 stations and 16 human gates. Every lane, station, and gate is listed with its description in the pipeline directory section below.

Live map, rendered from real data

One person runs this AI factory. This is its real pipeline floor.

Skills, agents, and workflows assembled into pipelines that ship content, courses, and client work. Green means the line is running. Red means a human signs off.

Join the Skool communityFree to join — runbooks, build logs, and the operator inside. For founders and operators who don't write code.

On this floor, red means a human acts — this button is yours.

7 public pipelines on the floor — every lane in the directory

How the floor works

Skills become agents. Agents become workflows. Workflows run as pipelines.

Every machine on the floor is a tool I built and run daily: a skill does one job well, agents chain skills with judgment, and workflows run whole pipelines end to end — the same lines producing the videos, courses, and client work this site points at.

The map above isn't an illustration. It renders from the same files the pipeline runner reads, through one curation pass so the names read in plain English. When the floor changes, the map changes. One of the lanes up there — Website Dev — is the pipeline that built this page.

Node detailin production

Course judge

Pipeline
Course Builder — research wiki → outline → lessons → judge → published course
Does
Scores the course against its wiki — coverage, grounding, pedagogy — and blocks packaging until it passes.
Upstream
Assessment builder
Downstream
Course packager — the shipped course file
Nearest gate
human gate Outline approval — the operator signs the curriculum before a single lesson is written.

rendered from PIPELINES.md — the same file the pipeline runner reads
topology real · names rewritten for a public audience · derived 2026-07-06

Built in, not bolted on

Guardrails are how the factory is built, not a service tier

Approval gates, blast-radius limits, and audit trails run in every lane by construction. The red lamps on the map are real stops: nothing publishes, prices, or deploys until a human says so.

Separate rooms, separate keys.

Every tool runs in its own space with only the access its job needs. If one breaks, the others keep running — one problem stays one problem.

A human holds every switch.

The gates on the floor are real: drafts wait for approval, publishing defaults to dry-run, and deploys wait for a word. The tools draft; a person decides.

Everything leaves a trail.

Each run writes its result and the operator's next step to plain files on disk — documentation you can read, not a dashboard you have to trust.

The floor, in text

Every lane, every station, every gate

The same map, readable without a pointer: 7 pipelines, 50 stations, 16 human gates — a curated public subset of the factory's pipeline map, topology as declared.

Course Builderresearch wiki → outline → lessons → judge → published course9 stations · 4 gates
  1. Demand gatehuman gateNo course gets built until a human validates real demand for it.
  2. Curriculum outlinerDerives the course outline from the research wiki and its playbook.
  3. Outline approvalhuman gateThe operator signs the curriculum before a single lesson is written.
  4. Lesson writerWrites each lesson with every claim cited back to the wiki.
  5. Assessment builderBuilds each module's quiz from the written lessons.
  6. Course judgejudgeScores the course against its wiki — coverage, grounding, pedagogy — and blocks packaging until it passes.
  7. Course packagerAssembles the judged course into one polished course file.
  8. Community exporterPreps the finished course for publishing in the community.
  9. Launch-kit builderDrafts the launch comms — every outward action stays an operator checkbox.
  10. Publish approvalhuman gateThe operator prices, publishes, and posts the comms; nothing goes live on its own.
  11. Metrics exporthuman gateThe operator exports the launch numbers by hand — results are read, never scraped.
  12. Sales analystTurns launch numbers into a ledger verdict and signals for the next course.
  13. Run recorderWrites the run's result and the operator's next step to disk.
YouTube Factorychannel blueprint → scripts → four judges → finished videos8 stations · 5 gates
  1. Channel deconstructorReverse-engineers a winning channel into the blueprint every generator targets.
  2. Blueprint approvalhuman gateThe operator signs the channel blueprint before generation starts.
  3. Title & topic generatorGenerates and shortlists titles and topics against the blueprint.
    Script generatorWrites the video script to the blueprint's formula, in the house voice.
  4. Outline approvalhuman gateThe operator approves the script outline before the full script is written.
  5. Title judgejudgeScores every title against the blueprint before anything moves on.
    Hook judgejudgeScores the opening hooks — weak openers stop here.
    Thumbnail judgejudgeScores thumbnail concepts for click-worthiness and honesty.
    Script judgejudgeScores the full script for structure, voice, and retention.
  6. Voice-over recordinghuman gateThe operator records the voice-over — the human voice stays human.
  7. ProducerTurns the approved script into the finished video package.
  8. Spend & final cuthuman gateThe operator approves the render spend and reviews the final cut.
  9. Manual publishhuman gateThe operator publishes by hand; nothing uploads itself.
Website Devinterview → brief → directions → build → verify — the lane that shipped this page12 stations · 4 gates
  1. Intake strategistInterviews the operator into a validated site brief.
  2. Reference scraperPulls the loved and hated reference sites for teardown.
    Design teardownReads how each reference site is actually built.
    SEO auditorAudits the live site's search standing before anything changes.
    Competitive scanReads the landscape the new site has to stand out in.
  3. Brief approvalhuman gateThe operator signs the site brief before any design starts.
  4. Direction designerProposes distinct visual directions the operator can open and feel.
  5. Direction judgejudgeScores every direction against the brief; a human still picks.
  6. Direction pickhuman gateThe operator picks the winning direction by taste.
  7. Site builderOne builder realizes the picked direction across the whole site.
  8. Data sign-offhuman gateThe operator approves everything the site may show before any deploy.
  9. Verify gatesjudgeAdversarial checks: performance, accessibility, design fidelity, conversion.
  10. Fix passFixes what the verify gates flagged; the gates re-run.
  11. Ship decisionhuman gateNothing deploys to production without the operator's word.
  12. Retro writerWrites the cycle's lessons back into the pipeline.
  13. Run recorderWrites the run's result and the operator's next step to disk.
Instagram Growthblog post → draft → verify → human approval → publish5 stations · 3 gates
  1. Trend analystReads what's working on Instagram right now.
    Performance analystTurns our own post metrics into next-cycle lessons.
  2. StrategistPlans the cycle: which post to repurpose, what format, what angle.
  3. Post creatorDrafts caption, slides, and image directions from the source post.
  4. Draft verifierjudgeFresh-eyes gate: grounded in the source, on-voice, not a repeat.
  5. Draft approvalhuman gateThe operator approves every post before it can be published.
  6. Publish switchhuman gatePublishing runs dry by default; a human flips it live.
  7. Metrics pullhuman gateThe operator pulls the numbers that teach the next cycle.
Competitor Watchcompetitor feeds → outliers → ranked content queue7 stations · 0 gates
  1. YouTube watcherPulls competitor channels' recent numbers.
    Instagram watcherPulls competitor accounts' recent post data.
  2. Outlier detectorFlags posts overperforming their own account's baseline.
  3. Replicability judgejudgeScores each outlier: is it worth making our own version?
  4. Dashboard rendererRenders the outlier dashboard the operator reviews.
    Topic queue builderTurns approved outliers into a ranked content queue.
  5. Run recorderWrites the run's result and the operator's next step to disk.
Deep Researchopen question → verified answer → playbook3 stations · 0 gates
  1. Subject mapperMaps a field's real masters into a wiki and a judge-gated playbook.
  2. Deep researcherFans out searches, cross-examines sources, returns a cited report.
  3. Repo deconstructorTakes an unfamiliar codebase apart into an architecture map.
Research Wikiraw sources → structured, cross-linked knowledge6 stations · 0 gates
  1. Wiki scaffolderStarts a new research wiki from the house template.
  2. Topic researcherResearches a topic into vetted, staged sources.
    Batch ingesterTurns a whole reading list into wiki pages in one run.
  3. Source ingesterConverts each source into structured, cross-linked pages.
  4. Wiki analystAnswers questions from the wiki and files the analysis back.
    Wiki auditorjudgeHealth-checks the wiki for contradictions, stale claims, and gaps.

curated public subset — private client and persona lanes are excluded, never disguised · derived from PIPELINES.md + AUTOMATION.json on 2026-07-06

Join the Skool community

Workshop notes

Read how tools like these get built and used

The blog is the factory's paper trail — what shipped, what broke, and what it costs to run.

AI Agents That Improve Their Own Instructions: The Karpathy Loop for Skill Files

How agents can rewrite their own skill files, test the result, and keep only what performs better.

Why Your Vibe-Coded App Breaks — and What Actually Works for Non-Technical Builders

AI-generated code fails in ways you can’t fix by describing the fix. What holds up instead.

Build Your First AI Agent With No Code

A plain-English starting point: what an agent is, what to hand it first, and where the limits are.

Everything this factory ships lands in the community first.

Why a community instead of a sales call? Because the runbooks, the build logs, and the pipelines you just toured are posted there as they ship. Free to join, no card required.

Join the Skool community

Want the operator, not the room? info@onemanops.com