Feature

Reflexes

Declarative triggers. CX in, webhooks out.

Reflex

How it works

Reflexes

A Reflex owns a CX expression and decomposes into one or more Motifs. When the live graph satisfies a Motif, a Locus materialises; the Reflex fires per Locus.

YAML-first DSL — declare what to watch, not how to poll
CX expresses structural patterns, negation, aggregation, correlation, reachability

Primitive

Reflex

Declarative triggers. CX in, webhooks out.

In practice

Built for replay, audit, and scale.

One entity covers structural completion (a supplier going bankrupt) and scalar drift (sentiment exiting a band). No specialized trigger types, no second registration surface.

Cooldown is per Locus — one noisy entity does not throttle the others
Every webhook delivery includes affected entities, reasoning chain, and change delta

# Declare a Reflex once, fire on every match.
reflex:
  name: supplier-risk-spike
  watch:
    cx: entity(supplier).risk_score > 0.75
  fire:
    webhook: https://hooks.example.com/supplier-risk
    cooldown: 1h

Pair it with these primitives.

Synapta

Memory Graph

Entities, relationships, embeddings — one unified graph.

Packet

Context Packets

The only output shape — provenance assembled in stages.

Citation

Verified Citations

Every fact traces back to its source line.

Try Reflexes on your stack.

Book a 30-minute walkthrough or wire it up via the API.

Book a demo Back to features