Skip to main content

Changelog

What has been built on the DomeCommand platform. This is R&D in simulation, roughly a 70% proof of concept, with a human on the trigger. Nothing here has been fielded or deployed. The versions are a narrative sequence over real development, anchored on the platform_v1 baseline.

v1.4.0, 2026-07-20​

Autonomy modes and click-to-surveil tasking reached the console, alongside three more simulated fusion sensors. Multi-hypothesis tracking began, phase A: a k-best assignment engine and independent-group gating. Live track-id churn dropped after removing an over-eager deletion rule. Phase A is a start. The later phases are still spec, not code.

v1.3.0, 2026-07-16​

Fusion became honest math. A Kalman-filter estimator core with line-of-sight noise, an interacting-multiple-model tracker for hover, cruise, and maneuver, a simulated thermal sensor with radar-cued convergence, and per-platform bias estimation. The planner learned to ask first: plans are authored, reviewed, and require operator approval before any auto-execute. The review is a model in the loop with a human approving each step, not an autonomous authority.

v1.2.0, 2026-07-14​

Sensor fusion was rebuilt around three questions: does this exist, what is it, and whose is it. Kinematics alone can never make something hostile. Honest per-sensor simulation models, a Contacts surface with standard fused symbology, and a decision queue. A fusion audit then fact-checked the design doc and corrected two of its own conclusions.

v1.1.0, 2026-07-12​

The v3 rewrite. A typed domain, a server and database backend, a live decision loop, and natural-language scenario creation. A behavior-tree DSL for assets and threats, with comms-degradation predicates: the machinery for a system engineered to survive lost links. The coordinate loop here is simulated, not on-mesh.

v1.0.0, 2026-07-01 (platform_v1)​

The unified command-and-control baseline. A full rewrite into a single C2 platform, with a Rust server and a sensor-simulator backend.

Earlier, May to June 2026​

The pre-1.0 foundation. Initial scenarios and the first backend, a counter-UAS demo integration with signals ingestion, polygon geofences, and a clean routes-and-services split.