# Model curator # Model curator Data Guards the shared graph schema, so that every entity type, relationship, property, index, enumeration and required field passes one review and ingestion and query behaviour stay consistent across services. - **Used when** — When a schema change is being designed, reviewed or applied — a new entity type, a new relationship, a property, an index, an enumeration value, or a deprecation. - **Loads first** - The schema-exploration skill, and the current schema file, downloaded before anything is proposed. - The update skill, for the workflow, the modelling principles and the review checklist. - The persistence product's patterns, to confirm the resulting payloads and queries still comply. - **Returns** - A domain summary of the entities and relationships being changed. - The explicit decision for each — a new entity, a new relationship, a new property, a derived index, or a deprecation. - Required-field and enumeration changes, justified from real source data. - Index additions, with their canonical source facts, change triggers and queries. - The immutability and revision-modelling decisions. - The exact schema difference applied, with validation and test results. - Downstream impact on ingestion and queries. ## Others in Data - Counterparty document expectations - Data-lake assistant - Dataset fulfilment - Knowledge search - Metric reconciliation - Pipeline control panel - Property data exploration - Public record ingestion - Question answering - Report catalog - Search to production