Interop Standards

NATO / military interoperability + symbology standards across Bedrock. Each row links its reference doc; status reflects what is actually implemented, verified against source.

Status

Standard	Purpose	Status	Doc
MIL-STD-2525D / APP-6D / ADatP-37	Map symbology via 20-digit SIDC	Implemented	app6-symbology, adatp37-sidc
ADatP-3	Formatted military text (OPREP, INTREP, SALUTE)	Implemented	adatp3-messages
CoT / TAK	ATAK / TAK Server exchange	Implemented	cot-tak
NFFI / STANAG 5527	Blue-force tracking XML	Implemented (file export)	nffi-stanag5527
STANAG 4774/4778	Classification labels + ceiling enforcement	Implemented	stanag4774-4778
Link 16 (MIL-STD-6016 / STANAG 5516)	Tactical data link (air/naval)	Planned / design	link16-track-ingest
Link 11B (STANAG 5511)	Serial tactical data link	Planned / design	link11b-serial-ingest
VMF (MIL-STD-6017)	Variable message format (binary)	Planned / design	vmf-binary-messaging
MIP / DEM	Multilateral data exchange model	Planned / design	mip-dem-exchange
NVG	NATO vector graphics (tactical)	Planned / design	nvg-tactical-graphics
OTH-Gold	Over-the-horizon maritime reporting	Planned / design	oth-gold-maritime
HLA	High-level architecture simulation	Planned / design	hla-simulation
WMS (OGC)	User-configurable map tile layers	Not started	wms-map-sources

Full maturity view and where each capability lives: Status & Roadmap.

The "Planned / design" docs describe the standard and a proposed integration approach; no format adapter exists in gateway/src/formats/ yet.

Where the work lives

• Gateway adapters follow src/formats/<standard>.rs (serialize/parse) + src/publishers/<standard>_<transport>.rs (file / MQTT / multicast / HTTP / serial). That source-layout convention stays documented in the gateway repo.
• Symbology (SIDC parse + render) is common/src/sidc/ and android/ui/symbols/; the web renderer is not yet ported (options in app6-symbology).