AGENTS.md amendment: cross-verify magnitude claims (two-night escalation trigger fired)
cancelledAgent: carson-engineer
Priority: 2
Two-night escalation from 2026-06-22 reflection AI#2: ship as same-cron sub-agent doc-only PR. Add a new subsection to AGENTS.md (near the "Silence is not absence" section) titled "Cross-verify magnitude claims". Body approximately:
---
## Cross-verify magnitude claims
Any reflection or planning step that asserts a magnitude about authored work, fleet-task state, or PR counts (e.g. zero, all, none, first-time-in-arc, dissolved, fully clean) MUST be cross-verified via a sub-agent or heartbeat with a known-good auth context before becoming load-bearing in next-cycle planning.
Cron-context tool failures (May 8 stale gh token, May 15 Fleet API 403, May 18-20 no mono mount, June 13 BOLT-1204 recall miss, June 21 phantom-zero-authored-PRs) produce false-confident state. Treat empty results from cron-context `gh` / `gh pr list` as "unknown," not "zero," until verified via sub-agent at lease time.
**Operator rule:** Pre-flight should ask "are any magnitude claims in this reflection depending on `gh`/repo-mounted tools? If yes, queue a verification sub-agent and downgrade the claim to provisional until verification returns."
---
Workflow:
0. `eval "$(~/bin/gh-fleet-token.sh)"` (isolated standalone line). Verify GH_TOKEN length=40.
1. `git fetch origin main && git checkout -B kai/agents-md-cross-verify-magnitude-claims origin/main`.
2. Set git identity: `git config user.email [email protected] && git config user.name texture-coding-agent`.
3. Create Linear issue (use LINEAR_API_KEY fallback if op unavailable): title "Codify cross-verify magnitude claims operator rule in AGENTS.md", team BOLT, labeled docs. Capture BOLT-XXXX.
4. Edit `/home/agent/agents/carson-engineer/AGENTS.md`: insert the new subsection above or below "Silence is not absence".
5. `git add AGENTS.md && git commit -m "docs(agents-md): cross-verify magnitude claims (BOLT-XXXX)"`.
6. `git push -u origin kai/agents-md-cross-verify-magnitude-claims`.
7. `gh pr create --repo TextureHQ/mono --base main --head kai/agents-md-cross-verify-magnitude-claims --title "docs(agents-md): cross-verify magnitude claims (BOLT-XXXX)" --body "<concise body referencing BOLT-XXXX + June 21 phantom-zero-PRs evidence + the codified operator rule>"`.
8. PATCH this task to completed with result.pr_url, result.linear_url, result.branch.
9. No Slack DM. Routine doc PR; next standup will mention it.
Guard: if any step fails (auth, lint, push), PATCH status=blocked with metadata.blocked_reason and surface in June 24 standup.
Event Timeline
created
status_change
queued → in_progress
status_change
in_progress → blocked
status_change
blocked → cancelled