Dot 3 / Responsibilities

Start with one useful responsibility

Find a useful next step, then decide what dot should help keep moving over time.

Start with a next step you can recognize

You might begin with “Help me get this project moving again.” After a little discussion, the next step could be to collect open questions, choose a priority, or update a private checklist. You can work out the responsibility together.

Choose something you already understand well enough to judge. Starting with your least understood, highest-stakes problem makes it difficult to separate a helpful result from a confident mistake.

One responsibility is a teaching starting point, not a product limit. Dot can keep track of several responsibilities. Name the project when switching priorities, and explain what should keep going or wait.

Make the next result clear

A practical responsibility has four parts:

  • Input: the specific information to review.
  • Work: the analysis or preparation to perform.
  • Output: the document, table, or recommendation to return.
  • Finish line: what should be present, checked, or left unresolved.

For example: “Review these five project notes. List unfinished commitments, their named owner, and any stated deadline. Cite the source note. If an owner or date is missing, write ‘not specified.’ Finish with the three decisions that need my attention.”

This avoids a common failure: a polished summary that never identifies what to do next.

Let a useful next step become ongoing help

Once you have something useful, say what to carry forward: “Keep this private project checklist current from the notes I share. Tell me when a deadline changes or you need a decision.” Add new context and priorities as they arise. Ask “What’s finished and what’s blocked?” when you return.

Dot can continue assigned work and decide when to follow up; every next step does not need a fixed timer. It may also suggest useful work based on context it is authorized to read. These are possibilities, not a guarantee of timely or useful suggestions. OpenAI’s tasks and memory guide.

Be clear about preparation and action

A helper can prepare a response without being authorized to send it. Name what may proceed and which decisions need you. You can explicitly authorize a scoped action or ongoing responsibility, subject to actual permissions and product safeguards. OpenAI’s controls guide.

Our recipes start with review and preparation as beginner preferences. They are starting points for a conversation, not separate agents deployed by this website.

Add a schedule when timing matters

For a regular check-in, agree on a day, time, time zone, source window, and end date. Say which changes deserve an update and where to send it. For example, ask for a Tuesday review until the event, with a message only for new decisions or blockers.

A cadence written in our builder does not create a schedule or automation. Ask dot to confirm what it saved in the actual product and review its scheduled tasks. You can revise the responsibility or cancel the schedule later.

An event is different from a timer

Where a connected service supports event monitoring, you can request work when a particular event occurs. Identify the source, event, scope, and what merits an update. Ask dot to confirm what it can follow and how to stop it. Connecting the source alone does not establish monitoring.

A contextual suggestion is different again: dot may connect available information with your goals and raise something useful. Its timing and usefulness vary. Do not treat that possibility as a guaranteed alert.

Finish or change the arrangement

Review active work as well as future runs. Pausing dot’s main task does not stop every delegated task or cancel schedules. Use Activity to inspect and stop delegated work, and Scheduled to disable or delete recurring runs. Confirm any relevant event monitor is disabled too. See the steering guide or existing work and automations.

Try this now

Complete this sentence:

Review [one small input], prepare [one observable output], and stop before [the next consequential action].

Then write a first test small enough to check every item. Three invented customer records or a single non-production project note is enough. Compare the result with your own assessment before expanding the source set.

Common mistakes

Losing track of several jobs. Keep outcomes and update preferences clear for each responsibility. Begin with one if that makes review easier.

Using “handle it” as a finish line. Specify what the helper should return and when it should stop.

Making the output uncheckable. Require references, unknowns, and a short explanation for recommendations.

Scaling before reviewing. A successful small test gives you something to improve; it does not prove every future case is safe.

Your next dot

Now decide which actions may proceed and which need you. Continue to Set boundaries before giving more responsibility.

Official references

Source check: October 14, 2026. A source check is not hands-on testing.