There are many directions a defence software company could take. We chose airspace because it brings a difficult coordination problem into a form we can examine: several flights needing the same area at different heights and times.
A route can be workable on its own and still conflict with another request. A small change to one flight may affect the options available to someone else.
Give the shared problem a common frame
A useful planning workspace needs to represent routes, time windows and restrictions together. The reviewer should be able to connect a finding to the part of the plan that caused it and understand how a proposed change affects the rest.
That is the starting point for Aerlattice. Before adding more information, we need to make the relationships within that first task understandable.
Let the task guide the scope
Airspace also gives us concrete design questions. What does the reviewer need to see when a route changes? How should a delayed observation affect the discussion? Which version of a flight is the accepted plan?
Working through those questions will help us decide what belongs in the application. Broader context is useful when it helps someone resolve a specific planning question and its source is clear.
