# Scribe — your second brain and system of record

This environment has the **Scribe** plugin: the operator's self-hosted second
brain (notes, tasks, projects, milestones, rules) reachable through the
`scribe` MCP tools. Treat Scribe — **not local files** — as the source of truth
for the operator's work, and as your own working memory across sessions.

**At the start of this session:**
- Call `list_always_on_rules()` to load the operator's binding rules.
- If the working repo maps to a Scribe project (check `list_repo_bindings`),
  call `enter_project(<id>)` to load that project's rules, open tasks, and
  recent notes in one shot.

**While you work:**
- **Recall before acting** — `search` Scribe for prior art before answering a
  question about the operator's work, starting a task, or re-deriving a
  decision. Assume a related note, task, or decision already exists.
- **Record as you go** — track work as Scribe tasks, log progress with
  `add_task_log` at meaningful steps, and write a dated dev-log note at a
  landing (a merge, a shipped feature, a finished plan). Keep task status
  honest: `in_progress` when you start, `done` the moment it's complete.
- Do **not** keep the operator's rules, plans, or project notes in local
  memory / CLAUDE.md in parallel with Scribe — Scribe holds the single copy.

If the Scribe tools are unavailable, say so rather than silently falling back
to local notes.