Skip to content
CCinder
Roadmap

Reference

Roadmap

See the near-term direction for turning a validated semantic-runtime MVP into a stronger developer product.

Roadmap principle

Keep sharpening the semantic runtime path for websites you control before expanding outward into broader platform and distribution work.

The roadmap stays intentionally staged so the team can keep improving developer trust, local-first execution quality, and onboarding clarity.

Current state

The current SDK now proves:

  • semantic scan from tagged UI
  • scoped graph construction
  • active route/context awareness
  • graph-aware local resolution
  • tag-only DOM execution for common browser flows
  • tier 2: optional client-side embeddings for typo/paraphrase recovery (@usecinder/embeddings)
  • bounded tier-3 fallback with telemetry and normalization, hosted and metered through Cinder Relay
  • public extension points for routes, adapters, intents, context, events, speech, and the llm-core slot itself (setLlmCore)
  • a developer-run audit/integration CLI (@usecinder/cli) and an agent-fetchable onboarding entry point
  • focused red-team validation coverage, plus full public API coverage validation

Near-term priorities

Developer ergonomics

Keep improving docs, examples, debugging guidance, and first-run DX so new developers can integrate the SDK quickly and honestly.

Real-world app coverage

Prove the runtime on more structured real apps, especially where route/context duplication and custom controls show up in practice.

Extension-point maturity

Deepen route registry, DOM adapter, custom intent, and runtime-context patterns so advanced integrations stay explicit and maintainable.

Likely later directions

  • a production-grade ledger for Relay (integer micro-cents, not floating-point cents) and real verification of its Razorpay integration against a live account
  • an admin/analytics view beyond the current per-developer Relay dashboard
  • richer debug tooling and graph inspection UX
  • optional performance and loading improvements for the docs frontend

Continue reading