# How the pieces connect

Follow the relationship between Mpalo’s purpose, technical direction, research architecture, and current developer interface.

HTML page: https://developer.mpalo.com/map
Markdown page: https://developer.mpalo.com/map.md

## Navigate sections

- [The map](map#the-map)
- [Follow a path](map#follow-a-path)

## Purpose and technical direction

1. [**Institutional purpose** Mpalo’s institutional purpose, guiding the work that follows.](https://mpalo.com/our-mission)
Relationship to next: guides
2. [**Experience-aware memory** The technical focus pursued today.](architecture#technical-focus)
Relationship to next: pursued through
3. [**Palo Bloom** The memory architecture under development.](architecture#palo-bloom)
Relationship to next: first planned layer
4. [**PaloSpring** The first planned application layer for Palo Bloom.](architecture#palospring)

## Available to developers today

1. [**Hosted v1 runtime** Stores text deterministically and retrieves it lexically today.](current-state#runtime)
Relationship to next: documented in
2. [**API quickstart and reference** The API reference, integration guide, and endpoint contracts.](https://api.mpalo.com/get-started)

The upper path shows technical direction. The lower path shows the hosted interface available today.

## Continue from your question

- [What is Mpalo developing?](architecture.md)
- [What is implemented today?](current-state.md)
- [Where do I begin integrating?](start.md)

## Related pages

- [Architecture and design intent](architecture.md)
- [What exists today](current-state.md)
- [One institution, distinct domains](domains.md)

## Authoritative integration reference

- [API quickstart](https://api.mpalo.com/get-started)
- [API reference](https://api.mpalo.com/landing)