The Almighty stack is organized into four tiers — Renderer, Orchestration, Agents, and Kernel — with cross-cutting concerns for tenant isolation, the unclassified banner, the override policy plane, and the live PyRapide-to-CZML adapter. The integration grid below lists the thirteen components that span these tiers.
Sensor / Effector / Mover / Communicator / Commander officers can only emit verbs and parameter ranges declared on their immutable capability profile. Out-of-range orders are rejected before commit.
// Example: Sensor officer emits a radar fan
sensor.detect({
family: "radar_fan",
range_m: 32000, // validated against profile
bearing_deg: 184,
});Per-event always wins. Per-agent-per-turn beats per-turn. The default is review — an empty policy table means everything pauses for white cell decision.
// Example: white cell override on a kinetic engagement
gateway.policy({
scope: "per-event",
match: { verb: "engage", family: "indirect_fire" },
action: "review",
});Each (tenant_id, scenario_id) pair gets its own Poset. Cross-namespace leakage is structurally impossible. Replay rebuilds a fresh DAG from the per-tenant Postgres up to any turn N.
// Example: causal predecessors recorded with the event
kernel.commit({
tenant_id: "1ad-jrtc",
scenario_id: "rotation-24-04",
event: e,
causedBy: [e_radar, e_jamming],
});3D Cesium-based theater render with capability-gated CZML overlays for radar fans, EW cones, jamming circles, and indirect fire arcs.
Exercise controller workstation. Live DAG view, per-event override authoring, override-scope priority indicator.
Multi-tenant orchestrator. Tenant and scenario registry, role-based access control, JSON Web Token (JWT) issuance with tenant_id binding.
Intercepts agent-emitted events between officer-interface tools and DAG commit. Three scopes, strict priority, default-to-review.
Tenant- and scenario-namespaced causal DAG. In-memory Posets partitioned per (tenant_id, scenario_id) with no shared event store.
System of record for committed events. AAR replay rebuilds a fresh DAG up to turn N from this table; the in-memory kernel does not persist.
Per-tenant VPC subnet, RDS instance, S3 bucket, and KMS key. No shared infrastructure across tenants.
ATO readiness tool. SCAP- and STIG-hardened images that pass clean against grype, trivy, and anchore. Emits POA&M, STIG CKL, and NIST 800-53 artifacts as machine-generated XML + YAML for ATO and continuous ATO (cATO) CI/CD pipelines.
Blue, red OpFor, and white cell adjudicator crews. Each agent uses the native PyRapide connector to subscribe to the kernel DAG and adapts its next moves in real time as new causal events commit.
Distributed Interactive Simulation and High-Level Architecture adapter contracts for live device telemetry into the kernel DAG.
Single-binary Go variant of the kernel for on-device DAG execution where Python cannot run. Offline feed cache included.
Tenant-filtered event delivery to renderer surfaces. Stress-tested at four concurrent tenants with zero cross-talk required.
Deterministic re-walk of PyRapide from durable storage. Exports PDFs with the unclassified banner reproduced on every page.
Source is at github.com/Dynamo-Technologies/almighty. The glossary at docs/glossary.md is the canonical reference for officer types, effect families, echelons, tiers, and override scopes. All marketing copy on this site links back to it.