enrich-from-pages-you-do-not-control

Fill fields from pages somebody else serves, at volume, without recording a guess as a fact or a refusal as an answer.

Procedure

  1. start start. Goes next to s1
  2. check Fetch one page, read its status code. Goes on_fail to s10; next to s2
  3. decision What did the fetch actually get?. Goes if refused to s3; if needs_browser to s4; if gone to s9; if default to s5
  4. action Record the refusal as a refusal, RW (reversible-write). Goes on_fail to s10; next to s9
  5. action Queue it for a browser, after the cheap pass, RO (read-only). Goes on_fail to s10; next to s9
  6. decision Does the page carry structured markup?. Goes if prose_only to s6; if default to s7
  7. action Write a rule for this family, not for all, RO (read-only). Goes on_fail to s10; next to s7
  8. decision Did this field ever arrive?. Goes if never to s8; if default to s9
  9. action Stop promising the field, or take it from text, RW (reversible-write). Goes on_fail to s10; next to s9
  10. action Write what was read, and leave the rest empty, RW (reversible-write), requires approval. Goes on_fail to s10; next to __end_success
  11. escalate Stop before the batch runs. 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.

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 check — Fetch one page, read its status code
  2. s2 decision — What did the fetch actually get?
  3. s3 action — Record the refusal as a refusal (reversible-write)
  4. s4 action — Queue it for a browser, after the cheap pass (read-only)
  5. s5 decision — Does the page carry structured markup?
  6. s6 action — Write a rule for this family, not for all (read-only)
  7. s7 decision — Did this field ever arrive?
  8. s8 action — Stop promising the field, or take it from text (reversible-write)
  9. s9 action — Write what was read, and leave the rest empty (reversible-write) — requires approval
  10. s10 escalate — Stop before the batch runs

Capabilities

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

  • cli:curl — used by s1

Provenance

Source
https://runbooks.directory/r/std/enrich-from-pages-you-do-not-control/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/enrich-from-pages-you-do-not-control@1.0.0 --as "$(whoami)" \
  --input sample_url=<one page from the family being measured>