Sub-Agent Roster
The crew that built this platform. The orchestrator fanned out file-partitioned strands by discipline; each carried its own skills, owned one slice of the monorepo, and ran across the build waves. This is the roster behind the timeline.
10
Disciplines
61
Agent-runs
54
Distinct skills
12
Waves covered
Roster
One card per discipline: its charter, the area it owns, the skills it carries, and the waves it ran in.
Owns the Postgres schema, migrations, RLS, and the state-machine RPC.
Owns packages/db · supabase/migrations
Skills
Ran in
Pure, framework-free gates, readiness, ceiling, critical-path, and forecast.
Owns packages/validation-engine
Skills
Ran in
Signature product components and design tokens shared across apps.
Owns packages/ui
Skills
Ran in
Next route handlers for nodes, roles, nuggets, acks, tasks, and alerts.
Owns apps/web/app/api
Skills
Ran in
Supabase Realtime subscriptions, presence, and live-data wiring.
Owns packages/supabase · apps/web hooks
Skills
Ran in
Background jobs: notifications, escalation timers, retention, scheduler.
Owns apps/worker · packages/notifications
Skills
Ran in
Unit, integration, and E2E coverage plus perf and a11y budgets.
Owns packages/test-utils · **/__tests__ · e2e
Skills
Ran in
The tracker you are looking at: KPIs, waves, RTM, drift, and status.
Owns apps/dev-admin
Skills
Ran in
Security review, threat model, and the AI drift monitor guarding R1/R5.
Owns tools/drift-monitor · docs/security
Skills
Ran in
Monorepo rails, Docker, self-hosted Supabase, CI/CD, and release.
Owns infra · docker-compose · .github/workflows
Skills
Ran in
The roster is the cockpit's own build crew log (illustrative project-tracking state), not product data. Wave labels resolve against the build-waves timeline; disciplines with no waves yet render an empty “not yet deployed” state.