Guides
Tag-Only Integration Patterns
Prove the product promise on standard browser surfaces before reaching for bindings, adapters, or custom matchers.
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.
Tag-only integration is the best first proof for the SDK.
Start with standard browser behavior
Good tag-only targets include:
- anchors and path-based route activation
- native inputs and selects
- normal buttons
- standard forms
- outputs that can be focused or revealed
Good first commands
open reportssearchshow priceset crop to soybeansave changes
Add complexity only when needed
Reach for extensions only after the standard path is proven:
- tags first
- inspect scan and graph
- prove local run/dispatch
- only then add bindings, route registry, adapters, or custom matchers
Why this order matters
It keeps the product promise honest and prevents app-specific code from masking weak semantic structure.
Related pages
Continue reading
Previous: Understanding Fallback Telemetry
Inspect fallback reasons, timeout/error classification, and usable vs unusable normalized results.
Next: Auditing and Enrichment Tools
Three developer-run tools - auditUntaggedElements, auditLabelQuality, and exportGraphForEnrichment - for finding tagging gaps and improving graph labels offline, never at runtime.