Provenance trust gate
EchoCore caps confidence at the assurance level of the supporting evidence. A spoofed broadcast, stale detection or synthetic stream cannot support a high-confidence track.
The engine associates sensor observations, checks trust and policy, and releases a result only through the fixed pipeline.
EchoCore associates sensor observations and applies trust and policy checks before release.
Automated tests cover trust, compliance and determinism. Valhalla scores the engine against synthetic ground truth.
Extend the same evidence-first release path into live sensor integration, operator workflows and field evaluation.
The first gate limits confidence using the source and quality of the evidence. The second applies policy before and after fusion.
EchoCore caps confidence at the assurance level of the supporting evidence. A spoofed broadcast, stale detection or synthetic stream cannot support a high-confidence track.
Machine-readable policy runs before and after fusion. It can permit, restrict, downgrade, segregate or block. Missing labels cause a block. Audit records are hash-chained, and bundle files are covered by a SHA-256 integrity manifest.
EchoCore orders claims as presence < bearing < position < track < identity. Each evidence combination sets the highest claim type and confidence the engine may release.
Valhalla sends unchanged synthetic datasets through EchoCore AI. The scorer compares the output with simulation ground truth. We used it to find defects in stream handling, multi-target separation and cross-target association. We run it as the acceptance gate for engine changes.

mean cross-target contamination
Share of observations associated across targets. Baseline run, then fusion-fixed run.
mean track purity
Share of observations from the correct target. Baseline run, then fusion-fixed run.
These figures describe pipeline behaviour across an 8-seed Valhalla sweep of the raid_demo scenario.