Skip to content
CELLAS

Product

Runtime

The deterministic execution environment where CELLAS turns declared intent into concrete runs.

Read the docsQuick Start

What it is

Runtime binds configuration, adapters, and execution context so the same inputs produce the same observable results. It is the environment operators and engines share when running Intent Computing workloads locally.

Why it exists

Documentation and knowledge systems need reproducible execution—not ad-hoc scripts that drift between machines. Runtime encodes that contract: pinned inputs, explicit network posture, and separated evidence paths.

When to use it

  • Local development against conformance fixtures
  • Operator workflows that must not mutate historical evidence
  • Integrating Engine runs with verify / certify

How it works

Runtime configuration is mutable per Execution and lives alongside profiles and agent runtime docs in the monorepo. Local adapters should prefer network: none unless you are deliberately testing registry integration. Run outputs write to .conformance/runs/ (or a temp directory)—never into samples/reference-execution-001/.

How to start

pnpm create cellas my-docs --yes
cd my-docs
pnpm exec cellas verify
pnpm exec cellas certify

Relationship to other components

  • Engine executes workflows inside Runtime constraints
  • CLI exposes Runtime-adjacent test / verify / certify commands
  • Conformance consumes Runtime/Engine artifacts as evidence

Related

Next steps