Core Developer: Key Questions
Reference: This page is a source-based technical synthesis of the LaTeX chapter cited below. For exact syntax, availability or ABI signatures, verify the versioned source, manifest and executable tests.
Scope and source boundary
Core-runtime decisions require evidence from versioned source interfaces, generated contracts and tests, not merely a diagram.
The Runtime documentation establishes an order of evidence: current grammar and public source/tests, versioned generated contracts, checked examples and only then integration patterns or architectural descriptions. An internal class or proposed design does not constitute a supported public API. This prevents a guide from promising capabilities beyond the tested release.
Engineering rules
- Label verified APIs separately from patterns and design proposals.
- Check symbols, signatures and examples against the selected version.
- Record platform, binding and ownership constraints.
- Do not infer licensing, availability or performance guarantees from architecture alone.
Chapter outline (original LaTeX headings)
- Status vocabulary
- Current validation matrix
LaTeX provenance
Primary chapter: Runtime/logiCells Runtime Programming with RadStudio/documentation-authority-and-runtime-status.tex.