The Apex Engine
The Apex Engine is the autonomous control layer behind Justice Apex. It runs continuous test cycles, routes work to the right agents, triggers Technician-driven repairs, and keeps the whole system in a known-good state – without constant human babysitting.
What the engine does today
Full test coverage passes
The engine now passes all core tests: orchestrator run, CLI invoke runner, runner confidence score, coverage visualizer, and global runner sanity. When something regresses, Apex and Technician work together to patch it.
Self-healing & repair loop
Apex watches logs for failing commands or orchestrator calls, hands problematic cases to Technician, applies safe patches, and re-runs tests. Sandbox and fragile components are isolated and protected.
Cloud + local coordination
The engine coordinates local runners with a deployed orchestrator on Google Cloud Run, giving Justice Apex a hybrid model: fast local iteration plus cloud-backed, production style workflows for demos and clients.
How agents plug in
Every agent connects to the Apex Engine through a simple contract: mission briefs, configuration files, and structured logs. Apex is responsible for routing work, enforcing health checks, and making sure each agent behaves like part of a single system—not a pile of scripts.
- Agent Jade – website generation, landing pages, and template systems.
- Agent Lumi – banners, diagrams, and visual assets for brands and decks.
- Technician Apex – embedded repair agent for code, tests, and runners.
- Defintel, Compliance, and future data agents plug into the same engine.