# Mpalo Developer Hub

> Public guide to Mpalo’s technical direction, design principles, system relationships, and documented implementation status.

## Start here

- [Overview](https://developer.mpalo.com/index.md): Choose a topic and understand the boundary between this hub and the API docs.
- [Structured page index](https://developer.mpalo.com/index.json): Machine-readable page URLs, section anchors, related links, and system map.
- [Complete text edition](https://developer.mpalo.com/llms-full.txt): All public developer hub pages in Markdown.

## Public pages

- [Mpalo’s design principles](https://developer.mpalo.com/index.md): This hub translates Mpalo’s mission into shared principles, foundations, and domain-specific rules for interfaces.
- [No-Go’s](https://developer.mpalo.com/no-gos.md): A direct reference for design choices Mpalo should not make, grounded in institutional truth, human agency, and domain boundaries.
- [Principles that guide the work](https://developer.mpalo.com/principles.md): Mpalo’s mission and ground principles provide the reason and constraints for every design decision.
- [One institution, distinct domains](https://developer.mpalo.com/domains.md): The domains share Mpalo’s purpose and identity while adjusting language, visual density, and interaction to the work each one serves.
- [The parts we can govern](https://developer.mpalo.com/elements.md): A practical index of design decisions, from spacing and surfaces to controls, assets, and behavior, with one home for each category.
- [Choose a path into the system](https://developer.mpalo.com/start.md): Begin with the resource that matches the work you want to do, and see which parts are ready to use.
- [How the pieces connect](https://developer.mpalo.com/map.md): Follow the relationship between Mpalo’s purpose, technical direction, research architecture, and current developer interface.
- [Architecture and design intent](https://developer.mpalo.com/architecture.md): Separate Mpalo’s institutional purpose, the architecture being developed, and the software path documented today.
- [What exists today](https://developer.mpalo.com/current-state.md): Read the deterministic text-memory runtime and lexical retrieval status separately from research direction and planned product work.

## Authoritative integration documentation

- [API quickstart](https://api.mpalo.com/get-started): Installation, authentication, and first requests.
- [API reference](https://api.mpalo.com/landing): Endpoint behavior and integration contracts.

## Reading guidance

- Treat status wording on each page as the boundary for claims about current behavior.
- Planned architecture, research direction, and contract-stage response shapes do not establish deployed capability.
- This hub does not publish staff-only or internal operating material.