System
How It Works
A high-level explanation of the open engine, maintained pack model, runtime catalogs, and why the map product is built this way.
Read pageDocs
Public system notes for
how DaedalMap works.
This section is for product and system explanations that should live on the public site: how the engine works, how packs are organized, and how hosted and local use fit together.
Data
Packs
The public explanation of pack structure, release tiers, and the difference between a durable pack library and a hosted runtime.
Read pageMetadata
Source Data
The public-facing source sheet format for packs: maintainer, methodology, update dates, coverage, and caveats.
Read pageCoverage
Source Map
A public-facing coverage map that shows the source families currently in play, what they cover, and where the strongest maintained packages exist today.
Read pageWorkspace
Accounts
Why login exists, what a settings-backed workspace should mean, and how persistence differs between guest and signed-in use.
Read pageContribute
Make A Pack
A scaffolded walkthrough for contributors who want to build a source pack, document it, and move it toward QA and release.
Read pageDeployment
Hosted vs Local
The practical difference between using DaedalMap in the hosted app, local analyst mode, or a self-hosted environment.
Read pageDeployment
Self-Host
The current self-host path through the open GitHub repo, plus the longer-term direction toward a simpler native install.
Read pageReference
FAQ
Quick answers to the main questions about the engine, packs, hosted access, contributor workflows, and self-hosting.
Read page