map-the-landscape

# Map the Landscape Build a useful mental model, not an exhaustive catalog. Reveal the structure that makes details make sense: what is inside the boundary, what sits outside it, which relationships matter, how value or data moves, why the landscape looks this way, and where uncertainty remains. ## Set the Zoom Infer these from the request and available context: - **Subject:** the topic, field, ecosystem, or repository to map. - **Mode:** `topic`, `repository`, or `hybrid` when a repo must be placed in its wider ecosystem. - **Audience:** the user's current knowledge and intended use. - **Decision:** what the map should help the user understand or do next. - **Depth:** `snapshot`, `standard`, or `deep`. - **Time horizon:** current state by default; add history when it explains the present. Ask at most one clarifying question only when the subject or intended zoom is genuinely ambiguous. Otherwise state the chosen boundary and proceed. Use `standard` depth unless the user requests a quick overview or a deep study. ## Evidence Discipline Keep the map auditable without making it read like a research paper. - Label important statements as **Observed** when read directly from repository files, **Sourced** when supported by an external source, **Inferred** when deduced from evidence, and **Unknown** when evidence is insufficient. - For current or unstable topic claims, browse and cite authoritative sources. Prefer primary documentation, specifications, papers, rep...