DaedalMap documentation.
Shared runtime, maintained packs, and the public surfaces built on top of them.
Reference
FAQ
Quick answers about the engine, packs, hosted access, and the install-it-yourself path.
Data
Packs
Pack structure, release tiers, and why the pack is the unit of published truth across every mode.
Data
Source Map
See which source families are live, where the strongest maintained paths exist, and where the gaps are still visible.
Runtime
How It Works
Shared pack truth, lane-specific reasoning, deterministic execution, and the common map/display contract.
Deployment
Install It Yourself
Install the open runtime yourself. Start with the packaged local copy or use the GitHub/manual path for deeper deployment control.
Contributor
Make A Pack
A walkthrough for contributors who want to build a source pack, document it, and release it.
Contributor
Source Data
The source sheet format for packs: maintainer, methodology, update dates, coverage, and caveats.
Agent
loc_id Guide
Learn the shared location key used across packs, why joins stay clean, and why tsunami ocean-region ids look different.
Reference
Coverage Model
How packs describe country coverage against a shared 200-country baseline, using common_missing and uncommonly_included for exceptions.
Reference
Research Mode
Explore vs Research, what corpus-bound analysis means, and how both lanes stay on the same runtime truth.
Agent
For Agents
The shortest path for developers and agents: live endpoints, shared pack semantics, paid-lane flow, and the main MCP quickstart.
Agent
Agent Examples
Copyable free and paid calls built around the live flagship packs and the first successful earthquake flow.
Reference
Roadmap
What is being built, what is stable, and where the product is headed.