Roles

The distinct roles that make up Dark Factory -- Coach, Architect, Development, Validation, Security, and Orchestration.

Dark Factory’s work is divided across distinct roles, each with its own contract, authority, and boundaries, so that no single role creates, approves, validates, and deploys the same piece of work. The roles are:

  • Architect — interprets approved requirements into an architecture and an implementation plan, and sizes each iteration of that plan to a single, reviewable scope. Its plan is what a human approves at a gate before development begins.
  • Developer — implements one iteration’s assigned chunk against the approved plan, writing tests alongside the code, and reports what changed, why, and how it was verified locally. It does not approve or validate its own work.
  • Validator — independently checks the Developer’s output against the iteration’s acceptance criteria, in a separate context from the one that produced it.
  • Security — independently reviews the same output for the excluded-content and sensitive-infrastructure constraints, including a mandatory redaction check against the full diff. A single confirmed instance of a prohibited detail fails the iteration.
  • Orchestration — the layer that moves work between the roles above: assigning chunks, sequencing stages, and enforcing that each handoff carries its evidence. In Phase 1 this was substantially a human stepping in by hand; the runner and orchestration machinery it would run on are being built, and this site describes them only as proposed or in progress, not as an operating system.
  • Coach / Observer — a feedback loop outside the build itself: it observes how a delivery is going — which steps stalled, which review found a real gap — and improves the process for the next delivery. The Journal records concrete Phase 1 instances of this loop, including a review that failed on its first attempt and was revised before approval.

What a human continues to do is the part no role here takes: retaining final approval authority at every gate, confirming what counts as done, and making the decisions the process is designed to surface rather than hide.

How the method these roles follow is shaped — specification first, gated phases, early architectural validation — is on the Method page.