Competency 02 — AI Factories

AI Factories

Harley Factory: multi-model orchestration, agents and production pipelines, with independent review before anything ships.

Business job: Turn complex software delivery into controlled, reviewable execution.

  • Multi-model orchestration
  • Governed AI workflows
  • Agents
  • Production pipelines
Intent → lanes → review → verify → releaseWork orderWO-114Acceptanceexercised at runtimereviewed by a second personreview record kepttestsruntime readbackread at runtimeArchitecture boundaryOrchestratorbounded tasksArchitectFrontendBackendDataReviewQABrowserchange #4186 files · reviewableIndependent reviewsecond reviewerfinding FF-7 routed backrework before releasecorrectionfinding applied · re-testedIntent → reviewed release.

Scroll: intent enters, lanes run, a finding comes back.

Owner intentA request arrives as a work order, not a prompt

Flagship film · 30 s · intent to release

  • 00–09 intent, scope and architecture
  • 09–23 lanes run; a finding returns to the author
  • 23–30 the change is checked, released, handed over
HA-FILM · 30s · 1920×1080 · 30 fps — Intent → verified release.

Systems in operation

Working structures behind the competency.

  • 01

    Product factory control

    25 controlled stages

    Owner intent → architecture → specialist work → acceptance → assurance

  • 02

    Independent release gates

    Readiness is never inferred

    Adversarial review → QA → security → runtime → staging → acceptance

  • 03

    Owner-controlled execution

    External actions stay gated

    Decision → permission → bounded execution → readback → retained state

How the factory runs

  • 01

    Work orders are decomposed into bounded tasks with named owners.

  • 02

    An independent reviewer can return a change to its author before it ships.

  • 03

    Release waits until the change has been exercised and passes its check.

Technical details
  • Models, tools and agents are routed per lane, so one task can use several without losing the work order.
  • The review lane is staffed by a reviewer other than the author of the change.
  • Runtime behaviour is exercised before a change reaches release.

Surfaces shown: website-native SVG, Canvas and native-ratio campaign media.

Have a system that needs shipping discipline?

Build