uhifadhi/module-contracts dependents (8) Order by: name | downloads Show: all | require | require-dev
-
PHP
uhifadhi/area-module
Area: what an installation manages — the named protected area, its gazetted boundary as a PostGIS multipolygon, and the answer to the seam's area contract so nothing has to be written by hand.
-
PHP
uhifadhi/incident-module
Incidents: what happened in an area — poaching, human–wildlife conflict (with fines and compensation), unauthorized construction and roadkill, as one record type served to every department that needs it.
-
PHP
uhifadhi/map-module
Map: the platform's map machinery — self-hosted Leaflet, the one basemap seam (configurable satellite provider: Esri, Google Map Tiles or a custom XYZ/WMTS source), the boundary drawing and the map chrome every map in the product wears.
-
PHP
uhifadhi/patrol-module
Patrols: field patrol effort as first-class records — GPX track ingest, en-route observations with photos, coverage mapping and a per-user widget dashboard.
-
PHP
uhifadhi/seam-module
The seam: the module seam runtime every uhifadhi module registers with — the catalogue, per-area installation, the permission declarations modules contribute, and the seed that keeps them in step.
-
PHP
uhifadhi/storage-module
Storage: the platform's file-storage machinery — named Flysystem storages, a private evidence API with a detected-MIME allowlist, thumbnails, and authenticated streaming behind a per-module permission seam.
-
PHP
uhifadhi/team-module
Team: who an installation's people are and how they sign in — the user account, the sign-in screen, the position that bundles permissions, and the permission catalogue every module's declarations fold into.
-
PHP
uhifadhi/widget-module
Widget: the dashboard machinery every module with a surface would otherwise reinvent — a surface registry modules declare into, one person's adopted preset and layout per surface, and the library component that arranges them.