Admingen glossary

Short definitions for model, generation, relationship and release terminology.

On this page

Interfaces and commands use the same terminology. Use this reference to distinguish similar operations.

Term	Meaning
Manifest	Application description in project.yaml: entities, fields, relationships and settings.
Normalized model	The model after validation and permitted defaults.
Plan	Operations the generator intends to perform.
Diff	Changes to current file contents.
Generate	Creating and applying source files from the model. Does not itself apply SQL to the database.
Generated	Files updated by the generator.
Custom	Your code, preserved through generation and used with standard foundations.
Lock	Internal file containing the contract and generated-file hashes.
Saved model	Exact model bytes from the last successful generation.
Module	Entity group for project structure and navigation, not an access role.
Persistent entity	Entity with its own data storage.
Projection	Read-only virtual entity selecting existing data without a new table.
FK: foreign key	Field referencing another table's key.
Relationship owner	Side defining physical storage and membership changes.
Inverse	Inverse view of an existing relationship.
Ledger	Applied migration log and expected file hashes.
Preset	Predefined environment component layout.
Release	Verified immutable image set and release metadata.
Digest	Image-content identity. Unlike a tag, identifies specific content.
Recovery point	Coordinated database/media backup for restoration.
Rollback	Return to recorded images from an earlier release. Does not automatically undo SQL changes.
Restore	Restore data from a complete recovery point.
DTO	API request/response object with explicitly defined consumer fields.

Adding a field and running Generate updates code; the database migration must still be applied. Editing article text in the admin changes data and needs no Generate. Distinguish model, source and database records to understand operation results.