A

Agentic Ops

Jira ticket → orchestrated agent team → production

Hub
Standby
GEO-142

Map-first news intelligence workstation

Epic · pulled via Jira MCP · spec locked in plan.md · lead orchestrates, never writes app code

High
7Team members
0/8Jira children
0/8Playwright
TicketCurrent phase

Pipeline

Ingest the ticket, then spawn a specialist team around the spec.

Agent team

Multi-agents · lead sequences work

Swarm & orchestration

DB first, then parallel, then E2E loop
LEAD DB API LLM UI E2E OPS orchestrates only sub-agents spawn under each specialist for focused tasks

Event stream

Hooks · messages · bugs

Jira board

Child tickets move as agents complete work

Practice stack

The same toolkit used to build the project — highlighted as the pipeline reaches that layer.

Integration Tester loop

Playwright e2e runs when the stack is ready. Failures go back to the owning engineer — not the lead.

DevOps ship path

Sandbox in Docker. One start script. No paid APIs. Agents never leave the gated shell.

waiting for green e2e…