African Parks Network
Integrated Conservation Portal
One authenticated network. Independent portals, independent park runners, and explicit communication contracts.
Network Hub
→
Service portals
→
LTSS/BP nodes
Independent park runners
33
Own data frame, users and release manifest
Core service portals
4
Separately deployable platform capabilities
Registered clusters
3
Read-only aggregation relationships
Independent systems
Core portals
Each card opens its isolated runner workspace.
Portal registry
The directory is a read-only view of independent portal boundaries.
LTSS/BP park nodes
Every park remains independently deployable and insulated from changes to every other park.
Landscape clusters
Clusters aggregate published outputs without taking ownership of member-node data.
User control
Runner isolation
Independent user dictionaries
Each runner owns its own dictionary; network administrators are inherited explicitly.
Network events
Cross-portal communication is accepted through versioned events. Direct writes into another runner are prohibited.