Interoperability Plane
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
The interoperability plane depends on an explicit ABI, native modules and versioned external bindings.
Interop connects native code, generated bindings, ABI modules and external systems at explicit boundaries. The source distinguishes internal implementation interfaces from public ABI entry points and warns that loader/platform details may not be portable. Argument shapes, marshaling, ownership and compatibility belong to the published contract.
Engineering rules
- Keep internal class names out of public compatibility guarantees.
- Generate clients against the actual ABI manifest and version.
- Define who allocates, retains and releases values and handles.
- Test the exact loader, platform and extension deployment path.
Chapter outline (original LaTeX headings)
- Why This Layer Matters
- The Public Contracts and Kernel Implementations
- Load the ABI Manifest First
- Load and Register a Native Module
- Build the Executor and FPL Bridge
- Compile Source into an ABI Invocation
LaTeX provenance
Primary chapter: Runtime/logiCells Runtime Programming with RadStudio/native-abi-and-fpl-native-modules.tex.