What problem does it solve? Understanding the Salesforce Revenue Cloud (RLM) data model requires knowing how 263 objects, 4,252 fields, and 674 relationships connect across 9 domains, and release-to-release schema changes (such as the 262 to 264 field removals) silently break queries and integrations built on outdated assumptions. ## Core Features & Use Cases - Domain-Organized Schema Reference: Per-domain reference files cover PCM, Pricing, Rate Management, Configurator, Transactions, DRO, Usage, Billing, and Approvals with object tables, key fields, and relationships. - Cross-Domain Relationship Maps: Documented foreign key paths show how Product2, Account, PriceBook2, UsageResource, and LegalEntity connect domains, plus the full quote-to-cash object lifecycle. - Verified Release Deltas: Field-level 262 to 264 changes are recorded with migration guidance, such as usage policy bindings moving to ProductUsageResourcePolicy. - Use Case: When writing a SOQL query to resolve overage chargeability for a usage entitlement, look up the Usage domain file to learn that 264 sources it from UsageOveragePolicy via ProductUsageResourcePolicy rather than the removed TransactionUsageEntitlement.ChargeForOverage field. ## Quick Start Ask the agent to explain how products, pricing, and usage grants relate in Revenue Cloud using the data model skill and its domain reference files.