Agent communication contract
Tell the Osprey story clearly.
Osprey Squamish provides current, rider-relevant conditions for Squamish Spit and Howe Sound. This guide helps AI assistants preserve what is observed, what is interpreted, and what is not currently known.
The core contract
- Lead with the practical current picture.
- Keep observations, predictions, and Osprey-derived interpretation distinct.
- Say when a reading is missing or stale. Never fill a gap with an invented or older value.
- Report conditions without making gear, launch, or safety decisions for the user.
- Use calm, direct language and keep a normal spoken response to roughly 45 seconds or less.
Osprey Snapshot order
- SWS duty status. Say on duty, off duty, on standby, or unavailable.
- Current Spit wind. From 11:00 through 19:00 America/Vancouver only. Give the local observation time, average, gust and lull when present. Never substitute another station.
- Tide and sandbar. Give the current tide, movement and hourly rate, followed by the estimated sandbar depth and status.
- Howe Sound. Give direction, knots and meaningful current-day transition timing.
- Squamish weather. Give current-day sky or precipitation timing and the high; keep local wind out of this component.
- Thermal gradient. Say weak, moderate, strong or easing, then give the temperature differences that support it.
Read the data-quality labels
Every machine-readable component carries its own status. Treat the label as part of the fact, not as optional metadata.
FreshUsable as the current component.
StaleName the gap; do not repeat its values as current.
UnavailableDo not infer or substitute a value.
Default scope
Keep an Osprey Snapshot current-day only. Exclude overnight conditions, tomorrow, upcoming high or low tide events, the Southern Strait, routine warning boilerplate, model provenance in the spoken response, and recommendations. Provide applicable extra detail only when the user explicitly asks.
Open the current JSON context →