Formal Names
Reference: This page is a source-based technical synthesis of the LaTeX chapter cited below. For exact syntax, availability or ABI signatures, verify the versioned source, manifest and executable tests.
Scope and source boundary
Formal model identifiers are contracts for meaning and traceability, distinct from class, package or user-interface labels.
Names, identifiers, and runtime handles serve different purposes. The LaTeX guidance distinguishes human-readable and formal model names, semantic identity scoped by context, and handles used by execution or interop. Treating these as interchangeable makes evolution, serialization, and cross-context integration fragile.
Engineering rules
- Declare the owning context of a business identity.
- Do not infer permanent semantic identity from a memory address, UI label, or temporary handle.
- Document how formal names are projected into generated implementation names.
- Make identity stability and collision behavior explicit before distributed exchange.
Chapter outline (original LaTeX headings)
- Three Names, Three Responsibilities
- Bounded Context Prefixes
- Why Formal Names Use snake_case
- Relations and Verbs
- Stability Rules
LaTeX provenance
Primary chapter: Domain-Driven Design with logiCells/formal-identifiers-and-model-names.tex.