CatalystVisual

06 Data Flow

Evaluation Data Flow and the PII Boundary

Where the caller's attributes cross the wire, and the narrow window after which they are never handled again.

The caller's user_id and attributes travel to the API, get matched against rule conditions, and are then written nowhere. What persists is configuration only: keys, defaults, kill-switch state, rollout percentages, and rule conditions. The response carries a value, a reason, and a rule id, but never the attribute that produced the match.

What to look for

  • Trace the security-coloured flow: that is the only place PII enters the system.
  • Everything after the gate is configuration. The cache holds nothing else.
  • The evaluator performs no I/O at all, which is what makes the SDK mirror trustworthy.