Requirement and workflow ownership boundary for this API group.
Scope and purpose of this API group.
This comes before name so the group is named from the user-facing API
surface it owns, instead of backfilling a description after a technical
name has already been chosen.
Group name derived from the described API surface.
Prefer PascalCase names that remain consistent with database namespaces, schema file names, or table prefix patterns when those are a natural fit.
Final rationale for the API group scope.
Review of the group boundary and nearby endpoint-surface risks.
Initial reasoning about why this API group should exist.
Logical grouping of API endpoints based on Prisma schema structure.
Groups divide large API specifications into manageable generation cycles, maintaining alignment between API structure and database schema.
Author
Samchon