Rhythm CRM Architecture

What This Record Is

RHYTHM-CRM-ARCH-001 is the definitive architecture and completion plan for Rhythm 2.0 CRM (customer relationship management: contacts, organizations, affiliations, duplicates and merging, record lifecycle, console and data operations) and the standard against which CRM work is judged, with a gap matrix and milestones CRM-M9 to M23. Proposed 2026-10-19 for Andrew's review; eleven decisions CRM-Q1 to Q11 await him and the document itself builds nothing.

(Summary from the Rhythm 2.0 Architecture Library card; the parts below are the proposal's own text, converted verbatim.)

Parts

1. RHYTHM-CRM-ARCH-001: Rhythm 2.0 CRM — Definitive Architecture and Completion Plan: Status: proposed 2026-10-19 for Andrew's review; documentation only, nothing built by this work. Branch crm-architecture
2. 01. Product Vision, Architectural Principles and Research Method: Part of RHYTHM-CRM-ARCH-001.
3. 02. Rhythm 1.0 (Rolodex) and the Support History: Part of RHYTHM-CRM-ARCH-001. Evidence: e01,
4. 03. Rhythm 2.0 CRM Today: Assessment by Functional Area: Part of RHYTHM-CRM-ARCH-001. Evidence: e03 (services-crm
5. 04. Domain and Relational Data Model: Part of RHYTHM-CRM-ARCH-001. Evidence: e03 §2–§12. Paths are
6. 05. Functional Architecture: What Every CRM Capability Does: Part of RHYTHM-CRM-ARCH-001. This chapter specifies target behaviour. Each section ends with a short
7. 06. API and Service Architecture: Part of RHYTHM-CRM-ARCH-001. Evidence: e03 §2, §14–§16;
8. 07. Duplicate Detection and Record Merging: Part of RHYTHM-CRM-ARCH-001. The binding sub-architecture is services-crm:docs/merging/ (approved
9. 08. Record Lifecycle and Safe Delete: Part of RHYTHM-CRM-ARCH-001. The binding sub-specification is the record lifecycle design,
10. 09. Console Experience: Search, Explorer, Queries and the 360 Pages: Part of RHYTHM-CRM-ARCH-001. Evidence: e04 (with addendum A–D),
11. 10. Data Operations: Imports, Upserts, Exports, Bulk Changes and Rollback: Part of RHYTHM-CRM-ARCH-001. Evidence: e03 §13,
12. 11. Security, Audit and Operational Contracts: Part of RHYTHM-CRM-ARCH-001. Evidence: e03 §14–§15,
13. 12. Cross-Application Integration Contracts: Part of RHYTHM-CRM-ARCH-001. Evidence: e05 Part B (the full
14. 13. Decisions: Standing, Recorded, and Needing Andrew (Deliverable D): Part of RHYTHM-CRM-ARCH-001.
15. 14. Implementation Gap Matrix (Deliverable B): Part of RHYTHM-CRM-ARCH-001. Every significant capability, its target, its evidence, and what remains.
16. 15. Milestone Plan (Completion Roadmap, Deliverable C): Part of RHYTHM-CRM-ARCH-001. Gap rows are in 14; tests and the acceptance method in
17. 16. Testing and Acceptance Strategy: Part of RHYTHM-CRM-ARCH-001.
18. 17. Risks, Unresolved Items and Verification Limits: Part of RHYTHM-CRM-ARCH-001.
19. 18. Traceability Appendix: Part of RHYTHM-CRM-ARCH-001.
20. e01 — Rhythm 1.0 Rolodex: records and relationships (evidence): Research for the Rhythm 2.0 CRM architecture. What the Rhythm 1.0 CRM ("Rolodex") lets users do with contacts, organizations
21. E02. Rhythm 1.0 Rolodex: activities, engagement, tasks, duplicates and merging, search, data operations: Evidence for the Rhythm 2.0 CRM architecture. It records what the 1.0 product lets people do in five areas, with the rules
22. E03 — Rhythm 2.0 CRM Backend Assessment (services-crm): Evidence for the CRM architecture and gap analysis. Written 2026-10-19 from a read of the code only. Nothing was run except
23. e04 — CRM console assessment (react-console): Written 2026-10-19 (about 16:50 ET) for the CRM architecture gap analysis.
24. E05. Platform capabilities CRM depends on, and every other application's references to CRM records: Evidence for the CRM architecture. Read-only investigation, 2026-10-19 (ET). Nothing was changed in any repository.
25. E06 — Customer pain with Rhythm 1.0 CRM (Rolodex): Jira, Zendesk, HubSpot, Linear, GitHub: Gathered 2026-10-19, 16:37–16:42 ET, read-only. No ticket or issue was created, edited, commented on or transitioned.
26. Review R1: Rhythm 2.0 capabilities the CRM architecture overlooks or understates: Reviewer: independent read-only review, 2026-10-19. Scope: capabilities that already exist in Rhythm 2.0 and that
27. Review R2: Rhythm 1.0 CRM functionality missing from 2.0 and from this document: Independent review of RHYTHM-CRM-ARCH-001 (README, chapters 01–18, evidence e01, e02, e06), 2026-10-19.
28. Review r3: consistency, ownership and feasibility: Reviewer pass 3 of RHYTHM-CRM-ARCH-001 (README and chapters 01–18 as of 2026-10-19 ~17:10 ET). Scope: internal
29. Review resolutions: How the three review reports were applied (2026-10-19 evening). Every high and medium finding was applied; low