decision-normalization

To normalize product management decisions, you provide the PM decision response to generate a canonical, implementable requirement statement or mark it unresolved. This enforces a two-output contract, outputting either RESOLVED or UNRESOLVED to formalize the decision.

A RESOLVED or UNRESOLVED output contract is a binary framework that formalizes PM decisions. RESOLVED outputs a concise, implementable requirement statement, while UNRESOLVED signals the need for further clarification, ensuring decisions are explicitly codified without ambiguity.

To log PM decisions without adding fabricated details, the normalization process enforces strict faithfulness to the PM's original input. It provides guardrails that forbid inventing or synthesizing details beyond what was explicitly stated, preserving the integrity of the decision log.

Yes, you can integrate decision normalization with a Clarification Controller. The system is specifically designed to support workflow flows with the Clarification Controller and Decision Normalizer to manage clarification cycles and log binary or explicit selections.

You should mark a product management decision as UNRESOLVED when the PM's input lacks sufficient clarity for implementation. This signals the clarification cycle to continue, ensuring no requirements are forced through normalization without explicit, actionable details.