Generated from folio-assistant-core/processes/content/record-agent-step.bpmn by gen-processes-viz.ts — do not edit here. All processes · folio-assistant-core processes

Record agent step

Process_RecordAgentStep · strict (defaulted) · 3 step(s)

The one way an agent reports a move on a change set. The sheet script builds Agentic status, Agentic status (filter) and Staging review from the Agent tab, and warns that no agent has picked a row up when the Agent step is missing or older than Ready for agent. Writing only Feedback (agent) leaves those columns stale, so it is never done alone.

BPMN diagram: Record agent step

How it connects

  • Called by: Review-log watch
  • Calls: none
  • Presented on: no docs page section shows this diagram
  • Running instances: none recorded

Lanes — who acts

lanerolewhat it does here
Authoring agentauthoring-agentThe agent working the change set (or the log watcher writing on its behalf). Writes the Agent row first, then Feedback (agent) from that row, and reads back the sheet so the copied columns agree.

Steps

Every one of the 3 step(s) is documented.

steplaneskill / sub-processwhat it does
Write the change set’s Agent row
Task_WriteAgentRow
Authoring agentreview-sheet-agent-columnsOn the Agent tab, the change set’s row: Agentic status (Not started, Working, PR open, Ready for review, Change merged or Needs human); Pull request; Staging review page; Staging built, PR head, Staging built from and Staging deploy from agent-record.ts push; and Agent step from agent-record.ts step <name>, exactly “<step> <YYYY-MM-DD HH:MMZ>” with a step from the fixed list (reading, proposing, editing, pushing, staging, deploying, qa-review, merging, proposed, idle). Prose in Agent step is not read: use idle when the row waits for people. A preview or review link is written only once it is live: the GitHub Pages deploy of a gh-pages commit at or after the preview’s publish has succeeded, and an HTTP GET of each link answers 200 where the agent can reach the site. A publish that is only on the gh-pages branch is not live: Pages deploys can be queued for many minutes or cancelled by the next push. Until then Staging review page stays empty, Staging deploy says deploying, and Feedback (agent) says “Preview deploying” with no preview link.
Write Feedback (agent) from that row
Task_WriteFeedback
Authoring agentreview-sheet-scriptFeedback (agent) in the fixed layout (the ask first, then Status: and Next:), linking the same pull request and preview the Agent row now names. In a log one watcher owns, another thread sends the watcher its step and links instead of writing the sheet. A preview or review link is written only once it is live: the GitHub Pages deploy of a gh-pages commit at or after the preview’s publish has succeeded, and an HTTP GET of each link answers 200 where the agent can reach the site. A publish that is only on the gh-pages branch is not live: Pages deploys can be queued for many minutes or cancelled by the next push. Until then Staging review page stays empty, Staging deploy says deploying, and Feedback (agent) says “Preview deploying” with no preview link.
Read back Agentic status and Staging review
Task_ReadBack
Authoring agentreview-log-watchAfter the script’s next run, read the row’s Agentic status, Agentic status (filter) and Staging review. They must name the pull request and preview that Feedback (agent) names, and show no “no agent has picked this up” warning.

Decisions

1 of 1 decision(s) carry no documentation — gateway-documented lists them.

decisionwhat decides itbranches
Sheet agrees with Feedback (agent)?
Gateway_Agrees
—no: fix the Agent row, never the copied columns → Write the change set’s Agent row
yes → Step recorded

folio-assistant — code under the Apache License 2.0, documentation under CC BY 3.0. Generated schema and API references are rebuilt from source on every push to main.

deployed dev