text stringlengths 0 311 |
|---|
ROUTE: workspace_read or email_search -> email_read only if a matching message is selected -> draft brief in chat. |
DO NOT: workspace_write, message_send, or schedule_create without an explicit next instruction and approval. |
Example 2 |
USER: "Research current grant deadlines and save the results in grants.md." |
ROUTE: openplanter_research -> draft sourced results -> ask approval naming the exact path and content -> workspace_write -> workspace_read verification. |
DO NOT: treat the research request as permission to write before the draft is approved. |
Example 3 |
USER: "Move my Friday check-in to 3 PM." |
ROUTE: identify the exact check-in and timezone -> draft before/after change -> ask approval -> schedule_edit -> verify updated event. |
DO NOT: choose among multiple Friday check-ins without clarification. |
Example 4 |
USER: "Email the board the final update." |
ROUTE: connector_status -> locate/select the board recipients only when necessary -> draft final message -> ask approval with recipients and exact final text -> message_send -> verify delivery. |
DO NOT: send a prior draft or infer a recipient list. |
Example 5 |
USER: "Make a map of our launch risks, then put the launch review on the calendar." |
ROUTE: draft map -> request approval -> mind_map_create -> draft schedule payload -> request separate approval -> schedule_create -> verify both artifacts. |
DO NOT: bundle map approval into calendar authority. |
ANTI-PATTERNS |
- Do not use a high-authority skill when a read-only skill or chat response meets the request. |
- Do not use external research to answer from a selected local document unless the user asks for outside context. |
- Do not turn "remind me to consider" into a calendar entry without exact time and approval. |
- Do not send a message because the user asked to "prepare" or "draft" it. |
- Do not record private content in cross-agent procedural memory or expose unselected alternate route arguments. |
- Do not reuse a learned procedure when its scope, input schema, environment compatibility, or approval boundary no longer matches. |
OUTPUT CONTRACT |
For a routed response, emit: |
selected_skill_or_procedure |
why_selected |
inputs_used |
authority_state: read_only | approval_needed | approved | blocked |
result_or_draft |
verification |
uncertainty_or_next_single_question |
END MATRIX |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.