fleet-pulse.yml — the daily loop

fleet-pulse.yml — the daily loop A workflow diagram generated by Archify. 01 / Trigger 02 / pulse job — gather (deterministic) 03 / Memory (_data/) 04 / pulse job — plan 05 / doctor job (Opus agent) EX / Escalation Sense Derive + publish Act (bounded) Daily cron · fleet.yml cadence · Trigger › Sense Daily cron fleet.yml cadence Gather · actions · triage · pulse job — gather (deterministic) › Sense · PyGithub Gather actions · triage PyGithub Scorecard · trip wires · pulse job — gather (deterministic) › Derive + publish · offline Scorecard trip wires offline publish-data · → _data/*.yml · Memory (_data/) › Derive + publish · one commit publish-data → _data/*.yml one commit Remediate · one fix queue · pulse job — plan › Derive + publish · capped Remediate one fix queue capped Doctor agent · reads run logs · doctor job (Opus agent) › Derive + publish · --max-turns Doctor agent reads run logs --max-turns Draft PR · hub or submodule · doctor job (Opus agent) › Act (bounded) Draft PR hub or submodule Fallback issue · no fix found · Escalation › Act (bounded) Fallback issue no fix found signals commit red + expensive token probed fix cannot fix Legend Agent logic Policy Context / trace Cloud service External system

One job, one commit

  • • Four predecessors died silently on a bare git push
  • • publish-data commits once, falls back to a PR
  • • needs: pulse replaces the skipped workflow_run

Deterministic first

  • • Every signal is gathered by code, not an agent
  • • Red and expensive workflows become one keyed queue
  • • fleet.yml caps are paired to --max-turns

Bounded action

  • • FLEET_TOKEN is probed with a real API call
  • • Output is a draft PR in the hub or the owning repo
  • • No fix → a hub issue, so nothing fails quietly