Skip to content
KUJO05 / The Kujo system5 / 18

Build with clarity. Operate with control.

The language is the long-term foundation. Existing tools offer an earlier route into engineering workflows.

  1. 01

    Clarity

    Kujo language / Spec / Eval: explicit intent and testable outcomes.

  2. 02

    Context

    MCP / CaseFile / RunLedger: useful inputs, debugging evidence and run records.

  3. 03

    Control

    Dispatch / Workcell / ShipCheck: orchestration, bounded execution and release checks.

Existing repositories + coding agents explicit component contracts Kujo runtime + CLI
Inspect the execution boundary

Workcell owns supported container bounds. Dispatch owns workflow state. Neither confers enterprise certification.

Inspect the evidence boundary

CaseFile captures commands. Eval runs configured checks. RunLedger stores supplied outcomes. Artifacts remain separate.

KUJO / Investor briefingT01–T14 · tool boundaries remain distinct5

← → Navigate · Space Next · Home / End · F Fullscreen