watch_site
Report only the acquisitions new since the last check of this site.
SAR's value for monitoring is its cadence, so the natural workflow is
*standing*: run the same search each time and act only on what changed. This
tool packages that idempotent delta — call it in one turn, come back a day
(or a session) later and call it again, and it returns just the passes
published in between, not the whole list again. The scheduler is you: ask the
agent to check the site, and it reports the delta.
Define the site with the same filters as ``search_catalog`` — ``place``
(geocoded to a bbox), ``area`` (task/site-name substring, loosened by
``fuzzy``), ``bbox``, ``products``, and ``start``/``end`` date bounds. The
watch is identified by a stable ``name`` derived from those filters (pass an
explicit ``name`` to run several independent watches over the same site);
``reset=True`` re-establishes the baseline, reporting everything as new.
State persists in the local catalog index's ``meta`` table (created on first
use), so a watch survives across sessions with no extra setup. ``local``
selects the search backend exactly as in ``search_catalog`` — leave it unset
to use the on-disk index when present and a live S3 walk otherwise; for true
monitoring a live walk (``local=false``) catches freshly published passes.
**No model is called** — this is pure set arithmetic over the deterministic
search — and the returned ``new_items`` are context cards ready to hand
straight to ``change_composite`` / ``timescan``, closing the standing-analyst
loop (new pass → composite → describe) without leaving the conversation.
Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| end | No | ||
| area | No | ||
| bbox | No | ||
| name | No | ||
| fuzzy | No | ||
| local | No | ||
| place | No | ||
| reset | No | ||
| start | No | ||
| products | No |
Output Schema
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||