Store of Scope

View saved version →

---
name: setting-up-store-of-scope
description: Use when a user asks to set up, connect, configure, reconnect, schedule, or recover Store of Scope, including missing Gmail, Calendar, Drive, or automation capabilities.
---

# Setting up Store of Scope

## Overview

Complete one reviewable setup from dependency checks through a verified preview. Gmail is required. Calendar is optional and recommended. Drive is optional. Never ask the user to install Noodle Seed.

Read [the setup contract](references/setup-contract.md) before changing configuration or creating an automation.

## Setup order

1. Call `get_store_of_scope_status`. If the hosted MCP connection fails, stop and report the connection error; do not request Noodle credentials or attempt to bypass the configured endpoint.
2. Verify Gmail capabilities are installed, enabled, signed in, and able to perform a safe read. If absent, guide the user to install the Gmail app through the host and stop until authorization completes.
3. Request Gmail read access first. Verify send access only when delivery is enabled. Do not request delete, archive, label, trash, or read-status mutation.
4. Offer Calendar only for a managed reading event. Offer Drive only for user-owned cloud exports. A declined optional connection must not block newsletter setup.
5. Collect sender addresses, timezone, cadence, archive window, edition limit, delivery recipient, delivery mode, and optional reading-event settings.
6. Reject duplicate or invalid sender addresses before any mailbox search. Show a redacted configuration summary.
7. Run a read-only Gmail count preview by source. Do not pass credentials, raw message bodies, MIME content, or attachment bytes to Store of Scope.
8. Obtain explicit approval for initial ingestion, then save configuration using the current revision.
9. Generate and validate a workbook and e-book preview through separately authorized host capabilities. Do not claim success without validation receipts.
10. Obtain separate approval for the first send and future unattended sends. A first-send approval is not unattended-send approval.
11. If enabled, upsert one Calendar reading event and reconcile duplicates before creating another.
12. Propose one daily scheduled task in the configured timezone. Create it only after the user approves the exact schedule and prompt.
13. Re-read status and report connections, source counts, delivery mode, next run, pause control, and manual-mode fallback.

## Recovery

- On a revision conflict, reread status and reconcile; never overwrite.
- On Gmail disconnection, pause dependent work and guide reconnection.
- On a pending run, recover or reconcile it before starting another.
- If scheduled tasks are unavailable, configure manual mode and provide: `Run today's Store of Scope newsletter workflow.` Do not claim automation is active.
- Require confirmation before retirement, workspace deletion, Calendar cleanup, or replacement of user-owned artifacts.

Referenced files: 2 — file references are metadata, not package contents.

View saved version →

---
name: store-of-scope
description: Use Store of Scope to coordinate a revisioned newsletter-reading workflow after separately authorized host capabilities have read Gmail or produced external artifacts and receipts.
---

# Store of Scope

<!-- noodle-app-package source:fb3c2121eb4fd8990d33245e3eb6f1a042642ee3fbeeb7aa0a875d031a447f9c surface:0f151d604ce3e849494581c52d4beafb5611c9079450a9a816f0474d49c9b954 -->

## When to use this product
- The user wants to configure, inspect, run, pause, recover, or retire Store of Scope.
- The user wants to reconcile normalized newsletter metadata or commit validated workflow receipts.
- The user wants a reviewable three-week plan for unread newsletters.

## Workflows

### Configure a Store of Scope workspace

Create or update validated caller-scoped configuration without silently activating delivery.

1. `tool:get_store_of_scope_status` — Read current revisions and preserve existing state before proposing changes. (read-only; idempotent)
2. `tool:save_workspace_config` — Use the exact current configuration revision after the user reviews senders, schedule, delivery, and approval settings. (write; confirmation required)

### Run daily orchestration

Calculate due branches and acquire one idempotent run before external work begins.

1. `tool:get_store_of_scope_status` — Stop if the workspace is unconfigured, paused, retired, or already has a pending run. (read-only; idempotent)
2. `tool:calculate_due_work` — Supply the date and weekday already resolved in the configured workspace timezone; return cleanly on no_action_due. (read-only; idempotent)
3. `tool:begin_workflow_run` — Use a stable run id and idempotency key for each due branch and local date. (write)

### Commit a validated reading edition

Reconcile archive metadata and commit an edition only after external validation and delivery evidence exist.

1. `tool:reconcile_archive_index` — Pass bounded normalized metadata from an authorized external Gmail read; never pass message bodies, MIME content, or credentials. (write)
2. `tool:commit_workflow_run` — Commit only a passed artifact receipt and, when delivery is enabled, the matching provider delivery receipt. (write)

### Commit a Friday archive refresh

Preserve historical archive ids and commit a validated workbook refresh.

1. `tool:reconcile_archive_index` — A smaller later Gmail result never authorizes deletion of historical archive ids. (write)
2. `tool:commit_workflow_run` — Commit only after workbook validation passes; attach delivery evidence only if confirmation was sent. (write)

### Plan unread newsletters

Propose a deterministic plan first and persist only the exact user-approved digest.

1. `tool:propose_content_plan` — Treat the result as read-only; show dates and counts for review. (read-only; idempotent)
2. `tool:approve_content_plan` — Call only after explicit approval of the exact proposal digest. (write; confirmation required)

### Recover or pause automation

Inspect the recorded state before retrying and give the user a safe stop control.

1. `tool:get_store_of_scope_status` — Use pending and recent run receipts to decide whether to retry, reconcile, or stop. (read-only; idempotent)
2. `tool:set_automation_paused` — Require confirmation and the current configuration revision. (write; confirmation required)

### Retire Store of Scope state

Make all Store of Scope state handles permanently read-only after explicit confirmation.

1. `tool:get_store_of_scope_status` — Show the user the exact current state revisions and explain that retirement is terminal. (read-only; idempotent)
2. `tool:retire_workspace` — Call only after explicit confirmation using all four exact revisions. (write; destructive; confirmation required)

## Boundaries
- Store of Scope does not authorize Google accounts. Use external Gmail and optional Calendar capabilities only after their own connection and permission checks.
- Never store Google credentials, raw message bodies, MIME content, attachment bytes, or full recipient addresses in workflow receipts.
- A deployed MCP does not prove that Gmail, Calendar, workbook or PDF rendering, delivery, or scheduled automation is active.
- Do not claim artifact validation or delivery success without the corresponding external receipt.
- Obtain explicit approval for initial ingestion, first delivery, future unattended delivery, content-plan writes, and workspace retirement.
- On a revision conflict, reread status and reconcile; never overwrite newer state silently.

## Examples
- “Set up Store of Scope.” — use `configure_workspace`.
- “Run today's newsletter workflow.” — use `run_daily_orchestration`.
- “Plan three weeks of unread newsletters.” — use `plan_unread_content`.
- “Pause Store of Scope.” — use `recover_or_pause`.

## MCP surface

[Read the MCP surface reference.](references/mcp-surface.md)

Referenced files: 1 — file references are metadata, not package contents.