---
name: source-change-watch
description: "Name the pages to watch. Get a source comparison; a failed check never reads \"no change\"."
---

# Watch official sources for changes

Use the official URLs and change criteria in my brief. First save a dated baseline with each URL, access result and the relevant content or source locator. On a later authorized check, compare against that saved baseline. Do not infer a change from a failed fetch.

Save source-watch.md and the baseline/comparison evidence in the authorized location. For every source record Changed, Unchanged or Check failed. For a change include the old and new evidence, date checked, why it matters and any uncertainty about when it occurred. Retain the previous baseline and show what was compared. Stay quiet for unchanged sources unless I request routine reports; report a relevant change, failure or required decision.

This instruction alone does not create a recurring job. If I explicitly request recurring monitoring, use the host’s supported schedule controls, show the scope, cadence, time zone, storage location, notification rule and runtime requirements, and confirm the saved schedule status. If unavailable or unconfirmed, report “Not scheduled” and leave a proposal. Do not claim monitoring is active from a connected source or completed one-off run. Do not post externally or change source accounts.

## Required inputs

- A small named list of official URLs and the changes that matter
- Baseline location, later check time and notification rule

## Expected outputs

- Dated baseline or comparison report
- Evidence for each change
- Schedule proposal or host-confirmed schedule details

## Checks

- Every source has a result, including failed checks.
- Change evidence identifies both baseline and later observation.
- The report distinguishes detection time from an unknown change date.
- An active schedule claim includes a host-confirmed saved job and its requirements.

## Limits

- Local schedules require the supported computer/app runtime. Cowork tasks that need local files or apps run locally; cloud runs need remotely accessible inputs.
- Dot access, connected tools and schedules vary by plan, rollout and workspace.
- Copying a prompt or connecting a source does not activate monitoring.
- Self-hosted agents require operator-managed permissions, hosting and delivery configuration.

Revision: 2.0.1. [Read the complete kit](files/README.md) before use. This optional format is not a claim of support by every tool.