← SAIRYOCONTENT HISTORY

Update to SAIRYO

Snapshot Oct 24, 2026 · 13:05 UTC · version 2.0.0

Collection source: downloaded plugin package.

WHAT CHANGED

First saved snapshot

No earlier snapshot is available to establish a change.

Save SAIRYO and check future changes in Following.

Up to 3 plugins free · no card required.

Compare saved observations

Download comparison JSON
Full technical diff · 0 changed fields
Full snapshot data
{
  "description": "Reconcile Event and video-content sales, refunds, fees and settlement statuses without double-counting.",
  "included_files": [
    {
      "relative_path": "agents/openai.yaml",
      "size_in_bytes": 535
    }
  ],
  "name": "sairyo-revenue-reconciliation",
  "skill_md_contents": "---\nname: sairyo-revenue-reconciliation\ndescription: Reconcile Event and video-content sales, refunds, fees and settlement statuses without double-counting.\n---\n\n# Reconcile SAIRYŌ revenue\n\n1. Identify whether the Event record represents a scheduled event or video content; request period, event IDs, currency and gross/net/payout measures.\n2. Use `get_event_sales_summary`, `get_sales_metrics_for_date_range`, `list_event_transactions`, `get_transaction_details`, `generate_event_insights` and authorized CSV exports when relevant; respect access scopes.\n3. Compare paid/successful transactions to gross sales; reconcile refunds, fees and net earnings. Do not equate net revenue with paid-out Stripe balance.\n4. For paid videos, verify that the selected content Event is actually included in the Event-level datasets; the current 64-tool MCP catalog does not separately expose video playback, content entitlements or content-specific payout ledger.\n5. Distinguish historical data, report freshness, refunds in flight and settlement delay. Do not mix currencies or count the same video-Event transactions in both Event and Video buckets.\n6. Where metrics are not exposed, request a SAIRYŌ dashboard CSV and give a reproducible reconciliation rather than guesses. Exports may contain PII; only reveal permitted fields.\n"
}

SHA-256 of public snapshot: f69e964d7b7acbac13aed3fbd08670a8b7585b8e10d1b5b1be4a049a1e904118