DaedalMap documentation.
Shared runtime, maintained packs, and the public surfaces built on top of them.
Reference
FAQ
Quick answers about DaedalMap, maintained evidence, packs, access paths, and source trust.
Runtime
How It Works
The maintained evidence layer, the three human modes, and the runtime path from source to answer.
Data
Packs
Pack structure, release tiers, and why packs are the unit of maintained geographic evidence.
Geography
Geometry Tools
Technical point lookup, boundary, hierarchy, and sibling-layer bridge tools.
Geography
loc_id Guide
The shared location key that ties packs, maps, research corpora, watches, and agent calls together.
Data
Source Map
Which source families are live, where the strongest maintained paths exist, and where gaps remain visible.
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, bounded corpus analysis, source-backed answers, and slower evidence.
Data
Prepare Your Data
Shape tables with loc_id, time fields, metrics, and source notes before promoting them into maintained packs.
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
Source Data
The source sheet format for packs: maintainer, methodology, update dates, coverage, and caveats.
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.
Workflow
Grant Finder
Shareable notes for the private grant-research lane: matching, shortlists, memo support, budget framing, and submission checks.