← Store of ScopeCONTENT HISTORY

Update to Store of Scope

Snapshot Oct 24, 2026 · 13:39 UTC · version 0.1.0

Collection source: downloaded plugin package.

WHAT CHANGED

First saved snapshot

No earlier snapshot is available to establish a change.

Save Store of Scope and check future changes in Following.

Up to 10 plugins free · no card required.

Compare saved observations

Download comparison JSON
Full technical diff · 0 changed fields
Full snapshot data
{
  "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.",
  "included_files": [
    {
      "relative_path": "references/mcp-surface.md",
      "size_in_bytes": 2110
    }
  ],
  "name": "store-of-scope",
  "skill_md_contents": "---\nname: store-of-scope\ndescription: 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.\n---\n\n# Store of Scope\n\n<!-- noodle-app-package source:fb3c2121eb4fd8990d33245e3eb6f1a042642ee3fbeeb7aa0a875d031a447f9c surface:0f151d604ce3e849494581c52d4beafb5611c9079450a9a816f0474d49c9b954 -->\n\n## When to use this product\n- The user wants to configure, inspect, run, pause, recover, or retire Store of Scope.\n- The user wants to reconcile normalized newsletter metadata or commit validated workflow receipts.\n- The user wants a reviewable three-week plan for unread newsletters.\n\n## Workflows\n\n### Configure a Store of Scope workspace\n\nCreate or update validated caller-scoped configuration without silently activating delivery.\n\n1. `tool:get_store_of_scope_status` — Read current revisions and preserve existing state before proposing changes. (read-only; idempotent)\n2. `tool:save_workspace_config` — Use the exact current configuration revision after the user reviews senders, schedule, delivery, and approval settings. (write; confirmation required)\n\n### Run daily orchestration\n\nCalculate due branches and acquire one idempotent run before external work begins.\n\n1. `tool:get_store_of_scope_status` — Stop if the workspace is unconfigured, paused, retired, or already has a pending run. (read-only; idempotent)\n2. `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)\n3. `tool:begin_workflow_run` — Use a stable run id and idempotency key for each due branch and local date. (write)\n\n### Commit a validated reading edition\n\nReconcile archive metadata and commit an edition only after external validation and delivery evidence exist.\n\n1. `tool:reconcile_archive_index` — Pass bounded normalized metadata from an authorized external Gmail read; never pass message bodies, MIME content, or credentials. (write)\n2. `tool:commit_workflow_run` — Commit only a passed artifact receipt and, when delivery is enabled, the matching provider delivery receipt. (write)\n\n### Commit a Friday archive refresh\n\nPreserve historical archive ids and commit a validated workbook refresh.\n\n1. `tool:reconcile_archive_index` — A smaller later Gmail result never authorizes deletion of historical archive ids. (write)\n2. `tool:commit_workflow_run` — Commit only after workbook validation passes; attach delivery evidence only if confirmation was sent. (write)\n\n### Plan unread newsletters\n\nPropose a deterministic plan first and persist only the exact user-approved digest.\n\n1. `tool:propose_content_plan` — Treat the result as read-only; show dates and counts for review. (read-only; idempotent)\n2. `tool:approve_content_plan` — Call only after explicit approval of the exact proposal digest. (write; confirmation required)\n\n### Recover or pause automation\n\nInspect the recorded state before retrying and give the user a safe stop control.\n\n1. `tool:get_store_of_scope_status` — Use pending and recent run receipts to decide whether to retry, reconcile, or stop. (read-only; idempotent)\n2. `tool:set_automation_paused` — Require confirmation and the current configuration revision. (write; confirmation required)\n\n### Retire Store of Scope state\n\nMake all Store of Scope state handles permanently read-only after explicit confirmation.\n\n1. `tool:get_store_of_scope_status` — Show the user the exact current state revisions and explain that retirement is terminal. (read-only; idempotent)\n2. `tool:retire_workspace` — Call only after explicit confirmation using all four exact revisions. (write; destructive; confirmation required)\n\n## Boundaries\n- Store of Scope does not authorize Google accounts. Use external Gmail and optional Calendar capabilities only after their own connection and permission checks.\n- Never store Google credentials, raw message bodies, MIME content, attachment bytes, or full recipient addresses in workflow receipts.\n- A deployed MCP does not prove that Gmail, Calendar, workbook or PDF rendering, delivery, or scheduled automation is active.\n- Do not claim artifact validation or delivery success without the corresponding external receipt.\n- Obtain explicit approval for initial ingestion, first delivery, future unattended delivery, content-plan writes, and workspace retirement.\n- On a revision conflict, reread status and reconcile; never overwrite newer state silently.\n\n## Examples\n- “Set up Store of Scope.” — use `configure_workspace`.\n- “Run today's newsletter workflow.” — use `run_daily_orchestration`.\n- “Plan three weeks of unread newsletters.” — use `plan_unread_content`.\n- “Pause Store of Scope.” — use `recover_or_pause`.\n\n## MCP surface\n\n[Read the MCP surface reference.](references/mcp-surface.md)\n"
}

SHA-256 of public snapshot: c63b3b492cd8646739ff16664b7a37f982e4ecc85c4c63a60919c2571a3a5b4d