Warden Automatons

Warden Automatons (https://warden.autos) is a multi-agent executive command center and orchestration framework. Instead of micromanaging isolated coding agents or drowning in bloated chat threads, a founder briefs a single AI Chief of Staff (@warden), which governs a structured hierarchy of specialized agents across engineering, product, infrastructure, security, and growth. The Genesis, From Internal Studio Tooling to Commercial Demand: After exiting my previous startup, I started my fourth venture: an interactive entertainment and spatial computing studio shipping concurrent titles across XR (VR/AR) and mobile. Building multi-title games exposes a major gap in today's AI tools: core rendering pipelines, cross-platform SDKs, netcode, and backend services are shared across repositories, yet every AI coding session starts with organizational amnesia. I was spending hours manually syncing architectural constraints, API contracts, and sprint context across projects. To solve this, I initially built agenticMD (https://github.com/sma1692/agenticMD), a zero-dependency, folder-based Markdown harness to parallelize multi-agent tasks inside a repository. It worked out of the box, but living inside flat files made it a local power-user hack. When we shared agenticMD with fellow founders, demand was immediate across two segments: - Deep-tech and API infrastructure teams aligning multi-service architectures, security gates, and DevOps across repositories. - Service and consumer businesses (wellness and yoga studio operators) automating recurring technical SEO, Answer Engine Optimization (AEO), content, and bizdev ops. After piloting agenticMD, two businesses committed to becoming paying customers once we packaged it into a centralized cloud product. This hackathon was the catalyst to turn that folder harness into Warden: a Postgres-backed Control Plane and real-time React Command Center. Core Technical Architecture: - Code-Enforced Bottom-Heavy Token Pyramid: Warden enforces a strict runtime firewall in code (tierPolicy.ts). @warden (<=1,500 tokens/turn) and Level 0 executives (@cto, @cmo, @cbo, <=4,000 tokens/turn) cannot read raw source files. They dispatch @reader_scout agents for 150-word symbol digests, formulate plans, and fan out bounded file-edit shards to sandboxed Level 2 specialists (@frontend_dev, @backend_dev, @infra_jr, @sec_auditor). - Hybrid Institutional Memory (PostgreSQL + pgvector): Merges deterministic SQL state (sprints, architecture docs, pinned CEO decisions) with 768-dim vector + keyword recall. - Verification & Omnichannel Surface: Ships a React 19 + WebSocket dashboard, automated SEO/AEO auditing (/llms.txt and JSON-LD generation), Docker sandboxes gated by headless Playwright + WebGL QA, and a jailed local daemon (warden-link). - Roadmap: Section 11 of our README.md details upcoming Git/CI connectors, social publishing boards, company-brain ingestion (Notion, Linear, Slack), BYO-cloud deployers, and team multitenancy.