ce-pov
Form a Point of View
Return a decisive, graded verdict on something from the outside world — judged against this project, not in the abstract.
<pov_request> #$ARGUMENTS </pov_request>
(If $ARGUMENTS above appears as a literal token rather than the user's words — it was not substituted on this host — use the user's actual request from the conversation as the input.)
Note: The current year is 2026. Use this when weighting source recency and dating any captured record.
The one rule that is the whole moat
Do not issue a verdict you did not earn against the project's own context. Generic web research already covers "tell me about X"; the differentiator is never "research the web" — it is the refusal to answer in the abstract. The verdict must clear two absolute floors (see references/method.md): a project floor (a concrete verified project fact — a named incumbent + a touchpoint, or for a net-new adoption the verified absence of one plus where it would fit, or a prior decision) and an external floor (at least one verified external source). The floors are absolute and independent — strong external evidence never compensates for a thin project leg, and vice versa. Neither the conversation nor the user's own assertions substitute for grounding.
Interaction Method
When you must ask the user a question, use the platform's blocking question tool: AskUserQuestion in Claude Code (call ToolSearch with select:AskUserQuestion first if its schema isn't loaded), request_user_input in Codex, ask_question in Antigravity CLI (agy), ask_user in Pi (requires the pi-ask-user extension). Fall back to numbered options in chat only when no blocking tool exists in the harness or the call errors (e.g., Codex edit modes) — not because a schema load is required. Never silently skip the question. Ask one question at a time.