Cephalon Glossary Starter
เนื้อหานี้ยังไม่ได้แปลเป็นภาษาไทย แสดงเป็นภาษาอังกฤษแทน
Use this glossary starter during Weeks 1-2 of the Learning roadmap.
The purpose is to normalize the vocabulary you use when reading docs, code, tests, and runtime routes.
Do not try to make this exhaustive on day one.
Start with the core terms below, then extend the glossary as you learn more.
Core terms
Section titled “Core terms”Engine
Section titled “Engine”Working definition:
The composition, runtime, manifest, policy, package-loading, trust, and introspection center of Cephalon.
Where to verify:
- Cephalon.Engine
src/Cephalon.Engine
Your notes:
Abstractions
Section titled “Abstractions”Working definition:
The host-agnostic public contract layer that modules, adapters, and companion packs build on.
Where to verify:
- Cephalon.Abstractions
src/Cephalon.Abstractions
Your notes:
Module
Section titled “Module”Working definition:
A deterministic unit of runtime composition that publishes services, capabilities, metadata, and optional lifecycle behavior.
Where to verify:
- Module authoring
src/Cephalon.Abstractions/Modules/IModule.cs
Your notes:
Capability
Section titled “Capability”Working definition:
A named runtime contract or permission-like unit that can be published, traced to a source module, and evaluated by policy.
Where to verify:
src/Cephalon.Abstractions/Capabilities/engine/capabilities
Your notes:
Blueprint
Section titled “Blueprint”Working definition:
The primary app-shape descriptor that defines the broad project form without trying to encode every pattern, transport, or deployment choice.
Examples:
modular-monolithmodular-vertical-slicemicroservicemicroservice-suite
Where to verify:
Your notes:
Pattern
Section titled “Pattern”Working definition:
A design or runtime behavior choice that can be composed on top of a blueprint rather than replacing the blueprint itself.
Examples:
cqrsoutboxstrategypipeline
Where to verify:
Your notes:
Transport
Section titled “Transport”Working definition:
A public or runtime communication surface such as REST, gRPC, GraphQL, SSE, WebSocket, or another adapter-facing protocol.
Where to verify:
- App models
/engine/manifest
Your notes:
Technology profile
Section titled “Technology profile”Working definition:
An additive workload or platform hint that influences runtime surfaces without exploding the blueprint catalog.
Examples:
agentic-workloadsserverless-hostinghybrid-cloud-runtime
Where to verify:
Your notes:
Runtime introspection
Section titled “Runtime introspection”Working definition:
The operator-facing runtime truth surfaced through routes such as
/engine/manifest,/engine/snapshot, and/engine/runtime-story.
Where to verify:
- Project memory
/engine/engine/snapshot
Your notes:
Companion pack
Section titled “Companion pack”Working definition:
An additive package that extends Cephalon with focused runtime, provider, transport, or operational behavior without bloating the engine core.
Examples:
Cephalon.Data.EntityFrameworkCephalon.Observability.OpenTelemetryCephalon.Behaviors.Http
Where to verify:
Your notes:
Host adapter
Section titled “Host adapter”Working definition:
A thin integration layer that hosts the engine in a runtime environment such as ASP.NET Core or Worker without redefining the engine contract.
Where to verify:
Your notes:
Runtime manifest
Section titled “Runtime manifest”Working definition:
The stable runtime description of what loaded and what the engine selected, including modules, capabilities, app profile, and packages.
Where to verify:
/engine/manifest/engine/snapshot
Your notes:
Runtime story
Section titled “Runtime story”Working definition:
The ordered operator-facing answer for what loaded, started, failed, and why.
Where to verify:
/engine/runtime-story/engine/snapshot
Your notes:
Database role
Section titled “Database role”Working definition:
A logical engine-owned database slot such as
write,read,outbox, orhistorythat resolves to an effective provider and physical target.
Where to verify:
- Database topology
/engine/database-roles
Your notes:
Database migration target
Section titled “Database migration target”Working definition:
The operator-facing migration unit tied to a logical role and current execution status.
Where to verify:
- Database topology
/engine/database-migrations
Your notes:
Read-model sync
Section titled “Read-model sync”Working definition:
The process that reconciles write-side state into a read-side projection, including projection lag, retry state, and durable job tracking where implemented.
Where to verify:
/api/v1/showcase/system/database-topology/api/v1/showcase/system/database-topology/brief/api/v1/showcase/system/database-topology/handoff(self-describing zip withREADME.md,handoff-manifest.json, brief, and raw projection)samples/Cephalon.Sample.Showcase/Infrastructure/ShowcaseReadModelSyncService.cs
Your notes:
Terms to add later
Section titled “Terms to add later”Add to this section as you move through the roadmap.
- trust policy
- package policy
- outbox
- inbox
- execution graph
- hosted execution
- diagnostics convention
- technology surface
- projection
- event-dispatch runtime
- audit history
- reference docs
- scaffolding
- template pack
Cross-check rule
Section titled “Cross-check rule”Before you treat a glossary definition as stable, verify it in at least one of these places:
- a hand-authored doc
- a runtime route
- a public contract in
Cephalon.Abstractions - a concrete engine or sample implementation
If those disagree, keep the term marked as provisional until you resolve the mismatch.