Trixie, the rules engine

Rules and compliance · Layer 2

"Write the rule. I'll apply it."

What Trixie does

Trixie checks content moving through the platform against rules you write, such as regulatory requirements, and raises an alert when something is flagged.

Rules, not code

A new requirement means writing a rule. You don't touch production code.

A classifier API

Other services can ask Trixie to classify a piece of content against the active rules.

Checks on write

Content deposited into the platform is classified as it arrives.

Advisory by default

Trixie flags rather than blocks. A flagged item raises an alert in Marco's inbox and notifies the sender, and quarantine is a follow-up action.

Traceable

Rules live in versioned files, so you can see what changed and when, and tie an enforcement decision to the rule behind it.

How it works

Trixie sits on the path content already takes.

  1. Content is written into the platform.
  2. Trixie classifies it against the active rules.
  3. If it's flagged, an alert lands in Marco's inbox and the sender is notified.
  4. A person decides whether to dismiss it or quarantine the content.

Where it fits in the four layers

1 Infrastructure & roles Vera, Grant, the bus, the device registry
2 Data pipeline & state Flo, DynaRAG, the carousel
3 Reasoning & inference Rick, Annie, Max, Hank
4 UI & collaboration Marco, Noted, Norm, the graph

Trixie is on the layer 2 data path: it looks at content as it moves, and publishes its findings as alerts for layer 4 to show.