> For the complete documentation index, see [llms.txt](https://docs.doubleloop.app/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.doubleloop.app/map-building/map-objects.md).
# Map objects
## Cards (a.k.a. Flexible cards)
Use "Cards" to add any type of object you'd like to maps. You can customize the "types" of cards you add to match the vocabulary of your company.
Examples: Objectives, Customer Journey Steps, Pillars, Teams.
## Metrics
"Metrics" have time series data aggregated into stats. You can connect metrics to your data sources. Connect two metrics to see the correlation between them. You can attach key results to metrics if you'd like to set targets.
Examples: Monthly active users, ARR.
## Bets
"Bets" can be anything your company is investing in to achieve a business outcome. You can record hypotheses and results for bets.\
\
Examples: Improve song recommendation algorithm, launch new marketing campaign.
## Work
"Work" is similar to bets, but it's more intended for tactical execution. If you connect your work management tool, you can add (e.g.) Jira objects directly to your maps.
Examples: Implement AI model for song recommendations, back-end refactor.
## Sub-maps
If your map is getting too complex, you can nest maps inside maps. For example, you might have a company-wide map that shows how your products fit into the big picture of your strategy. Each product itself can be a map, with its on metrics.
Example: Marketing strategy, Checkout team strategy
## Sections
Use sections to logically organize your map. Add connectors to sections to avoid having to draw lots of connects to individual nodes.
## Notes
Add any text you want to provide context.
## Images
Add screenshots or any image you'd like.
---
# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.
## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.
Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:
```
GET https://docs.doubleloop.app/map-building/map-objects.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.
Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.