SDK and Bootstrap
Bootstrap and SDK initialization are the runtime bridge between published project state and a live page. The bootstrap route returns runtime JavaScript, and the SDK creates the browser-side state that can load, refresh, and execute eligible tools.
Bootstrap route concept
The bootstrap route should be documented as a real runtime script, not as a static placeholder. Its job is to resolve the bases and assets needed for the project runtime, then load the supporting runtime code into the page.
This is the cleanest docs model because it explains why installation starts with a snippet but still results in a dynamic browser runtime.
SDK initialization concept
The SDK is the browser runtime entrypoint. It creates runtime state, registries, telemetry behavior, and exposed methods such as load, refresh, and execute.
Docs do not need to overdescribe every internal structure, but they should make clear that the SDK is where the runtime becomes active rather than being only a helper library.
Load and refresh behavior
- Initial load brings the active project pack into the runtime after bootstrap completes.
- Refresh behavior exists so the runtime can react when page context or route context changes.
- Docs should describe refresh as part of runtime maintenance, not as a promise that every page mutation instantly re-registers everything automatically.
How bootstrap affects runtime availability
Runtime availability depends on this chain staying intact: snippet installation, bootstrap delivery, SDK initialization, active-pack fetch, and eligibility-based registration.
That makes bootstrap and SDK a practical operations topic as well as a setup topic. When the runtime does not load, these are the first surfaces teams should inspect.