Repository navigation
Health Scorecard
The Health Scorecard turns the verify-suite's JSONL check records into a
weighted Health Index across eight families (memory persist+recall,
plan-adherence+drift, verification honesty, capability function, memory
freshness+experience, efficiency, docs+voice health, safety/recoverability).
Family weights, the schema, and the dark-checks registry (designed-not-built
capabilities, tracked separately so they never count for or against the
index) are documented in
scripts/health/README.md.
The scorecard is no longer a page this wiki renders. Two producers exist, and neither commits anything back to this repo:
-
The local runner (
scripts/agentm-runner.sh, a launchd tick on this machine) runs thehealth-passjob daily (templates/jobs/health-pass.yaml): the fast tier feedsscripts/health/health_score.py --history --html, which appends one row to the health-history ledger in the engine state directory (~/.local/state/agentm/health/history.jsonl;$AGENTM_STATE_DIRoverrides it — machine state left the vault in filing-v2 part 2a, and the directory is a git repo the runner commits, so history-as-durability moved with it) — and renders the HTML report to a fixed device path./consoleand the morning brief link it. -
.github/workflows/health-nightly.ymlruns both the fast and heavy tiers on a schedule as the clean-runner regression signal, renders the same HTML report, and uploads it (plus the raw JSONL records) as a build artifact — advisory only, never a merge gate, and it writes nothing to the repo or the vault.
The canonical local path is:
~/.cache/agentm/telemetry/scorecard.html
GitHub renders no clickable file:// links on a wiki page — that's a
platform limitation, not a bug — so the block above is meant to be
copy-pasted into a browser's address bar or opened directly, not clicked
from here. Obsidian opens local files, so a note in your vault can carry
a real clickable link to it.
python3 scripts/status.py (or /console) prints the last-recorded Health
Index, the per-family breakdown, and the dark-check count from the same
ledger — on demand, no re-scoring. See
CI gates for how the nightly tiers fit into the rest of the CI
picture.