RMP.3:10 - Architectural Rationale

Separating design selection from operationalization protects two useful decisions. RMP.2 can compare evidence strategies without pretending every local detail is settled. RMP.3 can make one selected strategy executable without being allowed to change its criticism silently. The joint-input condition connects them: unresolved details are acceptable only inside the selected design’s admitted bounds.

The operational specification and the actual trace remain distinct because an intention and an account of conduct answer different questions. They can occupy one notebook and can develop together. RMP.4 also supports inherited work whose prospective specification no longer exists.

The cheaper alternative is often best: use a competent domain protocol and adequate records directly. The RMP contribution is needed when the question-to-operation connection, change consequence or research-use limitation remains unresolved. A universal form would add burden while obscuring differences among measurement, interpretation and source criticism.