AI & agents

Event-driven agents

Starts an agent run because a durable data event arrived, not because a clock ticked.

RoadmapEngine edition 5f8ea3af

What it does

The engine contains an event dispatcher: subscriptions on durable outbox partitions that match events by filter and start a durable agent run for each match, with loop prevention and quotas. It is separate from the cron scheduler. No route or command mounts it, so it is a roadmap capability.

How it works

Each subscription is backed one to one by an outbox consumer, so offsets, deduplication, bounded retry, dead-lettering and replay are the outbox. A poll reads events after the consumer offset, applies the subscription filter and starts a durable run for each match, recording which event triggered it. Nothing reads a clock to decide whether to fire.

Two independent mechanisms keep a self-referential subscription finite. A self-trigger guard refuses events that belong to runs the same subscription started, and a causal-depth limit (default 4) refuses an event whose producing run is already at the bound. A per-subscription quota window and a hard cap on events per poll bound the work further. The causal chain from event to run to parent run can be queried.

Where you reach it

  • LibraryEventDispatcher and Subscription (Rust crate kynetra-agents; not mounted by the server)

Limits

  • Not reachable through any route, command or setting of the private-preview server.
  • It drives durable runs, which are themselves unmounted.
  • Delivery is at least once; handlers and tools should tolerate a repeat.

Evidence

  • Tests17 test functions cover triggering, filters, deduplication, retries, dead-lettering, replay, quotas and loop prevention that stays finite

Test coverage is listed as present in the engine repository at this edition. This page does not report test results.

KynetraDB is in private preview

This is not available in the preview. Request a preview to discuss the current scope.