Design enterprise cdp with org structure

[312268112]

Initiate the design process for an enterprise Customer Data Platform (CDP) to gather detailed requirements.

The current state reflects the initial phase of requirement gathering for a specialized CDP targeting enterprise users, focusing on organizational structure and B2B scenarios. The AI is prompting the user for more information before generating the full design document.

---

 

---

Note

Adds a full enterprise CDP design document detailing architecture, identity (OneID), org modeling, data/labels/audience, security/compliance, tech stack/deployment, services, roadmap, and core APIs.

• Docs:
  • Adds comprehensive design spec in docs/enterprise-cdp-design.md for an enterprise B2B CDP.
    • Architecture: 5-layer system, core data flows, data collection SDK and pipelines (Kafka/Flink), storage choices (MySQL/CH/ES/HBase/Neo4j/Hive).
    • Identity (OneID): ID-mapping rules/flow, unified customer view, service capabilities.
    • Org Modeling: Enterprise hierarchy, contact-org relations, graph DB optimization (Neo4j), org visualization.
    • Data Modeling: ODS/DWD/DWS/ADS layers; account, contact, and event schemas.
    • Labels & Audience: Tag taxonomy, compute engine/process, storage; multi-stage audience query engine and APIs.
    • Security & Compliance: PIPL requirements, masking/encryption, RBAC/data permissions, audit logs.
    • Tech & Deployment: Backend/frontend stacks, cloud and on-prem deployments, microservice split and comms.
    • Implementation Roadmap: MVP → Enhanced → Intelligent phases; success cases and appendices (KPIs, service APIs).

^{Written by Cursor Bugbot for commit 9797397. This will update automatically on new commits. Configure here.}

[cursor]

Cursor Agent can help with this pull request. Just @cursor in comments and I'll start working on changes in this branch.
_{Learn more about Cursor Agents}