slug: common-room
provider: Common Room
generated_by: planning/capability-mapping/scripts/classify_capabilities.py
model: claude-opus-5
frame:
- Software & Technology
min_confidence: 0.7
capability_model:
  source: https://github.com/vincentmakes/turbo-ea-capabilities
  license: CC-BY-4.0
  attribution: Turbo EA Capabilities by Vincent Verdet — Turbo EA, https://github.com/vincentmakes/turbo-ea-capabilities,
    CC BY 4.0
  notice: NOTICE
edge_count: 4
edges:
- tag: Contacts
  spec_file: common-room-contacts-api-openapi.yml
  capability_id: BC-420.10
  capability_id_l1: BC-420
  capability_name: Customer Data Management
  confidence: 0.8
  evidence: 'GET /user/{email} Get Contact by E-Mail; DELETE /user/{email} Anonymize Contact; GET /members
    Get Contact By E-Mail or Socials; vendor: ''single identity-resolved view of contacts and organizations'''
  reason: Operations create, retrieve, match and anonymise contact records resolved across email and social
    identities — this is customer/contact master data and identity resolution, the core of Customer Data
    Management.
- tag: Right to Be Forgotten
  spec_file: common-room-right-to-be-forgotten-api-openapi.yml
  capability_id: BC-130.50
  capability_id_l1: BC-130
  capability_name: Privacy & Data Protection Management
  confidence: 0.8
  evidence: DELETE /user/{email}  deleteUserByEmail  Anonymize Contact
  reason: The operation anonymizes a person's record on request, i.e. fulfilment of a data-subject erasure
    right — privacy and data protection compliance. Some chance the intended fit is the SaaS-specific
    service privacy commitment capability instead.
- tag: Segments
  spec_file: common-room-segments-api-openapi.yml
  capability_id: BC-420.20
  capability_id_l1: BC-420
  capability_name: Customer Segmentation Management
  confidence: 0.8
  evidence: POST /segments  Create a segment; POST /segments/{id}  addContactsToSegment  Add Contact(s)
    to Segment
  reason: Creating segments and assigning contacts to them is customer/prospect segmentation management
    within CRM, not a technical grouping construct — the schemas (CreateSegmentRequest, ApiSegment) and
    contact membership confirm it.
- tag: Organizations
  spec_file: common-room-organizations-api-openapi.yml
  capability_id: BC-420.10
  capability_id_l1: BC-420
  capability_name: Customer Data Management
  confidence: 0.7
  evidence: GET /organizations Get an organization by ID / List organizations; schema Organization referencing
    Contact, ApiLocation, ApiLeadScore
  reason: Organizations are the company-level records in the identity-resolved account/contact graph,
    exposing firmographic and related-contact data — customer/account master data. Some ambiguity with
    Account Management (BC-410.20), but the surface is read-only data retrieval rather than account planning,
    so Customer Data Management fits better.