Open engine, maintained operating layer
The engine and schema model are meant to stay understandable and inspectable. The maintained layer is the operational work that turns public or partner source material into coherent, queryable releases.
Map-first querying
The product is not a generic dashboard shell and not a pure GIS desktop replacement. The goal is to let someone ask a geographic question, move through place hierarchies, and keep context while the runtime selects from compatible packs behind the scenes.
Runtime catalogs
A runtime catalog determines what the current shell can see. That means the same underlying engine can expose a public demo surface, a broader member catalog, or a private local catalog without changing the basic query model.
Why the split matters
This keeps the product honest. Hosted convenience, maintained releases, support, and broader access are the paid layer. The value is not a fictional ownership claim over raw public data. The value is the maintained system around it.