dirtyloops 2.2 · Codex + Pi

Control plane,
not choreography.

Planning decides what should be built. Dirtyloops compiles the accepted plan into portable durable state, binds it explicitly to Codex or Pi, and executes only through certified current capabilities.

Beads canonicalCodex defaultvanilla Pi baselinetransactional conversionversion-blind adapters

The three-part seam

PlanningInvestigate, compare designs, resolve consequential decisions, and accept a decision-complete, implementation-open plan.
dirtyloops create [profile] [harness]Compile Beads and portable phase contracts. Omitted profile means adaptive; omitted harness means Codex.
dirtyloops runEnforce adaptive or orchestrator-callback ownership, then generate helper missions from evidence.

The harness seam

Portable core

Accepted intent, Beads, phase docs, review, CI, and closeout contain no product-generation routing.

Codex

The default binding uses only first-party capabilities actually callable in the current surface. Missing child capabilities mean direct work or a blocker.

Pi

The bundled vanilla adapter owns durable sessions and mutation. Plugins are optional, exact-handshake accelerators.

Stable ownership profiles, adaptive missions

Dirtyloops guarantees

  • explicit schema-valid harness and profile
  • adaptive or mandatory orchestrator-callback ownership
  • Beads authority and accepted intent
  • one owner per mutable checkout
  • independent review and terminal CI state
  • one evidence-rich turn doc per phase

Stage owners choose

  • evidence-driven helper missions
  • an available model and reasoning effort
  • active concurrency within configured/runtime capacity
  • up to 20 useful helper missions per stage
  • coordination details and wave structure
  • when evidence requires a revised strategy

The orchestration brief

{
  "phase_issue_id": "example-1",
  "risk": "medium",
  "execution_profile": "orchestrator-callback",
  "strategy": "hybrid",
  "implementation_owner": "separate callback-bound owner",
  "review_independence": "fresh reviewer context",
  "delegation_plan": ["map integration seams", "challenge failure handling"],
  "model_and_effort_rationale": "strong synthesis, bounded scouts",
  "required_evidence": ["targeted tests", "typecheck", "review"]
}

The brief makes the decision inspectable without freezing it. When evidence changes, the orchestrator revises the strategy and records why.

Harness conversion

dirtyloops convert pi and dirtyloops convert codex change only generated harness state at an idle ownership boundary. The transaction archives, writes atomically, updates Beads, verifies protected hashes, and rolls back on failure.

Plan validation

Outcome

Every phase changes something observable and independently verifiable.

Intent

Constraints, settled decisions, open questions, scope, and non-goals are explicit.

Evidence

Acceptance evidence, quality gates, dependencies, and replanning triggers are concrete.

Version 1 migration

dirtyloops update preserves an explicit orchestrator-callback workflow as an ownership profile, defaults other historical loops to adaptive, and removes fixed helper-role, reasoning, and swarm choreography.