Portal Community
What GuardRails Does Every node execution in BizFirst AI runs through a configurable pipeline of guards. Guards check inputs, enforce rate limits, detect PII, apply timeouts, and redact sensitive data from outputs — all automatically, with zero changes to individual node code.

The Core Idea

In a multi-tenant AI workflow platform, every node execution is a potential risk surface. A single unguarded node can leak customer PII, allow runaway API calls, or fail silently when a downstream dependency goes down. GuardRails solves this by adding a policy enforcement layer that is:

Three Execution Phases

GuardRails intercepts every node execution at three points:

1

Pre — Before the node runs

Validates inputs, checks rate limits, verifies circuit breaker health, starts the timeout clock, and detects PII in the incoming data. If any security-critical guard blocks, the node never executes.

N

Node Execution

The actual node logic runs: sends email, calls API, queries database, invokes AI model, etc.

2

Post — After the node succeeds

Checks the elapsed time against the timeout, redacts PII from the output before it reaches the caller, and validates the output schema.

!

Error — When the node throws

Records circuit breaker state, writes audit violations, logs the exception. Error handlers never block — they observe and record only.

Built-in Guards

What's in This Guide

Status: Phases 1–4 Complete 81 tests passing. Domain contracts, Service layer, Provider.Core, Provider.PII guards, and BaseNodeExecutor integration are all production-ready. Phase 5 (full PII pipeline dispatch) and Phase 6 (Octopus agent integration) are planned.