Reference
Examples
Use these example integration shapes to decide where to start with a real Cinder rollout.
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.
Examples are most useful when they map directly to the runtime path you are trying to prove.
Recommended example order
Tag-only route + action flow
One route, one context, and one action. This is the best first proof for tag-only scan → graph → run.
Filter + result flow
Add filters and one output surface to validate local scoped matching and graph-aware execution.
Form + save flow
Use fields, submit behavior, and a save action to prove standard DOM execution before adding bindings.
Custom widget flow
Add a DOM adapter only after standard browser controls are already working cleanly.
Custom intent flow
Register an explicit matcher when app-specific local commands do not belong in the generic core planners.
Hybrid fallback flow
Enable the server only after the local-first path is already working on the real tagged surface.
Good first examples to build
1. Dashboard/reporting app
Use:
- one route
- one filters context
- one search action
- one output surface
2. CRUD form flow
Use:
- one route
- one form context
- fields
- one save action
- native submit behavior
3. Table/filter/result flow
Use:
- one route
- repeated data regions
- filters
- output or data surfaces
- active context awareness
4. Speech-enabled field entry flow
Use:
- text-first path proven already
listen({ autoRun: false })- transcript/error hooks
5. Hybrid local + fallback flow
Use:
- local-first path already working
- server health verified
- infer endpoint wired
- fallback telemetry observed
Example design rules
A good example should include:
- one real route
- one semantic context
- at least one action
- one output or data surface
- easy-to-inspect DOM structure
- no unnecessary fallback dependency in the first proof
Suggested reading path
Continue reading