Claude Operator: Prompt to Autonomy · 22 min · 140 XP

A read-and-write workflow: notes and pages

Turn source material into a draft without inventing anything or notifying anyone.

Connecting a document tool — Notion is the worked example here, but the shape is the same for any of them — gives you a workflow with a genuinely useful ceiling: read real material, produce a structured result, write it back as a draft. The discipline is in what you don't let it do.

Start by sharing only a practice page or workspace area. Most people connect their whole workspace because it's one click, then ask a question that happens to match a private page. Share the smallest area that makes the exercise real, and confirm the boundary by asking for something outside it — a connector that can't see your salary review is one you can experiment with freely.

Reading has one rule: unknown stays unknown. Summarising a meeting page, the temptation is to produce a complete-looking result, so an unnamed owner becomes a plausible name and an undated action gets "this week". Require the gaps: "If an owner or date isn't stated on the page, write 'not stated' rather than inferring one." A summary where every fact traces back to the source is worth something; one that's 90% traceable is worth nothing, because you can't tell which 10%.

A write that stays reviewable
From the practice page, produce:
  - Decisions (with who decided, or "not stated")
  - Actions (owner and date, or "not stated")
  - Open questions

Then create a new page titled "DRAFT — <date> review" under
the Practice parent. Do not notify anyone, do not assign
anyone, and show me the exact content before you create it.

Two things make that write safe. It's labelled a draft and lives in a parent you chose, so it can't be mistaken for a finished document. And it shows you the content first — the preview is what turns a write into a decision. For an update to an existing item, narrow it further: name the single property, and check afterwards that only that property changed.

Practice. Connect an approved endpoint and share only a practice area, then prove the boundary by asking for something outside it. Locate a page by a distinctive phrase and confirm the result matches the source. Summarise it with unknowns required to stay unknown. Create a clearly labelled draft in the parent you chose, with nobody notified or assigned. Update one low-risk property after previewing it, and verify nothing else moved.

Loading your workspace…