RIC legality demo
Deterministic legality gate in front of any text model.
The model proposes an answer. RIC applies hard rules and either lets it emit or halts it — with a replayable proof bundle for what happened. Same input, same candidate answer, same legality decision across machines.
1. What the user sees
In the UI you type a policy question, config change, or safety instruction. The downstream text model proposes an answer; RIC sits in front of it and decides whether that answer is allowed to emit.
- • You write a question and hit send.
- • The model produces a draft answer (its normal stochastic behavior).
- • RIC evaluates that draft against your rules, then returns:PASS with hashes and run ID, or HALT with a deterministic explanation.
2. What RIC does under the hood
The legality demo runs on the same deterministic substrate as the rest of RIC:
- • The app sends the model's candidate answer to RIC via
POST /run. - • RIC parses and normalizes the text, runs contradiction checks, constraint rules, and temporal/structural guards.
- • If it passes, RIC emits the answer with a proof bundle; if not, it halts and no model output is allowed through.
Q32 fixed-point numerics, no clocks, no randomness. Same request + same candidate answer → same legality decision and bundle, across machines and environments.
3. Why this matters
- • Auditability: Every decision is stored as a bundle with steps, legality reasons, and hashes. You can replay it and get the same result.
- • Tamper-evidence: Any change to the reasoning steps changes the hashes.
- • Safety & compliance: Encode rules that must never be violated (coverage windows, timing, policy constraints, safety limits).
- • Infra & robotics: Guardrail config updates, ETL outputs, and control instructions before they reach production systems or devices.
4. Integration sketch
Wiring pattern is simple:
- Your app calls your text model as usual.
- Instead of returning that answer directly, your backend wraps it in a RIC
/runcall with your legality/safety rules. - RIC returns either a legal answer + proof bundle or a halt signal with a deterministic explanation.
Small-footprint HTTP integration works with FastAPI, Express, Go, Rust, Terraform/Kubernetes gates, and edge or on-prem environments.