Signature system
The agentic engineering OS
A 50+ agent pipeline that plans, implements, audits, verifies, and releases — with reliability guardrails and host-resource governance.
The multi-agent system behind bretmcgee.com and my independent engineering work. It runs continuously, orchestrating autonomous coding agents across a strict-TypeScript monorepo with real-services quality gates.
Agent work is governed like production infrastructure — explicit handoffs, audit checkpoints, and automated verification on every change before merge.
Agent OS · Pipeline
Online
Execution
Pipeline phases
Five phases map to the agent graph. Each has a dedicated role and explicit entry/exit criteria.
01 · Plan
Translate intent into scoped, verifiable work.
A planner agent scopes features with clear acceptance criteria, dependency order, and disclosure constraints. Long-horizon decisions are recorded in a ledger so context persists across sessions.
02 · Implement
Parallel specialist agents execute in isolated scopes.
Domain specialists — UI, API, tests, infra — work concurrently within guardrails: strict TypeScript, lint gates, and provider-agnostic LLM routing. Subagent monitoring tracks progress and host-resource usage.
03 · Audit
Independent review before code is trusted.
An auditor agent checks diffs against standards: type safety, accessibility, disclosure policy, and architectural fit. Findings block progression until resolved — no silent drift.
04 · Test
Verify against real services, not mocks.
Integration and unit tests run against real APIs and backends where possible. Lint, typecheck, and test gates must pass before the pipeline advances.
05 · Ship
Integrate changes, commit, and deploy with full traceability.
A synthesizer agent reconciles agent outputs, prepares commits, and hands off to CI/CD. Every merge records what changed, why, and which gates cleared.
Constraints
Production guardrails
Throughput only matters if output is trustworthy.
- GATE-01
Host-resource governance
Caps on concurrent agents, memory, and run duration keep orchestration from destabilizing the dev environment.
- GATE-02
Disclosure-aware output
Public copy, résumé bullets, and case studies pass automated scans — client names and sensitive metrics stay gated until reviewed.
- GATE-03
Reduced-motion paths
Visual pipeline motifs degrade to accessible text lists under prefers-reduced-motion — motion never carries essential information.
- GATE-04
Zero-any TypeScript
Strict typing across the monorepo; agents inherit the same standards as human contributors.
Kernel idea
Capability mediation
Allow, deny, or hold for approval — denials refuse the request instead of silently downgrading.
Agents request capabilities; a mediator allows, denies, or holds for approval. Denials refuse the request — they do not quietly weaken into a lesser grant.
Audit log empty — request a capability above.
At scale
Fifty-plus orchestrated subagents run in production daily. Throughput and methodology are documented on the about page.