separate-people-from-automation-in-traffic

Make a rate mean something by counting a denominator every response passes through and a signal only a person can produce, without joining the two.

Procedure

  1. start start. Goes next to s1
  2. check Look at the shape, not the total. Goes on_fail to s9; next to s2
  3. decision Is the traffic mixed?. Goes if mixed to s3; if default to s8
  4. action Stop publishing rates over the total, RW (reversible-write). Goes on_fail to s9; next to s4
  5. action Count the denominator where every response goes, RW (reversible-write). Goes on_fail to s9; next to s5
  6. action Record a signal only a person leaves, RW (reversible-write). Goes on_fail to s9; next to s6
  7. check Time counts only while the tab is visible. Goes on_fail to s9; next to s7
  8. action Give both tables the same dimensions, RW (reversible-write). Goes on_fail to s9; next to s8
  9. check The rate is over the denominator it means. Goes on_fail to s9; next to __end_success
  10. escalate Report no rate rather than a wrong one. Terminal
  11. 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 — Look at the shape, not the total
  2. s2 decision — Is the traffic mixed?
  3. s3 action — Stop publishing rates over the total (reversible-write)
  4. s4 action — Count the denominator where every response goes (reversible-write)
  5. s5 action — Record a signal only a person leaves (reversible-write)
  6. s6 check — Time counts only while the tab is visible
  7. s7 action — Give both tables the same dimensions (reversible-write)
  8. s8 check — The rate is over the denominator it means
  9. s9 escalate — Report no rate rather than a wrong one

Capabilities

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

  • cli:psql — used by s1, s8

Provenance

Source
https://runbooks.directory/r/std/separate-people-from-automation-in-traffic/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/separate-people-from-automation-in-traffic@1.0.0 --as "$(whoami)" \
  --input window_days=<how many days the figures cover>