Handbook

Factory Droid Integration

Not the same as Forge Dark Factory. Factory Droid is a third-party implementation workcell that proposes patches. Forge Dark Factory is Forge's own PoC autonomous coding loop (see Bounded execution examples). Both emit…

Updated

Not the same as Forge Dark Factory. Factory Droid is a third-party implementation workcell that proposes patches. Forge Dark Factory is Forge's own PoC autonomous coding loop (see Bounded execution examples). Both emit reviewable changes; neither decides acceptance.

Positioning

Factory Droid is an implementation workcell.

Factory owns:

  • codebase analysis,
  • implementation proposals,
  • code review,
  • patch generation.

Factory does not own:

  • Forge governance,
  • final approval,
  • evidence system of record,
  • production execution.

Factory Droid governed lane

How Factory Droid proposes patches while Forge retains verification, evidence, and human approval.

  1. Lenses creates WorkcellRequestLenses shapes intent into a bounded WorkcellRequest for Factory Droid.
  2. Fleet runs Factory Droid in controlled modeFleet executes Factory Droid as a containerized workcell with operator boundaries.
  3. Factory emits WorkcellResultFactory Droid returns analysis, review notes, or proposed patches as structured output.
  4. LCDL verifies output against launch packLCDL checks whether the result satisfies launch-pack contracts and schemas.
  5. Lenses displays evidence and approval decisionLenses presents verification evidence and captures the human acceptance decision.

First templates

  • factory_droid_readonly
  • factory_droid_patch_proposal

Rule

Factory may produce patches. Lenses decides whether the output is accepted, and LCDL can verify whether the output satisfies the launch pack.