verify-a-listing-against-its-source

Check an entry against the page its subject publishes, not the aggregator that carried it, and write down only what that page actually said.

Procedure

  1. start start. Goes next to s1
  2. decision Is this the subject's own page?. Goes if aggregator to s2; if default to s3
  3. decision Is there a page the subject publishes?. Goes if carrier_only to s9; if default to s3
  4. decision Is the entry still current?. Goes if gone to s8; if default to s4
  5. action Retire the entry, and say on what evidence, RW (reversible-write), requires approval. Goes on_fail to s9; next to __end_aborted
  6. decision Is this page about only this entry?. Goes if shows_others to s5; if default to s6
  7. end aborted. Terminal
  8. action Take nothing from a page of neighbours, RO (read-only). Goes on_fail to s9; next to s7
  9. action Read the fields, and only what is stated, RO (read-only). Goes on_fail to s9; next to s7
  10. action Write only the empty fields, RW (reversible-write). Goes on_fail to s9; next to __end_success
  11. escalate Leave it as it is and ask. Terminal
  12. end success. Terminal

Open the graph on its own page — larger, printable, and an address you can send.

Walk it without running it — you answer what your environment would answer, and the path, the capabilities, the approvals and the distance back to an undo come out of the document. Nothing executes; there is no Run button here and there will not be one.

How this stands to other procedures

  • requires: this cannot run until that one has — std/enrich-from-pages-you-do-not-control@1.0.0 — The fetch-level rules — what a refusal means, what a status code means, when a browser is needed — are there and are not repeated here.

See it as a composition — what running all of it would grant, and whose trust level it would really carry.

Trust

T2 · attested 2026-10-11 · runbooks.directory

Nobody has attested this record. That is the ordinary case: T2 is what the catalog can check on its own, and T3 needs somebody to run the procedure and sign for it.

  • Link liveness has not been checked: it needs a network and the catalog builds without one. Run pnpm gates --online where there is one.

Steps

  1. s1 decision — Is this the subject's own page?
  2. s2 decision — Is there a page the subject publishes?
  3. s3 decision — Is the entry still current?
  4. s4 decision — Is this page about only this entry?
  5. s5 action — Take nothing from a page of neighbours (read-only)
  6. s6 action — Read the fields, and only what is stated (read-only)
  7. s7 action — Write only the empty fields (reversible-write)
  8. s8 action — Retire the entry, and say on what evidence (reversible-write) — requires approval
  9. s9 escalate — Leave it as it is and ask

Capabilities

This is a privilege request. Check it against your own allowlist before running.

  • cli:psql — used by s7

Provenance

Source
https://runbooks.directory/r/std/verify-a-listing-against-its-source/source.md
Fetched
2026-09-04
Source last checked
not since it was captured on 2026-09-04 — recorded as current
Licence
CC-BY-4.0
How it got here
Written by this catalog's maintainers and reviewed in full.
Highest risk in this procedure
reversible-write

Take it with you

Run it under supervision

Runs here, on your machine, under supervision: every step is proposed before it happens, an approval gate stops for you, and a failed expectation goes where the procedure says rather than on to the next step. Nothing is sent anywhere. To supervise an agent that is doing the work instead, runbooks hook sits in its tool-call path.

npx @runbooks/cli run std/verify-a-listing-against-its-source@1.0.0 --as "$(whoami)" \
  --input entry_id=<the entry being verified> \
  --input source_url=<the page published by the subject itself, not by an aggregator>