# Documentation scope

How public documentation, internal records, and external sources are separated and labeled.

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

## Navigate sections

- [Public record](scope#public-record)
- [Internal working record](scope#internal-record)
- [Restricted material](scope#restricted-records)
- [Evidence and sources](scope#evidence-and-sources)

## Public record

This site contains information Mpalo has chosen to publish for developers and other readers.

The public pages explain Mpalo’s institutional identity, published product direction, verified implementation boundaries, developer resources, and research results selected for publication. The API reference at [api.mpalo.com](https://api.mpalo.com/landing) owns endpoint behavior and integration instructions. This hub explains how those technical surfaces relate to Mpalo and its current system.

## Internal working record

Mpalo’s private source documents preserve the reasoning and work behind selected public explanations.

The internal canon holds enduring identity, charter, product, and governance sources. Operational documentation holds current product specifications, engineering references, legal material, and working records. Active research hypotheses, unpublished results, and unratified drafts remain internal until they are reviewed for publication.

## Restricted material

Some records need narrower access than the general internal library.

Credentials, personal records, detailed vulnerability information, and sensitive incident material belong in systems with access controls suited to that information. They are not included in this public site or its generated indexes.

## Evidence and sources

A statement’s source and maturity determine how readers should use it.

- **Commitment**: A settled institutional or charter position. Charter language is quoted exactly.

- **Product direction**: An intended product or architecture. It does not establish that the capability is implemented or available.

- **Research hypothesis**: A claim or mechanism that still needs a defined experiment and evidence.

- **Implemented or available**: Implementation means the code path exists. Available means the behavior has also been confirmed on the named hosted path.

- **Measured result**: An empirical claim tied to a named dataset, protocol, metric, and report.

External papers, standards, vendor material, and competitor documentation are cited as external sources. They provide context or evidence for a specific claim. They do not become Mpalo policy or proof that Mpalo has implemented the same capability.

## Related pages

- [Mpalo overview](index.md)
- [Documentation map](map.md)
- [Current system](current-state.md)

## Authoritative integration reference

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