Files
kamidso-back/kamidso/native_connectors/providers/didar/golden_reconciliation_template.json
T
javadandCursor edbaa2acec Add native Didar connectors so chats can query CRM data reliably.
Connector calls, semantic rules, and DuckDB memory keep long runs stable, and stream retry stops chats from stalling.

Co-authored-by: Cursor <cursoragent@cursor.com>
2026-10-12 19:26:47 +03:30

43 lines
1.4 KiB
JSON

{
"schema_version": "1.0",
"provider": "didar",
"description": "Fill this file with values read from the real Didar panel for one test account. Do not commit real customer identifiers or secrets.",
"test_account_alias": "staging-or-sanitized-account",
"timezone": "Asia/Tehran",
"calendar": "jalali",
"currency_profile": {
"base_currency_id": null,
"base_currency_code": null,
"base_currency_name": null,
"display_unit": null
},
"periods": [
{
"id": "mehr_sample",
"period_text": "مهر ۱۴۰۵",
"panel_expected": {
"sales_won_count": null,
"sales_amount": null,
"currency_display": null,
"won_count": null,
"lost_count": null,
"pending_count_snapshot": null,
"sales_by_owner": []
},
"kamidso_actual": {},
"tolerance": {
"count": 0,
"amount_absolute": 0,
"amount_relative": 0
},
"result": "not_run"
}
],
"verification_rules": [
"Counts must match exactly.",
"Money must match within configured tolerance only after currency semantics are known.",
"For sales reports, compare against Didar 'گزارش کلی فروش' for the same period.",
"Record the date basis used by Kamidso.",
"If a mismatch exists, inspect raw response, resolved UTC boundaries, Status, ChangeToWonTime, CurrencyId, and API-key visibility/access before changing semantics."
]
}