In defense and government, teams in the field often work where networks are contested, congested, degraded or cut off entirely. This client, whose name is confidential, needed AI support for English- and French-speaking users operating in exactly those conditions.
Wildstream designed a hybrid edge, fog and core architecture for two deployable AI assistants, one for technical support based on equipment documentation and one for operational knowledge retrieval, built to keep users working through outages of up to 24 hours.
Edge users keep working through network outages of this length, served by local models and a synchronized RAG cache
Edge, fog and core layers share the AI workload, so each request can run where current conditions suit it best
The architecture is built for contested, congested, degraded and disconnected networks, not only for stable connectivity
Field users need reliable technical support and knowledge retrieval, in English and French, in environments where connectivity is degraded or completely lost. Their networks can be contested, congested, degraded or fully disconnected, so an assistant that depends on a central server would stop working exactly when users need it most.
Edge users keep working through network outages of this length, served by local models and a synchronized RAG cache.
One supports technical work from equipment documentation, the other retrieves operational knowledge for users at the edge.
Both assistants serve users in either language, using multilingual models chosen to fit the edge hardware they run on.
Wildstream designed two assistants: one for technical support based on equipment documentation, and one for operational knowledge retrieval. Both run on deployable edge hardware as part of a hybrid edge, fog and core architecture, and every candidate model is also measured for memory use before it is selected. Testing checks how well answers stay grounded in the source material, their overall quality, and whether the local cache stays in sync with the wider system.
A local copy of the knowledge base stays aligned with the core, so offline answers draw on the same, current content.
Multilingual models are benchmarked for accuracy, latency, memory and power use before they are deployed on edge hardware.
Evaluation reproduces poor or lost connectivity and tracks response quality and service availability across both assistants.
Users keep solving equipment issues and finding operational knowledge on site, instead of pausing work until the link returns.
Groundedness is measured in testing, so responses stay tied to the equipment documentation and knowledge users already rely on.
Synchronization integrity is checked, so people working offline and online consult the same, current version of the content.
AI workloads in contested networks must cope with shifting bandwidth, latency and data-sensitivity constraints without failing. The system also had to serve two deployable AI assistants for English- and French-speaking users, whose requests cannot simply wait for a stable link to a central server.
Edge, fog and core layers share the AI workload, so each request can run where current conditions suit it best.
The architecture is built for contested, congested, degraded and disconnected networks, not only for stable connectivity.
Edge users can keep working through outages this long, because local models and cached knowledge do not need the core.
Wildstream designed this architecture behind two deployable AI assistants, one for technical support and one for operational knowledge retrieval. Edge devices run local models and a synchronized knowledge cache for disconnected use, while fog resources take on requests when connectivity, latency and available compute allow. A connectivity manager watches network conditions and changes how messages travel, and testing measures synchronization integrity and service availability as conditions degrade.
Each request is routed by connectivity, latency, data sensitivity, model capability and available compute, not by a fixed rule.
A dedicated component monitors network conditions continuously and tells the system which communication mode to use at any moment.
When links degrade, real-time messaging gives way to store-and-forward protocols that hold messages and deliver them later.
Service availability is tested under degraded conditions, so resilience is measured against the networks users actually face.
Data sensitivity is weighed in every routing decision, helping keep sensitive requests at the tier best suited to handle them.
Synchronization integrity is part of testing, so information created offline reaches the rest of the system once links recover.
Requests use fog compute when it is reachable and stay local when not, making the most of limited deployable hardware.
New assistants or workloads can plug into the same edge, fog and core design without rethinking how connectivity is handled.