The independent examination describes the scoped product at its pinned revisions. Its remaining concerns include replacement semantics, deployment switches, proof that exercises service fallbacks instead of the intended screen, and behavior owned by neighboring modules. Recorded findings separate these concerns from established behavior.
The examination checks source references, product decisions and existing automated-test bindings. It does not execute the CRM or console product suites. Observed code does not become product approval. The original technical catalog and examination notes remain in structured evidence.
The current planning layer groups four broad concepts across seven features, nineteen capabilities and five journeys. Superseded concepts retain their identities for traceability. Detailed facets replace the earlier table-by-table concept list.
The original examination's run details remain in frontmatter. Current corpus validation is performed by the authoring job that changes these artifacts.
Decision History
Product decisions recorded in this module's findings that bear on this module, as recorded.
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.
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.
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.