This section is directed at those who want to build on Alerta, adopt the protocol for their city in accordance with Article XIII, or understand the technical architecture that sustains the platform.
General architecture
Alerta operates on a Supabase backend (PostgreSQL with authentication and storage extensions) that sustains the four surfaces. The frontend is built on a modern React stack. The Saphi Intelligence constellation operates as a set of edge functions deployed on infrastructure shared with the backend.
The separation between surfaces (vigia, admin, aliados, docs) is logical rather than infrastructural: all four access the same dataset through differentiated authorization layers implemented with Postgres Row Level Security.
The data model
The core of the model rests on three principal tables:
- submissions records field observation submissions, in any processing state.
- observations contains validated and published records, with their complete verification chain.
- entities unifies the master register of Vigías, Expertos, Aliados and other institutional figures.
The auxiliary tables cover the seed economy, institutional agreements, counter-observation files, audit records and daily operations.
Adoption of the protocol
The adoption of the protocol in accordance with Article XIII follows a documented seven-step process: expression of interest, territorial study, adapted drafting, civic consultation, constitution of local chambers, ratification and technical integration. Each step has defined timeframes and deliverables.
License
The software components of Alerta are subject to license. The exact license and its scope will be published in a subsequent iteration. In accordance with Article XIV, the components will pass to the public domain under open license in the event of orderly dissolution of the platform.