Core monitoring infrastructure — detection patterns, alert routing, atom feeds

[koad]

Consolidates

• Setup: initialize atom feed watching on fourty4 #2 — Setup atom feed watching on fourty4
• Define alert routing protocol — where do Janus findings go? #3 — Define alert routing protocol
• Track trust bond expiration and credential age #4 — Track trust bond expiration and credential age
• Define silent blocker detection — unblocking patterns #5 — Define silent blocker detection
• Define orphaned work detection — unassigned & unclaimed issues #6 — Define orphaned work detection
• Define systemic pattern detection — collective signals across entities #7 — Define systemic pattern detection
• Define cascade failure detection — downstream impact tracking #8 — Define cascade failure detection

Shape

All seven were day-3 scaffolding for Janus's monitoring system. None were started. This issue tracks the whole system as one deliverable:

1. Atom feed setup on fourty4 — watch all team repos
2. Alert routing — critical → Keybase, warning → GH issue, info → daily log
3. Detection patterns — trust bond expiry, silent blockers, orphaned work, cascade failures, systemic signals
4. Credential age tracking — key rotation, bond TTLs

Blocked on

• Janus actually running (needs fourty4 setup or dispatch from wonderland)
• Daemon infrastructure for scheduled runs

Prior art

Janus #10 (orphaned pipeline observation), #12 (GitHub API monitoring), #13 (signed code block consensus), #14 (skills↔commands mapping) remain as separate issues — they're distinct work items, not part of this scaffolding cluster.

[koad]

Baseline scan filed today (flight 10, 2026-04-14).

File: ~/.janus/briefs/atom-stream-baseline-2026-04-14.md

Current state documented (github-feeds.sh running, no signature verification yet).

5 monitoring gaps flagged:

1. github-feeds.sh watches GitHub commit feeds, not entity feed.atom content
2. No signature verification in watch cycle (needed when Mercury Phase 2 ships)
3. No WebSub hub liveness check (Phase 3)
4. No OPML staleness detection (Phase 4)
5. Context injection loop (Phase 5) — no silent-failure monitoring design

Also surfaced Mercury's bad -pkeyopt digest:sha512 signing command — confirmed by Veritas, amended in SPEC-101 §7.2 by Vesta, fixed in Mercury's plan.

Additionally: watchers/github-discussions.sh shipped (flight 23) — discussions.atom watcher for all 13 entity repos, auto-baselines when koad enables.