C.32.LCA:11 - SoTA-Echoing

Which line answers the working question? For constructing joint control under different information, timing and authority, this pattern selects a synthesis of whole-arrangement comparison, explicit dynamic and temporal connections, and domain-specific qualification. A fixed three-layer template is cheaper to draw but leaves those connections to the reader. The additional work here is justified when a consequential dependency remains unresolved; :5 shows a changed command interface and an authority-dependent deadline. These are conditional constructions, not measured enterprise benefits. Retain a sufficient incumbent and reopen this choice if its extra analysis cannot change the receiving decision.

Adopt joint design rather than independent layer tuning. Matni, Ames and Doyle’s 2024 treatment, §§2–3 and 4.5 supports reasoning from a whole control problem to interacting layers. This changes :4.4 and :4.8: a removed consistency condition becomes an obligation to construct the connection. The source develops a research programme, not a universal optimal layer count. The common method adapts that question beyond its technical constructions; a claimed transfer still needs the receiving dynamics, conditions and evidence. Reopen when the proposed separation has no supported interface or a simpler controller answers the same demand.

Adapt quantitative architectural co-design within its class. Verhoek et al., 2026, §§2, 5 and 7 make model order, sampling ratio and controller parameters joint design variables for a two-layer LTI construction with compute constraints. Compared with fixed rate heuristics, this supports the whole comparison in :4.7–:4.10. The accepted cost is a demanding optimization and qualification problem. This is a bounded preprint result; general composition and several extensions remain open. Use a simpler qualified design when sufficient, and reopen on a changed plant, observation regime or implementation premise.

Retain a governor as a serious alternative. The Garone, Di Cairano and Kolmanovsky survey, §§2 and 6 supplies the established alternative of managing commands over a pre-stabilized system. Castroviejo-Fernandez and colleagues, 2024, develop a disturbance-observer-based continuation. Their conditions motivate :4.5 and the observation change in :5.1. Adopt the architecture when its qualified loop and admissible-set construction answer the demand; reject treating it as automatic mission achievement. Its price is altered progress and model-dependent qualification. Reopen if those costs or assumptions defeat the receiving use.

Adapt organizational design and commitment-based coordination. Joseph and Sengul’s 2025 review compares organizational-design approaches rather than making decentralization a universal answer. Guerreiro and Dietz, 2024, preserve request, promise, declaration, acceptance and exceptional continuations in business-process descriptions. These lines change :4.2, :4.6 and :4.8: the organization must supply decision rights and workable commitments, not merely fast commands. Their use can add negotiation and coordination cost. Reopen when the decisive dependency is an unavailable capability, resource or conflicting interest rather than the proposed information or authority arrangement.

Use safety analysis for its distinct result. The STPA Handbook, Chapters 2–3, is an established approach to unsafe control actions and inadequate process models. Adapt its attention to timing, missing feedback and conflicting control in :4.3, :4.7 and :4.8. It is a serious alternative to checking only nominal performance when harmful loss is possible; it does not replace performance synthesis or prove absence of loss. Reopen the relevant safety analysis when a control action, model, responsibility or operating condition changes.

Learned execution does not settle architecture qualification. Figure’s Helix 02 description gives a concrete comparator: semantic reasoning, 200 Hz joint targets and 1 kHz whole-body execution with a learned lower component. It supports considering different functional and timing demands, not the superiority of that allocation in every system. Adapt the distinction in :4.9; retain a programmed qualified component as a rival. Reopen on a changed policy, observation distribution, latency or relied-on constraint. The vendor demonstration supplies no general enterprise or closed-loop safety theorem.