SDK Engine: extension without extra authority
Historical SDK Engine implementation exists, including dispatcher and adapter artifacts. Current full Enterprise integration and support are not established. It is not a mandatory dependency of the reviewed core Work path; optionality is a separate question from integration.
Technical Whitepaper · English Edition · September 2026 · Figure 20
Open the full-resolution image to zoom; use your browser’s Back button to return. The complete plate is preserved; the explanation below remains readable without zooming.
Read the guide
A reading guide to the figure and its scope, not a claim of current implementation for every depicted concept.
Developer and partner environment
The diagram begins with applications, data, development tools, existing libraries, enterprise systems and documentation. These are possible integration inputs rather than a supported-language or connector matrix.
Implementation, integration and dependency
Historical code is evidence of implementation, not proof of current Enterprise integration. The current GUI contract defers the full SDK Engine. The supported Rust integration API is a separate surface. No live SDK edge to GAPE, Helper, Headless or Packr Engine is inferred, and no mandatory core dependency is invented.
Enablement layer
Libraries and interfaces, patterns, testing utilities, examples, version compatibility and reusable components are distinct concerns. The reference architecture does not announce that every item is packaged or released.
Extension categories
Custom integrations, applications, workflow extensions, domain extensions, partner solutions and reusable modules describe potential uses. Extension capability never transfers execution authority.
Discover · develop · validate
Review declared interfaces and documentation, identify the use case, then implement and test within supported requirements. Compatibility needs evidence, not just successful compilation.
Integrate · prepare · evolve
Connect through declared interfaces, document configuration, verify the compatibility matrix and prepare a governed handoff. Later changes require compatibility and scope review again.
About this reference
Full composition from Figure 20 of the September 2026 English technical whitepaper. The full-resolution WebP preserves the source figure pixel-for-pixel; thumbnails are reduced previews only.
The whitepaper distinguishes bounded roles, conceptual architecture and future concepts. This reference does not establish release authorization, certification, legal approval or customer production outcomes.