# Annotation catalog — key Core objects (ClientVerse Core 1.1.7)
# Priority Core objects the guides reference. Object-level meaning is authored here; full
# field-level detail lives in the Data Dictionary v3.0 (../../data-model/) — cite, don't duplicate.
# Structural facts are authoritative in ../catalog.json. See ../README.md, ../../_conventions.md.
package: core
module: null
applies_to: [core]
field_reference: ../../data-model/ClientVerse_Data_Dictionary_v3.0.md
annotation_status: drafted

objects:
  - api_name: Matter__c
    label: Matter
    field_count: 84
    data_source: PMS (practice management system)
    audience: [attorneys, bd, executives]
    description: >
      A piece of legal work the firm performs for a client — the central "work" entity. Sourced
      from the firm's practice management system. Connects clients (Account) to the lawyers,
      experience, time, and financials associated with the engagement.

  - api_name: Experience__c
    label: Experience
    field_count: 90
    data_source: Experience system / user-entered
    audience: [attorneys, bd, marketing]
    description: >
      A described instance of work the firm has done, captured for reuse in pitches, proposals, and
      directory submissions. The richest object in the model; the heart of experience management.

  - api_name: Experience_Holder__c
    label: Experience Holder
    field_count: 22
    data_source: Experience system / user-entered
    audience: [attorneys, bd]
    description: >
      Links a person (lawyer) to an Experience and the role they played in it, so individual
      experience profiles can be assembled.

  - api_name: Classification__c
    label: Classification
    field_count: 18
    data_source: User-entered / configuration
    audience: [admins, bd, marketing]
    description: >
      A node in a firm taxonomy (e.g. practice areas, industries, regions). Classifications are
      assigned to records to drive segmentation, lists, and reporting.

  - api_name: Classification_Assignment__c
    label: Classification Assignment
    field_count: 40
    data_source: User-entered / calculated (assignment rules)
    audience: [admins, bd]
    description: >
      Assigns a Classification to a record. Can be applied manually or by classification assignment
      rules. The join that makes the taxonomy actionable.

  - api_name: List__c
    label: List
    field_count: 20
    data_source: User-entered (List Builder)
    audience: [marketing, bd]
    description: >
      A curated or rule-driven set of members (contacts/accounts) built with List Builder. Static
      lists hold fixed members; dynamic lists are defined by SOQL/criteria. Feeds campaigns and
      outreach.

  - api_name: List_Member__c
    label: List Member
    field_count: 19
    data_source: User-entered / calculated
    audience: [marketing, bd]
    description: >
      Membership of a record in a List, with the metadata needed to manage and sync list/campaign
      membership.

  - api_name: Collaborator__c
    label: Collaborator
    field_count: 20
    data_source: ERM / user-entered
    audience: [attorneys, bd]
    description: >
      A person who works with the firm's people on relationships and matters; underpins the
      collaboration and team-sharing model.

  - api_name: Wall__c
    label: Wall
    field_count: 6
    data_source: User-entered
    audience: [attorneys, bd]
    description: >
      A collaboration space for a team to share records and updates, with role-based membership and
      sharing.

  - api_name: Connection__c
    label: Connection
    field_count: 34
    data_source: ERM (enterprise relationship management)
    audience: [attorneys, bd, relationship-managers]
    description: >
      A relationship signal between a firm person and an external contact, sourced from relationship
      intelligence (email/calendar analysis). Powers "who knows whom".

  - api_name: Trip__c
    label: Trip
    field_count: 8
    data_source: User-entered (BD trip planning)
    audience: [bd, attorneys]
    description: >
      A planned business-development trip/event, with legs, targets, participants, and an optional
      business plan. The anchor of the BD trip-planning feature.

  - api_name: Pitch_Proposal_Builder__c
    label: Pitch / Proposal Builder
    field_count: 7
    data_source: User-entered (BD)
    audience: [bd, attorneys, marketing]
    description: >
      A workspace for assembling a pitch or proposal from reusable elements (experience, bios,
      credentials). Drives the proposal workflow.

  - api_name: Referral__c
    label: Referral
    field_count: 6
    data_source: User-entered
    audience: [bd, attorneys]
    description: >
      A referral of business between people/firms, tracked for relationship and revenue attribution.

  - api_name: Time_Entry__c
    label: Time Entry
    field_count: 29
    data_source: PMS (practice management system)
    audience: [executives, bd]
    description: >
      Recorded billable/non-billable time, sourced from the PMS. Aggregated into timekeeper and
      financial summaries and used by Whitespace coverage analysis (Modules).

  - api_name: Saved_Search__c
    label: Saved Search
    field_count: 14
    data_source: User-entered
    audience: [attorneys, bd, marketing]
    description: >
      A persisted search definition a user can re-run, share, or drive lists/dispatches from.

  - api_name: Firm_Content__c
    label: Firm Content
    field_count: 15
    data_source: User-entered / integration
    audience: [marketing, bd]
    description: >
      A piece of firm content (alert, article, event) that can be associated with classifications,
      contacts, and distribution. Basis of the content library.

  - api_name: Intelligence_Asset__c
    label: Intelligence Asset
    field_count: 8
    data_source: User-entered / integration
    audience: [bd, attorneys, executives]
    description: >
      A piece of strategic client intelligence captured for business development.