<!-- GENERATED by tools/gen-md-twins.py from dark-factory.html. The HTML page is authoritative; if this file disagrees with it, this file is stale. -->
# Dark Factory Kits — The Method Behind the Gate | OneDroid

> Open skills, patterns and verification gates for governed, test-first, evidence-gated development with AI agents — the written method OneDroid Argus enforces.

Canonical: https://onedroid.ai/dark-factory

OneDroid

Dark Factory Toolkit

# Autonomous delivery
you can audit.

The kits are the method OneDroid Argus enforces. Argus is the gate;
this is what the gate is checking against, written down and free to read before you
talk to anyone. How Argus applies it.

Skills, patterns, and verification gates for running governed development loops
with AI agents — mission in, verified software out. Agents do the work;
evidence, not self-reports, decides what ships.

Read the method on GitHub
Help me implement this

Everything here is open source under Apache-2.0 — the method, the skills, the
enforcement hooks. There is no paid tier and nothing is held back. What we sell is
help making it work inside your organisation.

mission → design → build → verify → ship

evidence log
illustrative

The principle

## Trust evidence, not agents.

An agent reporting "done, all tests passing" is a claim, not a fact. In a dark
factory loop, every hand-off carries the evidence to prove it — test output,
diffs, exit codes — and an independent verifier tries to refute it before the
work moves forward. Work that fails the gate goes back. Nothing ships on
someone's word, including the machine's.

What's in the toolkit

## The loop, as reusable parts.

### Stage skills

Product owner, architect, test-first developer, QA — each stage of the
loop as a skill any capable agent harness can run.

### Verification gates

Adversarial review patterns that check the evidence for each claim —
the gate validates proof, never redoes the work.

### Test-first discipline

Acceptance criteria become a failing test list before code is written.
Green means done; the tests never get weakened to pass.

### Dispatch patterns

Fan work out to parallel sub-agents as explicit promises with defined
evidence, and verify what comes back.

### Autonomy policy

A simple decision model for what agents decide alone, what they log,
and what always stops for a human.

### Harness-agnostic

Works with any agent runtime that can follow instructions and run
commands — no proprietary orchestrator required.

## Take the tools. The hard part is adoption.

Read it, disagree with it, take it — you owe us nothing for any of it. But a method
is not a delivery capability. Getting this running against real repositories, real
pipelines and a real compliance posture is where the work is, and it is the part we
do for a living. If that is the problem you have, tell us what you're building.

Help me implement this
The method, open source

We reply within one business day. If your mail client doesn't open, the address is
michal@onedroid.ai.
