# kinds/entity.md — one entity (a table), after the fact The playbook `/ba-change` loads for `kind: entity`. The frame is in `SKILL.md`; this file carries what is specific to a **new entity** — the biggest change a finished module can take: a table, its screens, its pagespecs, its seed. Owner document: `//entité.md` (full re-Write, every other block verbatim). Grammar: `_workflow/doc-templates.md` § entité.md; `ba-create-data-model` Step 0 (trace audit) → Step 1 (the block); `levels/attributes.md`, `levels/relationships.md`. Code: `allocation.next` — `ENT-NNN`, module-wide (cited by `screen.md` `**Entité** : X (ENT-NNN)`). ## 1. Analyse the request One grouped AskUserQuestion: | Question | Why it matters | |---|---| | **What** is it — the business concept, its PascalCase name, one sentence? Is it an aggregate root, a component of another aggregate, a reference table (lookup)? | classification decides prefix, display field, seed tier | | **Who upstream asks for it** — which use case / rule names it? | verbatim trace (BLOCKED otherwise — DM-011) | | **Its key attributes** — identity, label, amounts / dates / statuses, the FKs to other entities (which module, which onDelete)? | Relations drag lookup grants; a status drags the state chain | | **Where does it live** — a satellite of an existing section (shown as a tab on its parent's detail + its own list/form) or a NEW menu section? | a new section is `/ba-create-menu`'s job, out of this change | Also settle: is it a **person** (→ `Personne` link to `auth_Users`, CODE-007)? Does it carry a **business code** (→ `**Code pattern**`, the socle allocates)? Which attribute **names a row** (`**Affichage**`)? ## 2. Challenge it - **Who upstream asks for it?** `report.trace` — no hit = BLOCKED; write the use case or the rule first. - **Is it already there?** `existing.exact` (same name) → nothing to add; `existing.similar` (`Prospect` vs `ProspectContact`) → the same aggregate? - **Is it a Core entity?** `User`, `Tenant`, `TenantOrganisation`, `Department`, `Office`, … are the platform's — the CLI BLOCKS (`core-entity-collision`): reference them through a `scope core` relation. A **reserved name** (`Notification`, `Ticket`, `Workflow`, `AuditLog`, …) is blocked too, with what to use instead. - **Is it a platform capability?** A document / attachment / search index / counter table is a service, not an entity (DM-019 / CODE-006) — the CLI warns; the playbook steers to the capability. - **Is it an entity or an attribute?** « La catégorie de l'opportunité » with three fixed values is an enum attribute; with a managed list it is a reference table (lookup) — then its label is its identity, no code unless the user decides it (DM-022). - **Is it a satellite or a section?** A satellite lives under an existing section (tab on the parent's 360 view + its own list/detail/form with `routeFamily` / `routeParent`); a first-class business object nobody parents is a new section — `/ba-create-menu`, then `/ba-loop` on the module, not this change. - **Who reads it?** The section's actors need rows at the section grain (`/ba-change` kind=permission) — and its FK producers become lookups (derived by the mandatory post-step). ## 3. Author The full block (doc-templates § entité.md): ```markdown ### — (agrégat racine | composant | référentiel) - **Préfixe table** : `_` - **Portée** : strict — données isolées par tenant - **Traçabilité** : UC-…, BR-… - **Sources** : SRC-NNN §n (when the registry exists) | Attribut | Type | Contraintes | Calculé | |----------|------|-------------|---------| | Id | Guid | PK | — | | … | … | … | … | - **Relations** : *→1 — FK Id, scope same-module, onDelete restrict. - **Index** : (), (Status). - **Affichage** :