Runtime

Overview

The Runtime is where intent becomes concrete execution. This page summarizes the local operator guide—it is not a production SLA.

Canonical source: docs/developer/runtime-operator-guide.md.

Concepts

• Local, deterministic Runtime configuration and execution
• Read-only use of historical evidence and golden fixtures
• Integration with cellas engine and conformance commands

Out of scope: hosted Runtime clusters, production monitoring, or credential management for external registries.

How it works

1. Pin inputs. Use fixture targets under conformance/fixtures/valid/ and explicit --seed values when running conformance tests.
2. Avoid network. Local adapter descriptors should set "network": "none" unless you are explicitly testing registry integration.
3. Separate evidence. Write run output to .conformance/runs/ or a temporary directory—never into samples/reference-execution-001/.
4. Treat golden data as read-only. Verify with cellas verify --type golden; do not approve or update golden projections from local runs.

Example

pnpm run build:workspace

pnpm exec cellas test \
  --target conformance/fixtures/valid/target.json \
  --json

pnpm exec cellas verify \
  --input conformance/golden/reference-execution-001/manifest.json \
  --type golden

Consumer First PASS (no monorepo):

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

CLI

pnpm exec cellas test --help
pnpm exec cellas verify --help
pnpm exec cellas engine --help

Related pages

• Architecture
• Engine
• Conformance
• Product: /product/runtime

Next steps

1. Quick Start
2. Examples
3. CLI