Skip to content
CephalonEngine

Cephalon Component Docs

This catalog maps the current solution into hand-authored component-level documentation.

These pages explain what each shipped package owns and how it fits into Cephalon. Generated API reference output stays separate under docs/reference/.

See also: Docs hub

Maturity at a glance

Section titled “Maturity at a glance”

Each shipped package carries a maturity label (M0 through M4) and an ownership mode (taxonomy-only / application-managed / cephalon-managed / provider-managed). Read the labels before assuming a package is runtime-ready.

When a component-page maturity label and the maturity audit disagree, the audit is the authoritative truth. When in doubt, follow the cross-reference into the conformance matrix.

Reading the per-package banner

Section titled “Reading the per-package banner”

Every component page below carries a one-line maturity banner directly under its H1 heading. The banner format is:

> **Maturity:** `Mx` · **Ownership:** <ownership-mode> · **Family:** `<family>` · See [audit](../engine-surface-maturity-audit.md), [matrix](../conformance-matrix.md).

What each field means:

  • Maturity — the package’s current target on the M0-M4 scale. M0 taxonomy-only; M1 catalog/runtime-truth; M2 narrow managed execution; M3 broader managed execution; M4 adoption-ready.
  • Ownership — who actually executes the work: taxonomy-only (no behavior claim), application-managed (consumer code or another runtime), cephalon-managed (the engine itself), or provider-managed (a specific provider companion pack). A package may declare a mixed ownership when one part is engine-owned and another is consumer-owned; in that case the banner spells out the split.
  • Family — one of the 12 shipping families (core-runtime, host-adapter, transport-adapter, behaviors, eventing, agentics, data-and-cdc, event-sourcing, multi-tenancy, audit-and-identity, edge, observability, scaffolding-and-tooling).

The banner is a read-only consolidation of the audit + matrix. When promoting a package’s maturity or splitting its ownership label, update the audit + matrix in the same slice; the per-component banner is regenerated against those sources rather than edited in isolation.

Core runtime

Section titled “Core runtime”

Technology and follow-through packs

Section titled “Technology and follow-through packs”

Phase 9 companion packs

Section titled “Phase 9 companion packs”

Phase 10 companion packs

Section titled “Phase 10 companion packs”

Sprint 31 companion packs

Section titled “Sprint 31 companion packs”

Phase 12 companion packs

Section titled “Phase 12 companion packs”

Phase 8 companion packs

Section titled “Phase 8 companion packs”

Tooling and adoption

Section titled “Tooling and adoption”

Additional repo surfaces

Section titled “Additional repo surfaces”
Section titled “Related docs”