I hope my solutions serves as nice demonstration how small embedded Linux designs can create operational value for tactical users but also NGO's and industry actors. They present what it takes to be resilient and secure when operating in battle space or supplying to it.

Secure PTT, Edgemap and Meshtastic integrations are small scale implementations which create digital sovereignty and operational security to users. They serve as design references how simplicity can be implemented.

Presented solutions are also excellent example when you need to think your organization abilities to operate and deliver during elevated operational demand.

So don't judge my implementations before you measure my capabilities to design, deliver and scale during times of crisis. Because that's what we should think now. What are my real abilities and external dependencies?

When times are 'normal', we can source, design and deliver pretty much everything we want. But if our user segment is critical infrastructure actor, defense, homeland security or organizations supporting them - demand can be normal or even low.

In elevated readiness conditions we might witness first supply chain related availability issues and delays. When logistic and components start to fall short, we should start thinking our abilities to produce and deliver. Typically these thoughts first hit for physical goods and components. But what about our digital delivery capabilities?

When your developers start off by downloading OS updates for their laptops, SDK's from cloud and source codes from external repositories - are they really ready to face new era in digital sovereignty? How can they actually operate when Internet is unreachable or cloud provider is in denied state ?

My fundamentals and reasoning for 'Resilience Theatre' has always been independence, digital sovereignty and operational design freedom.

I always wanted to create capabilities which are not affected by surroundings.

Partly this sources from my decades long professional background, mandatory military service and distance to Russian border. All of them being mind shaping realities which I simply could not change. So better be prepared.

When situation turns critical and your responding user segments are activating to full demand - you abilities to deliver (and support) solutions should follow.

But on the same time, you might loose your supply chain access and your local stock becomes an priority. Both physical and digital. Your software, mapping and data production should be able to operate regardless what is your operational location or Internet access status.

Think about it.

I hope this article gives you few ideas what to consider if you are tasked to be present and deliver when times get hard.

Because that's what I am able to do. I can continue develop, respond tactical demand, do required changes and scale my solution deliveries regardless of my access to Internet. Local source code, map data production and ability to turn these into useful products is present as long as I get electricity.

This combined to commodity design hardware creates totally new 'Battle space Ikea' - which I believe we see happening also in Ukraine.

Of course, I am just a one man band - but maybe your task is to make your development teams aware of this aspects and forget 'always available' access to macs, windows, cloud,vpn's and Starbucks. Because they don't exist when times get hard.

World is Grey when borders move.