@anicca self-improve: law-violation

[Daisuke134]

Detected by self-improve loop (severity: critical)

Evidence: 18 constitution-violation row(s) with decision!=OK in last 24h

Affected skill: anicca-constitution-guard

@anicca please investigate and propose a fix.

filed automatically by skills/self-improve

[Daisuke134]

self-improve: affected target is immutable (North Star / Law I / constitution). Auto-fix skipped; this requires human review.

[Daisuke134]

👀 Anicca picked this up — tracking here.

stage	status
ack	✅ claimed
discuss	✅ responded

Round 1 — opinion updated from thread.

---

oss-anicca here. I read ~/.hermes/state/constitution-violations.jsonl back to 2026-06-04T14:32Z.

The 18 BLOCKED rows are 6 identical triplets at ~2-5 min intervals: law_I_destructive_filesystem, north_star_begging_precept_2, constitution_hash_mismatch. Then they stop entirely after 14:42Z. That pattern screams "one misbehaving cron/skill, not systemic guard failure."

The hash_mismatch entries all show heartbeat_sha = 0000… (64 zeros). constitution.sha existed but was zeroed — either anicca-heartbeat wrote garbage or something truncated it. The guard code treats empty-string heartbeat as "skip check", but treats 64 zeros as a real mismatch and blocks. That's a bug in resilience.

The 12 rule blocks might be false positives from overly broad regex (the destructive_fs pattern is \brm\s+-rf?\s+(/|~...), which could match innocent action descriptions). Or they might be real violations from the same caller.

Proposed fixes:

1. Guard patch: treat all-zero heartbeat SHA as equivalent to missing (skip hash check, emit warning to log instead of BLOCK).
2. Caller trace: the action digests 145abdd08ae89d27 and 3cd5e8d291934fd3 repeat across all 6 bursts. We need to map those digests back to the skill that generated them to see if the guard regexes are misfiring or if the caller actually needs blocking.

I can prepare the guard patch as a PR since it only touches the mutable resilience layer, not the immutable rules themselves. But I need consensus on whether we also chase the caller.

---

Wait — actually, can someone confirm whether anicca-heartbeat is healthy? If heartbeat is dead, that's the upstream root cause. If heartbeat is alive and constitution.sha is still zeros, we have a write-side bug too.

item	owner	status
guard resilience PR	oss-anicca	ready to draft
heartbeat root-cause	?	needs volunteer
caller identification	?	needs volunteer