Roadmap

What works today, what we're building now, and what comes next, in order. The path runs from decision support, through augmentation, to automation.

Working today

The spectrum record

SFAF and SFAFx import with sources, markings and sealed sets, proven on 124k master reference records.

Engineering

ITM, link budgets, coverage plots, intermod, look angles, geodesy, UTM and MGRS.

Assignment and PACE

Frequency assignment with HiGHS, PACE checking and closure, and the PACE board.

Decision sheets

Sheets running natively on GRIPS, in dependency order, with invalid sheets refused. They include PACE triggers and alternate-frequency choices.

PACE on the clock

The time bar drives the rule engine's clock. The PACE sheet fires on it, an interference report moves a net, and the PACE board gives each move's reason. A degraded feed is shown to you.

The live spectrum

A receive-only SDR's waterfall arrives over the data network into the Spectrum tab, on the same clock, labelled uncalibrated. Coverage plots use a colour scale you can read by lightness, with a colour bar on the globe.

Synthetic values marked

Every value carries its source, and a synthetic value is marked synthetic wherever it's shown.

Goals and plans

Goals with measures, a plan you approve, and the Goals tab.

The application

The globe over local maps; the Graph, Whiteboard, Time and Goals tabs; weather, markups, pin grouping, the exercise clock, markings and screenshots.

Commands and the assistant

119 commands with undo, the EMSO script, and the assistant asking first or acting while you watch.

Trazore

Exchanges, installations, facilities and imagery loaded, and the Halcyon hurricane-relief set.

Building now

Halcyon running end to end with PACE and the optimizer, ready to demonstrate.
PACE commands made faster on a full exercise.
The assistant's view in the application: what it's doing, what it's waiting on, and what you've let it do.
Proof at scale: queries and validation over the 124k master reference records, and the engineering checked against reference results.
Decision sheets in the SFAFx standard (§3.7, in review).

Next, in order

#	Step	What you get
1	The three ontology layers, and one identity per thing across imports	Physics, the standards and each domain's view kept apart, so defaults can be synthesized from what each layer entails
2	The data network client: connect, publish, subscribe, query and answer	NEMESynth-EMSO on the network with other systems
3	Message schemas generated from the rules, and final decisions published with retry and read-back	Registered message formats that match the rules, delivered even when the link drops
4	Sensor readings as facts, checked against the assignments	What's heard checked against what's authorized, and a signal on a net's primary raising a PACE review
5	Halcyon reissued with its sheets inside the set	One package any node can run
6	The assistant runs the exercise while you watch	Halcyon worked start to finish, with each step explained
7	Subscriptions driven by the rules	You only receive what the rules need
8	Commands in, with oversight and command authority	Other systems can task NEMESynth-EMSO safely
9	Commands out: PACE switches carried out by the network manager	Plans executed on real networks
10	Node-to-node sync by sealed sets	Catch up after being cut off
11	Restricted frequency lists and the spectrum management tab	EA deconfliction, band occupancy and allocation views
12	Health of the network connection and the outbox	You're told when a link or a model goes bad, not only a feed

After that

EMSOPackage as a standalone GeoPackage file, with elevation.
NTIA GMF import and export.
Synthetic but realistic terrain for Trazore.
Judging effects against the baseline taken before the engagement.
Position and time from VICTORY on vehicles, with an interface control document and module map.
A local fine-tuned model for the assistant.

Help set the order

If one of these would make the difference for your unit or program, tell us. It's how we decide what comes first.

Get more information