Skip to content

Engineering Rig

The Engineering Rig is an automated development system that takes GitHub issues from backlog to production with minimal human intervention.

Based on the Tablez "How We Work" methodology.

Current Status

Component Status Docs
Conductor-E (Discord bot) Running conductor-e-docs.pages.dev
Conductor-E API (event store) Running conductor-e-docs.pages.dev/api
Coordination Cron (5 min) Running Syncs GitHub → event store
PostgreSQL (Marten) Running Event store database
FluxCD GitOps Running rig-gitops
Review-E Running (Pi4-02) Existing agent
Dev-E Not yet built Next step

Agents

Agent Role Summary
Conductor-E Coordinator Discord bot + event store API. Cron every 5 min syncs GitHub issues. 26 GitHub MCP tools.
Dev-E Developer Owns an issue end-to-end: implement → PR → iterate on review → deploy → verify. (Planned)
Review-E Reviewer Reviews every PR independently. Separate from Dev-E — the agent that produces cannot approve.
Monitor-E Monitor Watches production 24/7. Detects incidents, creates issues. (Phase 3)
Architect-E Architect Analyzes production data + feedback, proposes improvements. (Phase 4)

Architecture

All agents run on Automate-E — shared runtime, character.json config, no agent-specific code.

Conductor-E = Automate-E instance (Discord bot + GitHub MCP) + .NET 10 API (Marten event store, Clean Architecture).

┌──────────────── conductor-e namespace (Dell k3s) ──────────────┐
│                                                                 │
│  Automate-E ──HTTP──▶ Conductor-E API ──▶ PostgreSQL (Marten)  │
│  (Discord bot)        (.NET 10)            (event store)        │
│  + GitHub MCP         Clean Architecture                        │
│  + Cron (5 min)       39 tests                                  │
│                                                                 │
└─────────────────────────────────────────────────────────────────┘

Event Store

PostgreSQL-based event sourcing using Marten. 20 event types covering the full issue lifecycle. See Event Store.

Every 5 minutes, the coordination cron:

  1. Checks event store health
  2. Searches GitHub for agent-ready issues
  3. Syncs new issues as ISSUE_APPROVED events
  4. Posts summary to Discord #conductor-e

Priority

  1. Critical — production bugs (interrupt current work)
  2. High priorityhigh-priority label
  3. Normal — everything else
  4. Tie-breaker — oldest first

Escalation

Two strikes then human. First AGENT_STUCK → reassign to another agent with fresh branch. Second AGENT_STUCK on same issue → escalate to CTO via Discord #admin.

Rollback is never automatic. Always a CTO decision.

Human Gates

Trigger Detection
Authentication / session code CODEOWNERS + file path matching
Payment processing CODEOWNERS + file path matching
Database schema changes Migration file detection
Data deletion logic File path + keyword matching
New third-party dependencies Package file diff detection

30-minute Discord reminders. 4-hour escalation.

Phases

Phase What Status
1 — The Rig Conductor-E, Review-E, Event Store, coordination cron Running
1b — Dev-E Dev-E agent on Automate-E, receives assignments Next
2 — Going Live Production deployment, release pipeline, smoke tests Planned
3 — Monitor Monitor-E 24/7, incident auto-response, production data Planned
4 — Flywheel Architect-E proposes features from production data → humans approve → Conductor-E assigns Planned

Infrastructure

Resource Value
Host Dell k3s cluster (100.95.212.93 via Tailscale)
Namespace conductor-e
GitOps FluxCD via Stig-Johnny/rig-gitops
Event Store PostgreSQL 16 with Marten 8.x
LLM Auth 1-year Max subscription OAuth token
Discord #conductor-e (1489032262711251068)

Repos

Repo Purpose
conductor-e .NET API (event store, Clean Architecture)
automate-e Shared agent runtime (Discord/Slack, character config)
rig-gitops FluxCD manifests for Dell k3s

Naming

Tablez Term Our Implementation
Conductor Conductor-E (evolved from ATL-E)
Dev Agent Dev-E (planned)
Review Agent Review-E (existing)
Monitor Agent Monitor-E (Phase 3)
Architect Agent Architect-E (Phase 4)
Ops Agent Ops-E (not yet planned)