Skip to content

Factory Operating OS vs. Domain Execution Separation Standard

Prime Directive

BLUCITY MUST NOT KNOW HOW TO BUILD DRUPAL.
DRUPALWORKS MUST NOT KNOW HOW TO RUN THE BLUEFLY FACTORY.

The Separation, Stated Once

BluCity defines how the Bluefly Factory operates; BluCity-Packs defines how reusable capabilities are composed and configured; DrupalWorks defines how modern Drupal work is performed; BluCity-Docs defines the knowledge and policy those systems follow.

That sentence is the settled separation. Where any other document, table, or agent context disagrees with it, this sentence wins and the other document is corrected. Two consequences follow, and both have been got wrong before:

  1. Reusable Factory capabilities do not live in BluCity. A composition, overlay, or packaged configuration that more than one rig or product consumes belongs in BluCity-Packs. BluCity runs the Factory; it is not the shelf the reusable parts sit on. A capability that has only one consumer stays in that consumer's repository until a second consumer proves it reusable.
  2. Policy text does not live in the system it governs. The rule, standard, or playbook is written in BluCity-Docs; BluCity, BluCity-Packs and DrupalWorks reference it and enforce it. A system that carries its own copy of the rule has created a second authority, which the documentation governance standard prohibits.

System Responsibilities & Scope Boundaries

System Owns & Manages Prohibited Scope
Gas City Upstream orchestration runtime and six core primitives (Agent, Bead, Formula, Rig, Pack, Event). Bluefly-specific business logic or domain framework code.
BluCity How the Bluefly Factory operates: governance execution, lifecycle, work routing, agent coordination, health, recovery, GitLab delivery, cross-rig behaviour, Factory runtime policy as configured and run. Domain-specific execution (mol-drupal-*, SDC compilation, Canvas migrate); reusable capability compositions, which belong to BluCity-Packs; the normative text of any standard, which belongs to BluCity-Docs.
DrupalWorks How modern Drupal work is performed: Drupal-specific execution knowledge and reusable Drupal workflows (CMS, Canvas, SDC, Drupal AI, ECA, FlowDrop, Automator). Factory orchestration rules (session lifecycle, Bead claiming, MR lifecycle, release train).
BluCity-Packs How reusable capabilities are composed and configured: Bluefly compositions, overlays, packaged configuration and packaged policy bundles consumed by more than one rig or product. Direct product source code; the normative text of the policy a bundle enforces.
BluCity-Docs The knowledge and policy those systems follow: canonical Bluefly engineering standards, rules, playbooks, reference, decision records and evidence. Execution code, workspace-local state, or runtime configuration that a running system reads.
Beads / Dolt Durable work authority and issue state. Volatile ephemeral chat history.
GitLab Source control, CI/CD pipelines, Merge Requests, releases, chain of custody. Direct agent execution loop.

The deployment-layer expression of this same boundary — which repository owns host provisioning, which owns containers, which owns Factory configuration, which owns packaged composition, and where secret values may live — is production-deployment-law.md §11. The documentation-layer expression — what belongs centrally, what stays project-local, and what belongs in .agents/context/ — is documentation-governance-standard.md §8.

Agent Persona Responsibilities

  • BLU: Factory Coordinator (Mountain/Convoy visibility, agent workload, cross-agent coordination, human-gate aggregation).
  • MAYOR: Work Authority & Runtime Coordinator (Beads health, work routing, dependency graph, session capacity).
  • REFINERY: Source & Delivery Lifecycle (branches, worktrees, GitLab MRs, pipelines, release branch).
  • WITNESS: Independent Verification (acceptance, runtime proof, definition of done, evidence sufficiency).
  • HARBORMASTER: Knowledge & Context Governance (BluCity-Docs curation, project context, authority mapping).
  • FOUNDRY: Reusable Capability Builder (Packs, Formulas, Orders, Skills, upstream reuse).
  • SENTINEL: Security & Policy (secret handling, credential exposure, authorization boundaries).
  • OPENCLAW: Communications & Event Transport (message routing, external notification adapters).