Glossary

A collection of terms and abbreviations used within the Framework M ecosystem.

Term	Definition
Adapter	A concrete implementation of a technical Protocol (e.g., SQLAlchemy for Database).
App	A domain-specific package containing DocTypes, Controllers, and business logic.
Controller	A Python class where DocType-specific business logic and lifecycle hooks live.
Desk	The generic web-based administrative UI for managing metadata and data.
DocType (Document Type)	A metadata-driven definition for a business entity (e.g., Invoice, Item).
Entrypoint	A Python discovery mechanism used to load plugins and adapters dynamically.
Macroservice	A domain-scoped service extracted from a monolith but sharing some runtime components.
MetaRegistry	The central system-wide registry where all DocTypes and metadata are stored.
Port / Protocol	A typed Python interface (contract) defining a specific system capability (e.g., Cache).
Repository	A standardized interface for performing CRUD operations on DocTypes.
Studio	The developer CLI and UI used for scaffolding apps and managing metadata.
Unit of Work (UoW)	A pattern that maintains list of objects affected by a single business transaction.
Zero-Cliff Architecture	The design philosophy that avoids "cliffs" where a full rewrite is required for scale.