SEPAN · Snake Encounter Pattern Analysis Network
A Report is what a source told the system. An Encounter is the reviewed event. They remain separate so duplicate reports, uncertainty and misidentification are preserved rather than overwritten.
Encounters can connect to responses, captures/checks, individual snakes and identifiers, releases/relocations, bites and media references.
SEPAN code → GitHub → hosted interface releases → each organisation retains its own governed Grist database.
A portable Starter can also be used as a pinned deployment in a Grist environment. UI updates can be automatic; database migrations are deliberate, versioned and backed up.
Public Demo → Starter / design materials → configured pilot.