Second Life
Second Life is the in-world radio and instant-message path into ERIS. This page covers on-duty traffic, tasks, and notices on that path.
Those paths connect through Corrade, LSL proximity, and GridNet-style mirrors into the same dispatch operating context. Transport lives in channel adapters; radio discipline and tasks live in the dispatch module.
Radio (GridNet)
On-duty and field traffic can include callsign status phrases, radio checks, and task claims spoken on radio. ERIS tracks unit activity and responds when addressed; ambient chatter is not answered with generic fallback spam onto global channels.
A Discord channel can mirror GridNet radio into the same dispatch handler for mixed RP operations.
Tasks and alerts
High-priority alerts may fan out to radio and create dispatch tasks when alerts and dispatch modules are both enabled. Tasks are claimed and completed with explicit radio or HTTP status updates—not free-text invention of assignments.
Instant messages and notices
When Corrade reports login or location for a linked avatar, ERIS may flush the same cross-platform inbox notices as Discord DMs. Inbound IM OK / ACKOFF behaves like Discord when the HUD posts instant messages to the Corrade notify API.
Roster rows need the avatar’s Second Life UUID for attribution and notice delivery. Linking is an operator and personnel concern, not something this page documents as a bypass.
What this is not
Second Life integration does not replace the standalone ops desk or in-sim dispatch services when the brain link is off; it adds ERIS-side discipline and enrichment when channels and modules are enabled.