Architecture
How Runtime, Engine, CLI, plugins, and Conformance fit together in CELLAS.
Overview
CELLAS implements Intent Computing for documentation systems. Intent is declared, execution is deterministic, and results become evidence that can be certified.
Intent → Runtime + Engine (+ Plugins) → Evidence → Conformance (verify / certify)Concepts
| Piece | Role |
|---|---|
| Runtime | Deterministic environment and configuration for execution |
| Engine | Runs workflows and emits candidate artifacts |
| Plugins | Optional capabilities under the same contracts |
CLI (cellas) | Operator interface for test / verify / certify / engine |
| Conformance | Profiles, fixtures, digests, certification |
Frozen specifications in the monorepo remain the wire-level authority. This site explains the operator view.
Example
A new project never needs the full architecture to succeed—First PASS exercises the conformance edge:
pnpm create cellas my-docs --yes
cd my-docs
pnpm exec cellas verify
pnpm exec cellas certifyDeeper Engine work uses candidate directories under .reference-engine/runs/ and never mutates samples/reference-execution-001/.
CLI
pnpm exec cellas --help
pnpm exec cellas engine --help
pnpm exec cellas certify --helpRelated pages
- Runtime
- Engine
- Plugin SDK
- Conformance
- Reference map
- Product hub: /product