Skip to content

Define alert routing protocol — where do Janus findings go? #3

@koad

Description

@koad

Janus detects signals but has no defined output protocol. Where do alerts go?

Current gap: The CLAUDE.md says 'I file issues; I don't resolve them' but doesn't define the routing rules.

Proposed routing:

  • Critical (trust bond tampering, unauthorized commits, entity silent for 48h+): Keybase message to koad immediately via ssh juno@dotsh 'keybase chat send koad "..."'
  • Warning (pipeline stall, Veritas backlog, unassigned issue 24h+): GitHub issue on koad/janus with label alert
  • Info (daily pattern summary, commit volume, issue activity): daily log in ~/.janus/watch/YYYY-MM-DD.md

Output: ~/.janus/protocols/alert-routing.md — canonical routing table.

Dependency: koad/vesta should eventually spec this. For now Janus defines her own working protocol.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions