Oliver Kieselbach 22a8c7a51d rules: hard-block high-frequency event types as evaluateOn on_event triggers ...

A warning does not stop an end user — telemetry-cadence types (performance_snapshot,
agent_metrics_snapshot, download_progress, network_state_change/connectivity_check,
log_entry, agent_trace, stall_probe_check) would turn every ingest batch into an
analyze run. Now enforced in three layers:

- AnalyzeRuleTriggers.BlockedOnEventTypes (code-only enforcement): CRUD write is
  rejected with an explicit message, and OnEventTypes() drops blocked types at
  runtime so even a persisted row (pre-validation data, direct table write) is
  inert for the trigger registry and the engine alike.
- rules/guardrails.json gains blockedInterimTriggerEventTypes as the display/
  pre-flight mirror (baked into the MCP RULE_GUARDRAILS via combine.js); a
  parity test pins mirror and code set against drift — same pattern as the
  gather hard blocks.
- MCP validate_rule: the high-frequency finding is now an ERROR sourced from the
  baked mirror, not a hardcoded warning.

Suites: Backend 4155, MCP 548.

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>

2026-08-14 16:07:39 +02:00

..

analyze-rule-triggers.md

rules: hard-block high-frequency event types as evaluateOn on_event triggers

2026-08-14 16:07:39 +02:00

gather-rule-guardrails.md

gather-rules: mirror hard blocks in portal/MCP, stamp author on PUT-upsert; agent: bootstrap retry tests

2026-08-11 12:29:05 +02:00

gather-rule-phase-scoping.md

fix(agent): gather phase/event triggers follow the engine-reduced timeline

2026-08-04 14:44:35 +02:00

rule-authoring-surface.md

Logparser pattern testing with the agent's exact .NET engine (test_log_pattern) (#125)

2026-08-05 22:48:10 +02:00