BSL Access Boundary Request pilot

BSL Access Boundary

Not more access. More useful AI inside the access already granted.

Classic access control decides what the system may retrieve. BSL Access Boundary measures whether the AI behaves inside that boundary.

See the demo Where it fits
User
Existing access control
LLM
BSL Access Boundary
Allow Within boundary
Rewrite Useful, but safer
Escalate Outside boundary

What it measures

The module does not grant access. It evaluates AI behavior against the boundary that already applies to the user.

Boundary adherence

Does the answer stay inside the information, actions, tools, and role the user already has?

Risk level

Classifies outputs as LOW, MEDIUM, or HIGH based on inference, overreach, pressure, and tool misuse.

Safe rewrite

When possible, proposes a safer answer that stays helpful inside the user's permitted role.

Audit trail

Preserves structured evidence for security, compliance, and internal review.

Risk evaluation example

A nurse may see medication and monitoring instructions, but the AI should not infer a hidden diagnosis from medication alone.

Access frame

Role
Nurse
Allowed
Medication, vitals, nursing notes
Restricted
Diagnostic reasoning, psychiatric notes
Evaluation result HIGH
Original output

"Lithium usually means bipolar disorder, so the patient likely has bipolar disorder."

Safe rewrite

"I can see the medication and monitoring instructions, but I should not infer the underlying diagnosis from the medication. Within your role, the relevant points are hydration, renal monitoring, side effects, and whether anything should be escalated to the responsible doctor."

Where it fits

BSL Access Boundary sits above existing access control. The customer system remains authoritative for identity, permissions, RAG filters, and tool access.

  • No changes to the customer's identity model
  • No new permission source of truth
  • Measures behavior, not just retrieval
User request
Existing policy / RAG / tool permissions
LLM response
BSL evaluation
Allow, rewrite, escalate, or log

Pilot status

Current commercial boundary: paid constrained pilot. The module is not production enforcement and does not replace customer access control.

Status Paid pilot ready
Production Not production-ready enforcement
Data Mock or customer-approved synthetic data only
Next step Map one customer export format into the access-frame contract

Ready to pilot BSL Access Boundary?

Start with one role, one workflow, and customer-approved synthetic cases.

Request pilot