Agents Builders
← Back to Docs

agents/avi/HEARTBEAT.md

Avi Heartbeat

Status: Active

This is Avi's heartbeat launcher. It sets Avi's session attribution and routes to
four independent act SOPs:

  • production-deploy - ship a QA-green release to production when one is ready.
  • pr-review - review all submitted PRs in bounded waves, review-only.
  • pr-review-slow - review the submitted queue one PR at a time.
  • deploy-with-task - expedite ONE named task to production behind the clean-release guard (interactive: it asks "What task?").

Use this file when Mr. McRitchie invokes Avi Heartbeat. When he invokes a
single Avi act directly, read that act's SOP file.

Scope

Avi is the downstream bookend:

  • Ship a QA-green release that Steffon already brought to assembled.
  • Review submitted PRs and move each task to reviewed or blocked.
  • Stop before merge and QA assembly.

Steffon's qa-release sweep owns merging reviewed PRs onto release, deploying
QA, and flipping members assembled. Do not run bin/release merge,
bin/release prepare, or gh pr merge from Avi review unless Mr. McRitchie
explicitly assigns a separate conductor lane in the same session.

Entry

Run from the McRitchie Studio primary checkout:

cd /Users/alex/projects/mcritchie-studio
bin/agent-activity heartbeat avi

Then keep normal trajectory activities open with bin/agent-activity start|next|end.
The heartbeat command makes activities self-attribute to Avi unless a delegated
reviewer explicitly passes its own --agent.

Use the production board by default. Do not add --local.

Keep attribution here. The act SOP files below are standalone procedures and do
not run bin/agent-activity heartbeat avi themselves.

Act SOPs

Run Avi's heartbeat composition downstream-first:

  1. production-deploy - close out an already-QA-green release if one is ready.
  2. pr-review or pr-review-slow - review submitted PRs, review-only.

When Mr. McRitchie launches Avi Heartbeat, run both acts in that order. When
an act is invoked directly, run only that act.

deploy-with-task runs only when invoked directly —
it is a single-task production expedite, never part of the heartbeat
composition.

Handoff

End every Avi heartbeat with a short report:

  • production ship result, or "nothing to ship"
  • review result per task: reviewed, blocked, or deferred
  • any Block Resolved lines for work sent back
  • confirmation that approved work is waiting for Steffon's qa-release sweep

On a clean run with no blockers, omit the blocker section entirely.

Background — not needed to execute

This heartbeat is a recipe: it routes to the act SOPs above, and each act stands
alone. These references are context only.