Resources
Documentation
The Kenshiki Labs documentation index organizes the technical RFCs, founding research papers, and architecture specifications into three guided reading tracks: why this category exists (civilizational thesis, authority outside the model, distributed Enron moment), how the runtime contract works (governed intelligence architecture, bounded synthesis, SIRE identity, prompt governance, deterministic admissibility, Claim Ledger, evidence contracts, ARBV), and what fails without it (link margin, scaling fallacies, the failure-pattern record). Linked to the AI Incident Archive for the empirical case.
Track 01
Why this exists
Start with the thesis. These papers explain why authority has to move outside the model, why scale does not rescue reliability, and why the market window is already open.
Jump to track →Track 02
How it works
Then read the runtime contract. This path moves from system shape to ingestion, prompt compilation, admissibility, claim checking, and the APIs that expose the stack.
Jump to track →Track 03
What fails without it
Finish with the failure patterns. These are the documents that make the cost of unsupported authority impossible to shrug off as a product-paper problem.
Jump to track →Track 01
Why this exists
Start with the thesis. These papers explain why authority has to move outside the model, why scale does not rescue reliability, and why the market window is already open.
A Civilization-Scale Thought Experiment
The civilizational dynamics that make governed architecture necessary.
Why the lag between AI deployment and institutional response is not a policy failure but a structural property of the system — and why the populations that absorb that interval are not chosen randomly.
Simulators, Sensors, and Governed Architecture
The high-level argument for governed architecture.
The origin paper: how physics forced ontology, ontology forced authority, authority forced gates, and gates forced architecture — discovered empirically, not designed from first principles.
Authority Must Be Outside the Model
Why the model cannot be its own certifier.
Why safety enforcement visible to the model's optimization surface inevitably becomes performance theater — and why the architectural invariant is structural invisibility, not better prompting.
Why Runtime Governance, Why Now
Why runtime governance is a current need, not a future one.
A frontier model's own analysis demonstrates why training-time alignment is insufficient: its "contrarian" view was consensus opinion shaped by corpus bias, correctable only through external verification.
Track 02
How it works
Then read the runtime contract. This path moves from system shape to ingestion, prompt compilation, admissibility, claim checking, and the APIs that expose the stack.
Governed Intelligence Architecture
The canonical runtime contract for the whole system.
The unified architecture specification that integrates SIRE identity, air-gapped ingestion, CFPO prompt compilation, Tri-Pass inference, and the Claim Ledger into one deterministic, auditable pipeline.
Governed Intelligence API
How the contract shows up in the API surface.
How to integrate with the Kenshiki Labs API: verified vs fallback responses, tenant isolation, REBAC authorization, attestation, streaming, and error handling.
The Ingestion Pipeline
How raw sources become governed evidence.
How raw documents become governed evidence: air-gapped parsing, deterministic chunking, streaming embeddings, and geometric boundary calculation — the Phase 0 that feeds Kura.
The SIRE Identity System
How SIRE defines what a source is and where it can speak.
The deterministic tagging methodology that controls what evidence enters the retrieval boundary. SIRE defines the identity of every source document in Kura — not by what the model thinks, but by what the evidence actually is.
Prompt Governance
How Compiler turns a loose prompt into a governed query.
The specification that defines how Kenshiki Labs compiles prompts: CFPO ordering, evidence-to-zone mapping, compiler invariants, and the enforcement contract between the Prompt Compiler and the Claim Ledger.
The HAIC Framework
The HAIC architecture behind generate, decompose, verify.
The original architecture design that proposed externalizing the truth boundary, multi-pass causal verification, and cryptographic claim attribution — the intellectual foundation of the Kenshiki Labs platform.
Deterministic Admissibility Gating
How obligations and evidence sufficiency are enforced before emission.
The admissibility engine that resolves regulatory obligations to human-approved document versions, enforces transactional supersession, and fails closed with actionable remediation — the gate that runs before retrieval begins.
How Kenshiki Labs Reads the Model
How Claim Ledger reads what the model actually relied on.
Inference-time observability: the signals Kenshiki Labs uses to inspect token confidence, entailment, stability, and causal attribution before unsupported output reaches operations.
Evidence Contracts
The signed authorization primitive that makes governance non-repudiable.
The missing primitive between runtime governance telemetry and institutional accountability — typed, signed, chainable authorization records that prove what was authorized, not merely what was logged.
ARBV
How governance boundaries are specified, attacked, measured, signed, and replayed.
How Kenshiki Labs turns AI governance from policy assertion into continuously tested, cryptographically verifiable boundary enforcement through formal invariants, semantic fuzzing, Boundary Evidence Records, and auditor replay.
Track 03
What fails without it
Finish with the failure patterns. These are the documents that make the cost of unsupported authority impossible to shrug off as a product-paper problem.
The Distributed Enron Moment
The empirical case that the incidents are already here.
Why AI governance is on time, not early — 21+ verified incidents, active enforcement from state AGs and federal agencies, and a regulatory trajectory that mirrors pre-SOX accounting reform.
Link Margin: Why Scale Won't Save You
Why more parameters do not close the authority gap.
The dominant failure mode is not hallucination but unresolved ambiguity. Models lack authoritative variant spaces, resolution rules, and consequence thresholds at inference time.
See the empirical failure record
The archive turns the abstract risk argument into sourced incidents across healthcare, finance, government, legal, and consumer harm. It is the fastest way to test whether the architecture is solving a real problem.
Next Step
Use the documents to pick your next layer of detail.
If you understand the thesis and want to inspect the runtime contract, go to architecture. If you want to see how the system is packaged and bought, go to pricing. If you already know the fit, start in Workshop.