Entities
Purpose
Entities gives staff a shared record of the people and organizations known to their workspace. Its planning tree groups record maintenance, contact details, relationships, compliance, classification and record protection. Capabilities hold the rules; journeys connect those capabilities into staff work. Features share broad concepts through related concept references, while each concept has one owning feature.
Boundary
Entities owns the records listed in the charter. Neighboring CRM modules own duplicate decisions, merges, activities, regions, data jobs and workspace lifecycle. Platform supplies security, metadata definitions, query execution, communication delivery and file storage. Entities records the integration points without specifying those owners’ internal behavior. Entities owns its classification catalogues; the runtime function boundary belongs to Design.
Features
Capabilities
Journeys
| Id | Title | Product intent | E2E policy |
|---|
JNY-CRM-ENT-001 | Create a member record and inspect the saved information | proposed | required |
JNY-CRM-ENT-002 | Record an employer change while retaining the previous affiliation | proposed | required |
JNY-CRM-ENT-003 | Archive a closed organization and inspect its retained history | proposed | required |
JNY-CRM-ENT-004 | Configure an affiliation type and use it on a contact | proposed | required |
JNY-CRM-ENT-005 | Find current affiliates across an organization hierarchy | proposed | optional |
Testing Tree
The feature suites describe cumulative outcomes across their capabilities. Detailed capability proof belongs in design, and the implementation register identifies the existing executable files and their asserted bindings. The register records source inspection with execution and conformance still unverified. The continuation examination restores three feature bindings, including a partial unchanged-save contribution, and records the outstanding tooling and proof gaps.
| Layer | Directory | Artifacts |
|---|
| Planning | planning/acceptance/ | FAS-CRM-ENT-01, FAS-CRM-ENT-02, FAS-CRM-ENT-03, FAS-CRM-ENT-04, FAS-CRM-ENT-05, FAS-CRM-ENT-06, FAS-CRM-ENT-07 |
| Design | design/tests/ | ATS-CRM-ENT-001, ATS-CRM-ENT-002, ATS-CRM-ENT-003, ATS-CRM-ENT-004, ATS-CRM-ENT-005, ATS-CRM-ENT-006, ATS-CRM-ENT-007, ATS-CRM-ENT-008, ATS-CRM-ENT-009, ATS-CRM-ENT-010, ATS-CRM-ENT-011, ATS-CRM-ENT-012, ATS-CRM-ENT-013, ATS-CRM-ENT-014, ATS-CRM-ENT-015, ATS-CRM-ENT-016, ATS-CRM-ENT-017, ATS-CRM-ENT-018, ATS-CRM-ENT-019 |
| Implementation | implementation/tests/ | Executable suites listed in the charter’s structured testing tree |