What is authoritative, and what is available?
Documentation status: guide — consult the documentation maturity policy before interpreting this page as a release guarantee.
Order of evidence
When a book example and a running release disagree, the LaTeX guide gives the following precedence:
- The current registered declarative grammar, public source interfaces and executable tests.
- Generated contracts, especially ABI manifests and bindings for the selected version.
- Source-checked examples and source maps from the Runtime book.
- Integration patterns and architectural synthesis.
- Historical examples and notes.
An internal Kernel class may exist without being a public API. Likewise, a declared ABI value kind need not be accepted by every marshaling bridge.
Status labels
| Label | How to read it |
|---|---|
| Verified API | A specific symbol/path checked against the source (and tests where stated) for the documented version |
| Available | A shipped capability, not necessarily certified identically across all platforms |
| Integration pattern | Composition requiring adaptation to runtime, binding and deployment |
| Source boundary | Internal mechanism, not a complete supported application API |
| Design / planned | Not a delivered behavior or deployment promise |
Platform and binding distinctions
The source guide describes Windows, Linux and macOS Runtime availability and container deployment, but explicitly warns against equating that with every native loader being portable. At the recorded source boundary, ABINativeModule loads DLLs using Windows dynamic-library APIs. Python and C# ABI bindings are mentioned as supported surfaces; exact generation, ownership and argument directions remain governed by the versioned artifacts. The current public ABI reference documents the exercised subset and its limits.
Before publishing a new claim
Check the target build, tests, exact manifest and platform matrix; separate verified execution from architecture. Avoid unsupported benchmark figures and never infer license rights from a technical capability page.
LaTeX source: documentation-authority-and-runtime-status.tex; companion: programming-example-verification-and-source-contract.tex.