Decide it. Prove it. Account for it.
Three platforms on one loop. Each takes a stretch of the same problem and hands the next a decision somebody can check — and each leaves the same kind of record behind: inputs, tools called, outputs, and the name of the person who signed for it.
UEI UKELB3UV76V6 · CAGE 19S89
The operating system for space wargaming and BMC3I
Space wargaming and BMC3I simulation built for the next decade of contested orbital operations. High-fidelity orbital mechanics (Orekit) and distributed adversarial AI turn raw space data into repeatable, defensible courses of action.
A working body of orbital simulation, instrumented for battle management, command, control, communications, and intelligence. Every number traces to a physics-engine output — and every operator commit is recorded.
The v9 operator console carries the grammar trained operators already read: control groups on hotkeys, a command card of every legal order, resources that force tradeoffs and refuse an order over budget, a decision clock, and a red cell that plays at machine speed. Gold is decision, cyan is telemetry, red is lethal and nothing else.
Multi-actor scenarios with adversarial AI, stochastic event modeling, and human-in-the-loop branches for defensible course-of-action validation.
Native interfaces to the battle-management and command-and-control architecture, with standards-aligned data formats and decision-loop outputs scored against measures (MOMs/MOEs/MOPs).
AI-assisted analysis. Every operator commit is recorded, so the record is the audit trail.
Edge to core, and back.
Five domains sense at the edge — the domain space. One hybrid layer, designed to tolerate denied, disrupted, intermittent, and limited (DDIL) links, carries it to the core — the information and decision space. There, threat becomes measured courses of action (MOMs · MOEs · MOPs), verified by an operator, and battle management, command, control, communications, and intelligence (BMC3I) is pushed back to the edge at the speed the threat level demands.
Battle management, command, control, communications, intelligence — pushed back into the domain space. The threat level decides who acts and how fast.
- Who acts
- Core deliberates · commander commits
- Latency
- Hours → days
- What moves
- Updated TT&P · re-plan · retasking
- Who acts
- Core pushes ranked COAs · operator verifies
- Latency
- Minutes
- What moves
- COAs with probability of success · tasking
- Who acts
- Edge acts on pre-authorized response matrix
- Latency
- Seconds · near-real-time sensor-to-COA
- What moves
- Effects · then report to core
TT&P = tactics, techniques & procedures · COA = course of action · Core = information / decision space · Edge = domain space. Print boards: Master flow · Latency curve · Domain lanes. Measured results are shared in briefings.
Sources: USSPACECOM FY29–33 IPL · DAF FY27 RDT&E · JP 3-60 · AFRL Small Satellite Portfolio hybrid-architecture concept · HYPATIUS platform directives. Curve shapes illustrative.
ALIDADE
We do not guess. We engineer the win.
Capture decision intelligence for GovCon. Seven cited factors resolve into one probability of win, in three bands, with the gaps named — the colour is calculated, never chosen, and a mark and a word ride with it.
Teaming runs on consent: a partner is a handle until both sides agree to be named, and what each side can see is written down as a grant before the first message. Every tool an agent calls is attributable to a person, a grant and a scope. The run ledger is the product.
Built for delivery as an MCP tool server your agents call — in STARCHITECT, in your own client, or in the ALIDADE console.
CRATON
DCAA-ready timekeeping and the SF 1408 binder
Timekeeping, charge codes, indirect rate pools and the audit binder for small government contractors. At launch CRATON keeps the four things a cost-type award asks you to prove, in one append-only ledger anyone can read.
Book the day whole, in quarter-hour increments, with nobody approving their own week. Nothing is charged without a code, and the code derives from the funding source. Fringe, overhead and G&A pools update when the ledger does. The binder is generated from the ledger on the day it is asked for, not assembled the night before.
The fourteen areas of the SF 1408 decide whether a small firm may hold a cost-type award at all. The last of them asks whether the system is in full operation — a compliant package nobody uses fails it. That question is CRATON's home screen.
How the three compose.
The loop closes. What the record settles is what the next decision gets argued from — a debrief sharpens the next probability of win, a rate snapshot prices the next bid, a sortie changes what the next scenario has to survive.
Space wargaming and BMC3I simulation — courses of action a commander can take apart under a clock.
Detail →Capture decision intelligence — seven cited factors and one probability of win a bid board can source.
Detail →Hours, codes, rates and the SF 1408 binder — an append-only record an auditor can read.
Detail →