How this system is itself governed
Where the models run, what may leave the bank, the rules every answer passes, and a tamper-evident log of everything anyone did.
On-premise console and gateway. No inbound internet access.
Stays in the bank
Raw logs, configurations, identities, customer records, the evidence store and the audit log.
Local models
gpt-oss-120b and qwen3-32b on the bank's own GPUs, served by vLLM behind Mesh.
Cloud models
Only questions about the frameworks themselves, enforced by Mesh data classification.
Answering with the local grounded engine: retrieval and templated prose over the same evidence, with zero network calls.
Each compliance task is pinned to a route. In a bank the local model is the default; the cloud chain is optional.
| Task | Local route |
|---|---|
| Readiness questions | gpt-oss-120b · vLLM |
| Evidence pack narratives | gpt-oss-120b · vLLM |
| Change impact | qwen3-32b · vLLM |
| Policy versus configuration | Rules comparator |
| Claim verification | Deterministic verifier |
Enforced in code, not in a policy document.
Rules set status
A deterministic rule over the evidence decides every control's status. Models only explain it.
Every claim cited
Each factual sentence ends with the control and evidence it rests on.
Verifier after every generation
Citations that do not resolve to evidence on that control are stripped; uncited claims are flagged.
No compliance conclusions
Sentences that declare compliance or predict an exam outcome are removed. The examiner concludes.
Refuse, don't guess
No matching evidence means "insufficient evidence", never an estimate.
10 golden questions, one with no answer in the evidence. Re-run on every model, prompt or route change.
Append-only. Each entry's hash covers the previous entry's hash, so any edit breaks the chain.
| # | When | Who | Action |
|---|
No entries yet
Nothing yet. Ask a question, draft a narrative or run a collection and it appears here.
Named sign-off
A reviewer approves every narrative before export; drafts with uncited claims cannot be approved.
Pinned routes, full log
Each task is pinned to a model and fallback chain in Mesh, and every call is logged.