put-an-item-on-a-public-feed

Publish one item to a feed strangers read, with the address assigned once by the server and kept even after the item comes off again.

Procedure

start start. Goes next to s1
decision Is this fit for a stranger to read?. Goes if not_fit to s8; if default to s2
action Record why it is not for the feed, RO (read-only). Goes next to __end_aborted
check Whether it has been on the feed before. Goes on_fail to s7; next to s3
action Turn the visible flag on, RW (reversible-write). Goes rollback to s6; on_fail to s7; next to s4
check The server assigned the address, not the caller. Goes on_fail to s7; next to s5
decision Does it read correctly to a stranger?. Goes if wrong to s6; if default to s9
action Take it off the feed, keeping its address, RW (reversible-write). Goes on_fail to s7; next to __end_aborted
action Note the address it now holds, RO (read-only). Goes next to __end_success
escalate Escalate to whoever owns the feed. Terminal
end aborted. Terminal
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

s1 decision — Is this fit for a stranger to read?
s2 check — Whether it has been on the feed before
s3 action — Turn the visible flag on (reversible-write)
s4 check — The server assigned the address, not the caller
s5 decision — Does it read correctly to a stranger?
s6 action — Take it off the feed, keeping its address (reversible-write)
s9 action — Note the address it now holds (read-only)
s7 escalate — Escalate to whoever owns the feed
s8 action — Record why it is not for the feed (read-only)

Capabilities

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

cli:curl — used by s2, s3, s4, s6

Provenance

Source: https://runbooks.directory/r/std/put-an-item-on-a-public-feed/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

SKILL.md — the record as an Agent Skills file
workflow.yaml — Open Workflow DSL 1.0.3, for a runner
record.json — the catalog's own JSON
graph.svg — the graph, standalone

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/put-an-item-on-a-public-feed@1.0.0 --as "$(whoami)" \
  --input item_id=<the item being considered for the feed> \
  --input admin_api=<base address of the administrative API that owns the flag>