Rhythm 2.0 Specifications

Appearance

Product areas

CRM

CRM

CRM gives an association a shared understanding of the people and organizations it works with. The area connects identity, relationships, geographic grouping and the context of ongoing work. Staff can orient themselves around the same records instead of keeping separate pictures of a person in each application. That shared foundation supports coordination across teams and gives neighboring applications a stable place to refer to the people involved in their work.

4 modules: Activities, Follow-ups and Task Work · Duplicate Review and Record Merging · Entities · Regions. A module holds features; each feature names its key concepts, capabilities, journeys and acceptance test sets.

Features
21
Capabilities
72
Journeys
22
Acceptance test sets
72
Awaiting approval
159

Read the area overview 10 actors Responsibilities

Architecture 3

The architecture decisions this area was built to, converted verbatim from their source artifacts.

  1. ARCH-CRM-01Rhythm CRM ArchitectureRHYTHM-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.29 partsCRM and people
    • Proposed

    Source: the artifact in the Architecture Library ↗ (proposed there)

  2. ARCH-CRM-02Households and Membership CoverageProposes how Rhythm 2.0 CRM should record households (the group an organization mails and recognizes as one unit), person-to-person relationships such as spouse or guardian, and who a membership covers and why, for museums, churches, fundraising shops and family clubs. Andrew ruled all nine decisions on 2026-10-21 (six as recommended, three changed: CRM-owned relationship tables, a household may hold a membership, implementation deferred until a signed customer needs it); nothing is built.33 partsCRM and people
    • Proposed

    Source: the artifact in the Architecture Library ↗ (decided in part there)

  3. ARCH-CRM-03Rhythm 2.0: Data Enrichment ArchitectureProposes how Rhythm 2.0 enriches contact and organization records from external data providers for association staff: provider answers are stored as claims rather than facts, staff review suggestions before anything changes, CRM (customer relationship management) keeps every write, and spend is bounded per association. Proposed on 2026-10-22 as RHYTHM-ENR-ARCH-001; the same day Andrew ruled the six decisions that gate the first milestone (enrichment lives inside CRM, tier 3 personal-identity data offered from ENR-M1 behind attestation, the other four as recommended), six decisions remain open and nothing is built.27 partsCRM and people
    • Proposed

    Source: the artifact in the Architecture Library ↗ (decided in part there)

Modules 4

Product-Area Documents 3

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.

Rhythm Software