05 / PROTOTYPE EVIDENCE

A working system.
Not a concept slide.

The prototype backend is deployed, its rules live as structured data, and a successful test request returned a specific compliance decision with the rule and reasoning that produced it.

OBSERVED TEST RESPONSEHTTP 200
STATUSnon_compliantdecision returned
MATCHED RULEB2
RETURNED CONTEXT

Rule name · Severity · Priority · Reasoning

Representative fields from a successful prototype test—not a customer result or performance claim.

CURRENT PROTOTYPE PATHLIVE BASE
01Customer AIprompt + API key
→
02Zuplogateway validation
→
03Vercel / FastAPIrequest handling
→
04Airtable rulesactive structured policy
→
05Evaluationstructured decision
See the beta implementation notes+
01 / STRUCTURED RULES

Rules are data, not one long prompt.

The rule library records identifiers, names, categories, priority, status, chatbot type and severity.

02 / CONTROLLED ACCESS

Each beta user gets an API key.

The current onboarding flow is deliberately manual while the product is being tested—there is no claim of automated billing.

03 / CLEAR SEPARATION

Policy context stays separate.

The beta specification keeps compiled governance rules in model-level context and the raw user prompt in the user-message channel.

NOWWorking base-level prototype

Moving from technical proof toward customer validation with smaller businesses.