Skip to content

MOD-CRM-ENTEntities

Markdown

MOD-CRM-ENT

Entities

Markdown
  • DocumentApproved

KindModule charterProduct areaCRMModuleEntitiesRevision2Approved byAndrewApproved at2026-10-22

Read atservices-crm a8d1364freact-console baf6dae3

Owns
Contacts (crm.contacts) and their e-mail addresses, phone numbers, addresses, communication preferences and custom field valuesOrganizations (crm.organizations) and their addresses, phone numbers and custom field valuesContact organization affiliations and the roles held on themContact roles, affiliation types and their default contact-information linksContact types, organization types (with their compliance rules and notice), address types and phone number typesOrganization contact role compliance: violations, reprocess runs and the noticeRecord locks and their audit, protected system recordsRecord revisions of contacts and organizationsCRM settings: default page layouts and forms, the default affiliation type, the date-reconciliation watermarkManaged file records of contact photos and organization logos

Repositories Read

Does Not Own

RecordOwner
Duplicate rules, duplicate candidates and mergesMOD-CRM-DQ (Data Quality, not yet registered)
Activities and tasksMOD-CRM-ACT (Activities and Tasks, not yet registered)
Regions and automatic region assignmentMOD-CRM-REG (Regions, not yet registered)
Bulk data jobs, imports and the job reconcilerMOD-CRM-DJ (Data Jobs, not yet registered)
Tenant provisioning, seeds and purgeMOD-CRM-TL (Tenant Lifecycle, not yet registered)
Custom field definitions, page layout and form definitionsPlatform (metadata)
Roles, policies, permission evaluation and application accessPlatform (security)
Record stamps, user display names, Quick Search and dataset queriesPlatform
E-mail templates, communication requests and sendingPlatform (communications)
File storage and the asset pipelinePlatform (files)

Decision History

Product decisions recorded in this module's findings that bear on this module, as recorded.

  1. OQ-CRM-ENT-001DecisionAndrew2026-10-22

    A: require complete payloads for whole-record saves of contacts, organizations and classification records, as Activities already do (reads state empty properties as null; an omitted property is refused; null clears). Affiliation and custom-field exceptions stay.

    Applied to: Structured decision update record

  2. OQ-CRM-ENT-002DecisionAndrew2026-10-22

    B: everything stays in Entities; no Configuration Types module. Entities owns contact, organization, address and phone number types, affiliation types and the contact-role catalogue and their rules.

    Applied to: Structured decision update record

  3. OQ-CRM-ENT-003DecisionAndrew2026-10-22

    B: a rule's product intent is derived from its origin: an origin that names a product decision (a milestone decision id or an answered open question) makes the rule confirmed; otherwise the rule inherits its capability's intent. No rule-level field.

    Applied to: Structured decision update record

  4. OQ-CRM-ENT-004DecisionAndrew2026-10-22

    A: the corrected console scope in the MOD-CRM-ENT registry row stands for the next delta pass. Resolved.

    Applied to: Structured decision update record

The Markdown files under specs/ in rhythmsoftware/rhythm-v2-docs are the canonical source of truth. This reader is a generated, read-only projection of them.