System documentation · platform view
HPS Portal Ecosystem
A shared architecture view for the public HPS Geospatial surfaces: the Portal provides orientation while the Poster Generator owns its specialized workflow.
Ecosystem model
How the systems relate
Portal → product
The Portal directs users into the operational surface and provides shared context, documentation, and contact paths.
Product → Portal
The Poster Generator can publish status, documentation, outputs, or links back to the Portal without surrendering its core workflow.
Shared foundation
Brand tokens, navigation rules, and deployment conventions keep the public experience coherent.
Cross-system principles
Clear ownership
Each system owns its domain data, workflows, and implementation decisions.
Explainable handoffs
Preserve source, version, attribution, and status metadata when outputs move between systems.
Shared design language
Use HPS Geospatial tokens and logo rules while maintaining distinct product identities.
Implemented vs proposed
Label planned exports, integrations, and services until they are verified in production code.
Shared stack candidates
HPS design system
Corporate logo assets, color tokens, typography guidance, and product-brand rules.
Identity and access
Define access controls only for workspaces that require restricted operational data.
Artifact exchange
Define a durable contract for posters, metadata, downloads, and versioned outputs.