CEG authoring

Editable CEG Source becomes a Kar sidecar through the authoring entry:

import {
  createCegSource,
  lintCegSource,
  compileCegSource,
  diffCegGraphs,
  validateCegSource,
} from '@knolo/core/kar/authoring';

@knolo/core and @knolo/core/kar do not load this module. @knolo/core/experimental/kar/authoring remains available for this cycle and is the module the stable entry re-exports. compileCegSource({ source, image }) returns the sidecar. The same source, image, and compiler version produce the same sidecar bytes. The compiler does not call a model, a clock, or the network.

knolo kar graph lint knowledge.ceg.yaml
knolo kar graph build --image knowledge.knolo --source knowledge.ceg.yaml --out knowledge.kar.json
knolo kar graph check --image knowledge.knolo --graph knowledge.kar.json

Domain Packs can propose CEG Source for contracts, policy, and operations. Their maturity in domains/v6-catalog.json is review-required. A proposal is not a committed graph until someone compiles the reviewed source. A later human-validation pass can mark a pack validated without a new KAR version. That pass has not happened for the bundled packs.

Rust, Python, and ICP do not compile CEG Source. Authoring stays on the TypeScript package.

The repository guides for producers, manual authoring, and the source schema are under docs/kar/ in Knolo Core. This page does not restate the schema. If you change byte rules, the change belongs in the spec and the conformance fixtures, not only in an application.