Curated has three primary surfaces you'll work in: Spaces, Artifacts, and Maps. Knowing what each one is — and how they relate — makes the rest of the product self-explanatory.
Spaces
A Space is a container for everything related to one project, market, or question. Think of it as a folder you'd open before starting work, except every conversation and output inside it is connected by Curated's understanding of the context.
Examples of how teams organize Spaces:
- One Space per region: "Texas markets," "Southeast expansion," "California portfolio"
- One Space per project: "Q3 site selection," "ACME franchise audit," "New product launch"
- One Space per customer: "Bank of Madison," "Riverside Property Group"
Within a Space:
- All conversations share the same default layers and filters
- All artifacts produced are grouped together
- All teammates with access to the Space see the same context
Switch Spaces in the sidebar at any time. Open a fresh Space when you start a new line of work — Curated will treat it as a clean slate, free of prior context.
Maps
A Map is what it sounds like: an interactive ArcGIS map with the layers you and Curated have added to it. Each Space has at least one Map; you can have multiple in a single Space if you want to compare states.
Maps are live: zoom, pan, click features, toggle layers, run a measurement. Curated sees the current map state and uses it when interpreting your prompts. Asking "how many of these are in the visible area?"* works because Curated knows what's currently on screen.
A Map is not a finished output — it's the working surface. When you want to share what's on the Map, you generate an Artifact from it.
Artifacts
An Artifact is anything Curated produces that you can save, version, share, or export. Most artifacts are generated by an agent in response to a prompt.
Types of artifacts:
- PlaceStory — narrative brief about a location
- PDF report — multi-page styled output, ready to email
- Marketing post — copy + image for a specific platform
- Map export — a static snapshot of the current Map with a legend
- Data table — filtered, exportable rows from a query
- Playbook output — structured deliverable from a vertical playbook (e.g. Active-Wellness deck)
Every Artifact:
- Has its own URL — share with anyone in your org without re-running the prompt
- Has version history — earlier versions are preserved and comparable
- Belongs to a Space — so it's findable in context
- Cites the layers, data sources, and (where applicable) web sources it used
How they fit together
Workspace (your organization's Curated environment) └── Space (one project / market / customer) ├── Map(s) (live working surfaces) ├── Conversations (the prompts you've run) └── Artifacts (the saved outputs)
When you're working day-to-day: you open a Space, interact with its Map, run conversations, and generate Artifacts. When you switch projects, you switch Spaces. When you share work outside your team, you share Artifacts.
What's next
Read Sign In and Ask Your First Question to walk through a real prompt-to-artifact flow end-to-end.