# Counterparty document expectations # Counterparty document expectations Data also Providers Loads counterparty contact details and document requirements from spreadsheets into the graph store, mapping each requirement onto the governed vocabulary and setting aside anything that does not map. - **Used when** — When an expectations workbook arrives and its contents need to become queryable facts rather than a file. - **Loads first** - The upload skill, followed exactly. - The schema-exploration skill, to confirm the current shape of every entity and relationship it will write. - The persistence patterns, for validation, ingestion and read-back. - **Returns** - The source workbook, sheet, row count, counterparty count and contact count. - The target environment and the verified account. - The schema mappings used, and the validation and ingestion status. - Records written, by type. - The unresolved sidecar and its count. - A read-back sample, and any schema gap that prevented a fact from being stored. - **Hands off** - Model curator — extending the schema when a fact has nowhere to go ## Others in Data - Data-lake assistant - Dataset fulfilment - Knowledge search - Metric reconciliation - Model curator - Pipeline control panel - Property data exploration - Public record ingestion - Question answering - Report catalog - Search to production