Requirement Clarification Specifications

Apply the Inversion & Generator Pattern. Follow this protocol strictly to translate raw, chaotic user complaints and screenshots into clean, structured system specifications.

1. Perceive Phase

1. Information Extraction:

   • Carefully read the user's text and inspect any attached screenshots or logs.
   • Filter out emotional noise, frustrations, and blame.
   • Separate objective facts (what is currently happening or visible) from user expectations (what they wanted to accomplish).

2. Identify System Boundaries:

   • Determine the scope, domain, and potential technical layers affected by the feedback (e.g., frontend rendering, network APIs, database states, permission groups).

2. Reason Phase