Fulcra Agent Health
Enhances fulcra-agent-teams. When a team is healed by
scheduled reconciles across several machines, the operational questions are "is anything actually
running?" and "which host went dark?" — this skill answers them deterministically. (The digest +
role-escalation sweep land here too — A5b.)
How it works
- Every
coord-engine reconcilewrites a small health shard (_coord/health/<host-key>.json: host, timestamp, engine version, task count, warnings) and prunes shards older than 30 days (age-based GC). coord-engine health <team>folds the shards: per-host last-reconcile age, STALE flag (>24h), engine version — exits non-zero when no host is fresh (usable as a monitor probe).coord-engine doctor [team]is the local preflight: storage CLI on PATH, File Store reachable, engine version. Run it after install and inside scheduled jobs' self-tests (the parent project's heartbeats failed silently on exactly these).
Operator digest (A5b)
coord-engine digest <team> folds the aggregate + presence into the four operator questions:
blocked on you (needs:human tags / tasks assigned to your handle — env FULCRA_COORD_HUMAN),
upcoming (not_before within 7 days), agents (liveness + open work each), and stale
(active tasks untouched > 48h). --store persists it to _coord/digests/<date>-<window>.md, deduped
per day+window (morning/evening) — heartbeat-safe. --emit-timeline additionally lands the digest as
a moment on the 'Agent Tasks — Digest' timeline track: the record id is deterministic per
(team, day, window) and the typed ingest endpoint upserts on explicit ids (live-verified 2026-07-14),
so fleet races and retries converge on one record; a failed emit warns loud, keeps rc 0, and retries
on the next heartbeat tick (the .emitted state is written only after a confirmed emit). Requires the
fulcra_common writer installed next to coord-engine — without it the emit degrades to a loud warn.
Role-vacancy escalation (A5b)
coord-engine escalate <team> sweeps every role doc: if a role is VACANT past its sla_hours and
today's marker doesn't exist, it writes the marker and files a P1 directive to the role's
maintainer ("claim it or reassign"). Idempotent per day; run it from the heartbeat.
Usage
coord-engine doctor <team> # preflight; exit 0 = healthy
coord-engine health <team> [--json] # fleet fold; exit 1 if no fresh reconciler
coord-engine digest <team> [--human H] [--json] [--store] [--emit-timeline]
coord-engine escalate <team> # vacancy sweep (heartbeat-safe)
When to use
- After installing coord on a new machine (doctor).
- In monitoring/heartbeat wrappers (health --json; alert on
healthy: false). - Diagnosing "the index looks stale" — health shows which reconciler stopped.