← SAIRYOCONTENT HISTORY
WHAT CHANGED
Update to SAIRYO
Snapshot Oct 24, 2026 · 13:05 UTC · version 2.0.0
Collection source: downloaded plugin package.
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 JSONFull technical diff · 0 changed fields
Full snapshot data
{
"description": "Validate readiness for either live Events or video-content Events before public release.",
"included_files": [
{
"relative_path": "agents/openai.yaml",
"size_in_bytes": 536
}
],
"name": "sairyo-publishing-readiness",
"skill_md_contents": "---\nname: sairyo-publishing-readiness\ndescription: Validate readiness for either live Events or video-content Events before public release.\n---\n\n# Publish SAIRYŌ Events and Content safely\n\nUse this for publication or visibility changes involving scheduled events, on-demand regular video or spatial video Events.\n\n1. Determine the Event's actual content classification and identify the record via `list_managed_events`, `get_event_detail` or authorized lookup; do not infer content type solely from its title.\n2. Read `get_event_management_context`, current tiers, media, and payout state. Check `get_event_publish_readiness`; report blocking issues verbatim. Do not bypass requirements by changing content type.\n3. For Apple spatial video, inspect processing/validation results. Backend may require `.aivu` input or `mediaStatus=READY` and `mediaProfile=SPATIAL_RECTILINEAR`; confirm on the actual record, not via inference.\n4. Use `render_event_publish_preview` if available. Show visibility, dates, prices, access, media and any limitations. Seek explicit user approval immediately before publication.\n5. Publish with `publish_event` only when supported for the selected Event type and user has approved. Verify with `get_event_detail` and explain any remaining content playback limitations.\n6. Never claim the content itself has been uploaded, trans-coded or playback-tested just because the Event record was published; use website workflow when APIs do not expose primary media processing.\n"
}SHA-256 of public snapshot: 24cbee67871ad47034bfade92a8fb87534d0dfca9b77a98074b93aaaa23658c8