Guides
Guides Overview
Practical guides for tagging, scanning, debugging, extending, speech, and enabling bounded fallback.
Need the shortest path?
Use Quick Start when you want the smallest working route → scan → graph → run flow first.
Something feels off?
Inspect scan output, graph state, active route/context, and dispatch in a practical order.
Need the full surface?
Browse all runtime methods, hooks, extension points, and lifecycle APIs.
Use the guides section when you already understand the product direction and want practical implementation help.
Recommended guide order
Tagging a Page
Mark a real UI with route, context, field, filter, action, and output semantics that help local resolution.
Scanning the App
Understand when to scan, how mutation observation behaves, and what the runtime discovered.
Debugging
Inspect scan output, graph state, route/context state, dispatch output, and fallback telemetry in a useful order.
Extension and advanced guides
Using Route Registry
Add explicit navigation and active-state behavior when anchors and path hints are not enough.
Using DOM Adapters
Handle custom controls and framework widgets when standard DOM execution does not fit.
Writing Custom Intents
Extend local resolution with explicit app-side matchers instead of hiding domain logic in the SDK core.
Injecting Runtime Context
Pass application state into local resolution and fallback in a deliberate, inspectable way.
Understanding Fallback Telemetry
Inspect fallback reasons, timeout/error classification, and usable vs unusable normalized results.
Tag-Only Integration Patterns
Prove the product promise on standard browser surfaces before reaching for bindings or adapters.
Other guides
Continue reading