Common questions about Almighty.

Almighty was created at the Special Competitive Studies Project (SCSP) hackathon by Shane Morris, Devin Hill, and Alex Curnow. It was not a Dynamo product before the hackathon. It is now engineered, deployed, and supported by Dynamo Technologies.

Exercise controllers, white cell operators, and the engineering teams supporting joint training, combined arms, and Multi-Domain Operations (MDO) exercises across DoD and the broader U.S. defense community.

A timeline tells you what happened in the order it happened. A directed acyclic graph tells you why each step happened in that order. PyRapide records each event's causal predecessors, so an electronic warfare effect that ripples into a kinetic outcome is queryable as a chain — not reconstructed by hand. The white cell sees the chain of decision, not just the chain of outcomes.

CrewAI agents — blue battalion, red Opposing Forces (OpFor), and the white cell adjudicator — use the native PyRapide connector to subscribe to the kernel DAG. As the kernel commits new causal events, agents consume the updated graph immediately and adapt their next moves against it in real time. The override gateway sits between the agent runtime and the DAG with three policy scopes; the white cell retains authority over irreversible effects.

Almighty is fielded at Technology Readiness Level 9 (TRL-9) posture. Container images are SCAP- and STIG-hardened by ACTA and pass clean against grype, trivy, and anchore. Builds emit machine-generated XML and YAML artifacts — POA&M, STIG CKL, NIST 800-53 control assessments — sized for direct CI/CD integration into ATO and continuous ATO (cATO) pipelines.

Yes. The same PyRapide kernel that runs synthetic rehearsals accepts live device telemetry through Distributed Interactive Simulation (DIS) and High-Level Architecture (HLA) adapter contracts. Capability profiles validate every action against what the device can actually do. The white cell retains override authority.

A Go reimplementation of the PyRapide kernel that ships as a single binary with an offline feed cache. It exists for hardware and firmware environments that cannot host Python. Event triggers can be written in Go, C++, or Rust for low-level integration.

Almighty container images are hardened with ACTA — the ATO readiness tool — which produces SCAP- and STIG-compliant images that pass clean against grype, trivy, and anchore scanners. ACTA emits eMASS-importable POA&M CSVs, STIG CKL XML, and NIST 800-53 control assessments as machine-readable XML and YAML on every build, sized for cATO CI/CD pipelines so an Information System Security Manager (ISSM) can fold them into Authority To Operate (ATO) workflows directly.