Expand description
yah-tower — rule-driven monitor on scryer (Phase 2).
This crate holds the rule engine: compiling TowerRule predicates to
ScryerFilter shapes, parsing rules from YAML/JSON, and validating rules
before they are loaded. The supervisor (F3), dispatch engine (F4), and
trigger families (F5) will live here too when those tickets land.
Architecture: .yah/docs/architecture/A052-yah-tower.md
Modules§
- dispatch
- Dispatch engine: capture event payload, render trigger, record tower.dispatch audit trail.
- event
- Minimal event type for tower-internal use.
- rules
- scryer_
filter ScryerFilter— the subscription filter shape tower hands to scryer.- simulate
- Dry-run a
TowerRuleagainst historical events from scryer. - storage
- Rule storage: per-machine
.yah/cloud/rules/*.yamlwith config-file watcher. - supervisor
- Subscription supervisor: per-rule scryer subscriptions, dedup, rate limiting.
- triggers
- Trigger family implementations: AgentDispatch, Notification, YubabaAction.