operator.md

Operator

The operator pages give the rules for the operator. The operator is the assistant session where the user works.

The start docs of the operator are:

1. docs/operator.md
2. The pages of the list "The pages" below
3. docs/dev/working-with-the-user.md
4. docs/dev/rules.md
5. docs/sessions.md

The operator reads them at its start, as the doc-read rule says. The form of a reply gives the form of each reply to the user.

Messages of the other sessions break into the conversation of the user, and open questions scroll out of view. A planner or an orchestrator sends each item that needs the user to the operator. Then the user reads the items in one place and answers the questions for the user alone.

docs/sessions.md defines the user, the slug, the sessions of a slug, an item, the own name of a session, the session ref and the socket address. The operator is named operator-<slug>. The operator of a session is the operator that the first message of the session names. If the first message names no operator, the operator of the session is operator-<slug> of its own slug. The reason: the name of the session of a topic handoff gives a slug that no operator has, so the first message carries the operator. This definition covers only the operator. A sentence that names planner-<slug> or orchestrator-<slug> still takes the slug of the own name of the session. The hold of the items keeps its own terms.

The tab list is the list of the tabs that an operator can close. Each entry gives the tab id and the session name of one tab. In a handoff of the operator, the old operator also closes its own tab, as Stop a session says.

The operator runs only these tasker commands: show-config, show-quota, show, show-bootstrap, show-plan, show-questions, show-verify, show-review, model, status and doctor. The operator also runs each tasker command that only prints or sets the assistant or the models of a repo or a task. It sets a value only on a request of the user. A message that starts with "From the user:" is such a request, and an item of another session is not. It runs no other tasker command and starts no task subagent of a ticket. An installing operator also runs the commands that The hold before an install names.

When a step of the operator pages applies the failure rule, the rule covers the operator in the place of the orchestrator. When the operator gets a notice, the operator follows the notice rule. For an item with a denied command, the operator follows the tool-block rule. For a denied command of step 3 of "The order of a milestone" or a denied removal of the label "on hold", the operator follows A denied command of the operator.

The operator pages are docs/operator.md and the pages of this list, "The pages":

• docs/dev/operator-start.md: "The order of a milestone", "Start a session", "The start prompts", "Stop a session", "The close of a milestone", "A handoff", "A denied command of the operator" and "A blocked session".
• docs/dev/operator-items.md: "The form of an item", "The open items", "The answer" and "The states of an item".
• docs/dev/operator-conversations.md: "A side conversation" and "The word of the user".
• docs/dev/handoff.md: "The suggestion of a handoff", "The handoff file", "The items of a handoff file", "The last item id", "The check of the handoff folder", "The end of a handoff", "The stop and the start", "A topic handoff" and "The hold of the items".
• docs/dev/handoff-operator.md: "The handoff of the operator", "The close count", "The steps of the old operator", "The handoff file of the operator" and "The start of the new operator".
• docs/dev/session-review-rounds.md: the rounds of /session-review before a stop.