Start governed synthesis without private infrastructure
Workshop
Shared Kadai or BYOK. Governed outputs. Workshop is the hosted entry tier — same Claim Ledger contract, no infrastructure required.
Workshop is the hosted entry tier for governed AI — the deployment customers reach for when they need a board-ready governed AI response within a quarter and cannot wait on infrastructure. Shared Kadai inference or bring-your-own-key configurations. The same Claim Ledger contract that runs in Refinery and Clean Room runs in Workshop; what changes is where the boundary lives. Workshop is also the evaluation surface for control design before promoting workloads to Refinery or Clean Room.
Without this: the model answers directly, and the burden of deciding whether it's usable falls on whoever reads it. You discover problems after someone relies on them.
Today
Your team calls a model directly. It returns fluent text. Someone reads it, decides it sounds right, and passes it along. When that output is questioned — in a review, an audit, a legal proceeding — no one can show what it was based on.
With Workshop
The same model can still generate the language — shared Kadai or a connected API — but now inside a governed loop. The prompt is compiled, evidence is retrieved, claims are checked, and the response gets an explicit state before it reaches anyone.
How Workshop works
A user question enters the Kenshiki Labs pipeline before the generation layer sees it. The prompt is compiled, evidence is retrieved, and bounded context is sent through Workshop's shared generation lane: Kenshiki Labs-hosted Kadai or a connected model API. The response comes back as a proposal, is decomposed into claims, checked against evidence, and assigned a state before it reaches anyone.
Output states
What Workshop is
The full Kenshiki Labs bounded-synthesis pipeline on shared infrastructure. Compiler, retrieval, Claim Ledger, and output-state assignment all run inside Kenshiki Labs. Generation can happen through Kenshiki Labs-hosted Kadai or an approved model API, both receiving only the constrained context Kenshiki Labs provides.
- Use shared Kadai or a BYOK/public endpoint as the generation layer
- The full governance pipeline runs in front of and behind that model
- Answers are evaluated before they reach a user
The Kenshiki Labs contract
Two APIs. One contract.
Put evidence into Kura. Ask Kadai for answers bounded by it. In Workshop, the generation layer can be shared Kadai or a connected model API — but the contract is the same. SIRE scopes what evidence is admissible. The generation model acts as a renderer inside the governance pipeline, not as the authority.
- Kura defines the evidence boundary
- SIRE scopes evidence admissibility per query identity
- Kadai returns answers bounded by that evidence
- The generation model renders — it does not decide
Who this is for
The Team Shipping AI Into Real Work
already using public model APIs, or wanting a shared Kadai starting point, but unable to justify what those systems produce under review, audit, or challenge.
The Decision-Maker
receives an answer only after Kenshiki Labs has checked what supports it, what is missing, and whether it is allowed to leave the system.
Go deeper
API Developer Guide
Full API reference — endpoints, request/response schemas, streaming, error handling, attestation verification.
See Workshop in action
Ask a question and watch the governance pipeline return a response with claims checked, gaps surfaced, and states assigned.
AI Incident Archive
Real cases where public models produced fluent, confident answers that turned out to be wrong.
Claim Ledger
The verification engine inside every Kenshiki Labs response. Breaks answers into claims and records what held up.
Platform Architecture
How the full Kenshiki Labs pipeline is structured — Kura, Kadai, Compiler, Ledger, and Boundary Gate.
Integrations
How Kenshiki Labs plugs into AI factories, enterprise SSO, evidence systems, and GRC workflows.
Pricing
Workshop starts under $100/month. Usage-based pricing for Kura and Kadai, with BYOK/public-model support.