Arjuna Badger Press

The police + judge guardrail

Part of the technology exposé. The two-layer safety gate that runs on both the studio's own pipeline and the Buabantu API — fail-closed.

Any system that lets text flow through a model needs a boundary. The studio's guardrail is built in two layers, cheapest first, and it fails closed: if it can't be sure, it blocks.

flowchart LR
    IN[Text · request or response] --> L1{Layer 1 · Policeman<br/>deterministic regex/patterns}
    L1 -->|clear violation| BLOCK[[BLOCK · BOUNDARY_EXCEEDED]]
    L1 -->|clean| PASS([allow])
    L1 -->|ambiguous| L2{Layer 2 · Judge<br/>small swappable model}
    L2 -->|violation| BLOCK
    L2 -->|clean| PASS
    L2 -->|unreachable / unsure| BLOCK
    classDef gate fill:#1b1b1b,stroke:#d4af37,color:#fff;
    class L1,L2 gate;

Layer	What	Cost
1 · Policeman	deterministic regex/patterns for high-confidence violations — self-harm, non-consensual, CSAM elicitation, prompt-injection, jailbreak, egress	Free — no model call
2 · Judge	a small, cheap, swappable classifier model decides the ambiguous cases (`GUARDRAILJUDGEMODEL`, default a mini model)	Cheap

Fail-closed, both directions

If the judge is unreachable or unsure on a flagged item, the request is blocked, not allowed through — safety defaults to deny. It runs on both directions: a request on the way in, and a response on the way out.

Humane by policy, not just by block

The guardrail isn't only a wall. Its content policy is deliberate:

Self-harm routes to crisis resources and a human-first nudge — it does not just throw an error code.
Lived-experience testimony about abuse is not blocked from processing (people deserve to tell

their story) but is flagged sensitive, and self-publication is hard-gated until a human review confirms anonymisation and that publishing won't cause further harm.

Consensual adult content is allowed; coercion never is.

One engine, two homes

The same code (saas/guardrails.py + judge_client.py) guards the press's own generation pipeline and is the safety VAS inside the Buabantu API — reused, never rebuilt. That reuse is the point: a guardrail proven on a million words of fiction is the same one a Buabantu customer's traffic passes through.

← Back to the technology exposé · the safety layer of Buabantu.

Craft Library · Place Wiki · About the press · View this document on GitHub · Write with us

← Back to the library