Reference
FAQ
Quick answers to the main questions about the engine, packs, hosted access, contributor workflows, and self-hosting.
View pageDocs
Public system notes for
how DaedalMap works.
Find details here on the system behind the map: coverage, packs, hosted versus local use, and the path to building or running your own version.
Open on GitHubReference
How It Works
A high-level view of the engine, maintained pack model, runtime catalogs, and why the map product is built this way.
View pageData
Source Map
See which source families are live, where the strongest maintained paths exist, and where the gaps are still visible.
View pageData
Packs
The explanation of pack structure, release tiers, and the difference between a durable pack library and a hosted runtime.
View pageData
Make A Pack
A walkthrough for contributors who want to build a source pack, use it, document it, and release it.
View pageData
Source Data
The source sheet format for packs: maintainer, methodology, update dates, coverage, and caveats.
View pageReference
Accounts
Why login exists, what a settings-backed workspace means, and how persistence differs between guest and signed-in users.
View pageDeployment
Hosted vs Local
The practical differences between using DaedalMap in the hosted app, local analyst mode, or a self-hosted environment.
View pageDeployment
Self-Host
The current self-host path through the open GitHub repo, plus the longer-term direction toward a simpler native install.
View page