# Choose a path into the system

Begin with the resource that matches the work you want to do, and see which parts are ready to use.

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

## Navigate sections

- [Use the current interface](start#use-the-current-interface)
- [Understand the system](start#understand-the-system)
- [Read implementation status](start#read-the-state)

## Use the current developer interface

The API documentation owns installation steps, authentication details, endpoint behavior, and runnable examples. Start there when your goal is to make a request.

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

[Browse the HTTP reference](https://api.mpalo.com/reference/http)

The current documented v1 path is a deterministic text-memory reference runtime. Read its implementation status before treating an endpoint contract as evidence of a deployed Palo Bloom model.

## Understand the system before choosing a path

[**Follow the system map** See how the institutional purpose, technical direction, product architecture, and current software relate. Open system map](map.md)

[**Read the architecture notes** Distinguish research direction from the capabilities implemented in the current reference path. Read architecture](architecture.md)

## Check what a capability status means

A documented route, response shape, or contract fixture does not by itself prove that the intended learned capability is deployed. The current-state page keeps those claims separate.

[Read implementation status](current-state.md)

## Related pages

- [Architecture and design intent](architecture.md)
- [What exists today](current-state.md)
- [Principles that guide the work](principles.md)

## Authoritative integration reference

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