A causal event engine, not a simulation framework.

Almighty did not exist as a Dynamo product before the Special Competitive Studies Project (SCSP) hackathon. It was built there, in a single working session, by Shane Morris, Devin Hill, and Alex Curnow — to answer a question exercise controllers and white cell operators kept asking about every wargame and live-fire rotation: not what happened, but why it happened in that order.

The kernel is a tenant- and scenario-namespaced wrapper around PyRapide, the Python implementation of Stanford's RAPIDE causal event architecture. Every event lands in a directed acyclic graph (DAG) with its causal predecessors recorded — a sensor return, the electronic warfare cone that triggered it, the commander order that authorized response. Reading the graph gives the white cell the chain of decision, not a timeline of outcomes.

CrewAI agents — blue battalion, red Opposing Forces (OpFor), and the white cell adjudicator — use the native PyRapide connector to adapt and react to those DAGs in real time. As the kernel commits new events, agents consume the updated causal graph immediately and reorder their next moves against it. Officer interfaces validate every action against capability profiles before commit. The override gateway sits between agents and the DAG with three policy scopes; the white cell retains authority over everything irreversible.

Almighty does not replace the human in the loop. It clarifies what the human is in the loop for.