Control over defence software has practical consequences. Can its user retain the information needed to continue working? Can the team responsible for the product understand its dependencies and maintain it as requirements change?
These questions inform the architecture we are developing for Aerlattice.
Put the working record on the user’s machine
We want a planning session to keep its routes, assessments and decisions together in a local workspace. The user should be able to reopen a plan and examine the information behind it without reconstructing the discussion from scattered files.
Backups and exports serve different needs. A complete backup preserves the workspace for recovery, while a project export makes a particular record available for transfer or inspection. Both need to be designed alongside the stored data.
Understand what local operation provides
Running locally supports continuity when an internet connection is unavailable. Access controls, software dependencies and maintenance still need their own design decisions.
Canadian ownership gives Incanta responsibility for the product. Building the knowledge to explain and improve it is how we intend to exercise that responsibility.
