Operator and Chat
Use conversation for exploration while creating durable work deliberately.
The organization chat is always available. It is appropriate for questions, synthesis, planning, and deciding whether an idea should become tracked work.
Conversation Stays Conversation by Default
Sending a message does not automatically create a task. This prevents every question from becoming operational clutter and gives the operator room to clarify scope before committing resources.
Use chat to:
- ask what Context currently says;
- compare alternatives;
- clarify the desired outcome;
- identify the owning department;
- discover missing evidence;
- review a proposed plan; or
- decide whether durable execution is warranted.
When to Create Durable Work
Create a task when the request needs one or more of:
- ownership;
- dependencies;
- scheduling;
- attempts and retries;
- files or artifacts;
- human blockers;
- consequential external actions; or
- an outcome that should inform future work.
Write Better Requests
State the outcome, constraints, evidence, deadline if real, and what requires approval. For example:
Review the last 30 days of support themes, use only connected read-only sources, group recurring problems by product area, and prepare an evidence-linked engineering brief. Do not contact customers or change tickets.
This gives the operator a bounded workflow without dictating every implementation step.
Attachments
Use attachments when the file is part of the current conversation. Use organization Context when the information should guide future work across chats and tasks.
If a Response Stops
Pending assistant messages are durable and can be recovered after a lost live signal or restart. Check service health before resending the same instruction; duplicate user instructions can create conflicting intent even when runtime execution itself is fenced.