E.17.ID.CR:1 - Problem frame

Engineer-managers, programme leads, and research or cultural reviewers repeatedly need to prepare or share a small comparative review unit that helps a team read two already available source epistemes or source publications together without overstating what downstream claim or effect that unit now carries. Typical moments include:

• a design-review note that says one already available option write-up foregrounds coupling risk more than another;
• a release or compliance comparison that says an internal control sheet and a vendor bulletin are not yet equivalent even though they speak to the same review task;
• an operations comparison that says a dashboard view and a maintenance note foreground different operational pressures in the same service episode;
• a research-review note that says one available synthesis foregrounds measurement uncertainty more than another without yet declaring a better method;
• a program or cultural review note that says one available brief foregrounds participation continuity more than another without yet deciding funding, curation, or program direction.

These review units are useful precisely because they make the next review discussion more precise. They become dangerous when a reader starts treating them as if they already established equivalence, root cause, redesign priority, action selection, program choice, or approval.