Automations

An automation is a record in a publication's own backend that says "when this happens, run that procedure with this input". It describes what already runs, links to it, controls it, costs it and shows what it did. It is built and tested.

What a record holds

• A trigger. A monitor that collected a new item, or a story entering a stage (these are Stage Bots).
• A procedure and its static input.
• Controls. enabled, a limit on concurrent runs, and a hop limit for chains.
• Cost. Each run records the tokens it used and what they cost, and the listing totals them.
• History. Every run, with its outcome and the tools it used, so you can see what a bot actually did.
• Run now. Start the procedure by hand, with the same record's input.

Distinctive Mark is the test site. Its first automation wraps the TTAB monitor, which starts the ruling-analysis procedure for each new decision, and its Stage Bots take the ruling from there.

Command line and console

papyrus automations list
papyrus automations show --id distinctive.ttab
papyrus automations runs --id distinctive.ttab

The console has the same list under Administration. Editors and admins can read the list and start a Run now. The details are in the Papyrus repository, in docs/automations.md.