Change the architecture. Preserve the mission.
The architecture separates mission intent from implementation, but now treats hardware state, model validity, configuration and mission priorities as one extended runtime state.
Architecture layers
Mission intent is resolved through functions, services, resources and supervisory decisions.
Mission → Function → Service → Resource.
The hierarchy survives the research revision. The key change is at the resource level: a resource is anything whose condition limits the ability to realise a function — including models and algorithms.
A candidate is useful only if all three questions are answered.
Resource condition propagates through services and functions to the mission-level capability score \(S\).
Observe → validate → score → plan → gate → execute.
The catalogue is finite because every configuration must be verified before deployment. Runtime learning or experience can alter preferences and transition probabilities, but it cannot create an unverified configuration or edge.
Different layers still run at different rates.
The abstraction hierarchy says what the system means. The execution hierarchy says where decisions are computed and how quickly they act.