Conformance
Evidence, verification, and certification in CELLAS.
Overview
Conformance turns deterministic execution into inspectable proof—and certification is the result of that pipeline.
Deterministic execution → Evidence → CertificationConcepts
| Term | Meaning |
|---|---|
| verify | Read-only checks on artifacts, digests, golden manifests |
| test | Mandatory suites for a target |
| certify | Evaluate a target against a profile; emit certification level (e.g. PASS) |
| profile | Suite selection under conformance/profiles/ |
| evidence | Manifests/digests; historical trees are immutable |
Example
# Generated project happy path
pnpm exec cellas verify
pnpm exec cellas certify
# Monorepo / advanced
pnpm exec cellas verify --input <file.json> --type <type>
pnpm exec cellas certify \
--target conformance/fixtures/valid/stack-target.json \
--profile full-reference-stack-v1
pnpm exec cellas test \
--target conformance/fixtures/valid/target.json \
--jsonEvidence rules
- Historical evidence under
samples/reference-execution-001/is immutable - Local runs write to
.conformance/runs/or temporary directories - Digests must match; integrity failures surface as non-zero exits (see CLI output)
CLI
pnpm exec cellas verify --help
pnpm exec cellas certify --help
pnpm exec cellas test --helpRelated pages
- Architecture
- Tutorial
- CLI
- Glossary
- Product: /product/conformance
Canonical monorepo: docs/developer/conformance-cli-examples.md, packages/testing/*, conformance/.