Roadmap
What we're building, in priority order. Now / Next / Later. Updated continuously; reviewed at the start of every quarter.
What we’re building, in priority order. Updated continuously; reviewed at the start of every quarter.
Now / Next / Later
Section titled “Now / Next / Later”🔥 Now (in flight)
Section titled “🔥 Now (in flight)”| Initiative | Owner | Target | Status |
|---|---|---|---|
| Sidekick context resolution v2 (Intelligence Engine) | @aphaiboon | This sprint | 🔵 In progress |
| Apex model rollout (Flash, General, Reason) | @aphaiboon | Q2 | 🟡 Pre-launch |
| Brain folder dossier injection | @aphaiboon | This sprint | ✅ Shipped (2026-04) |
| Composio v3 sessions (feature-flagged) | @aphaiboon | This sprint | ✅ Shipped (2026-05-07) |
| Page Layout Wrappers consolidation | @aphaiboon | Done | ✅ Shipped (2026-03-16) |
| Apex stack standup (apex-core + lab-flash + lab-general) | @aphaiboon | Done | ✅ Shipped (2026-05-19) |
| Internal-docs site (internal-docs.cmmd.ai) | @aphaiboon | This sprint | 🔵 In progress (Confluence migration) |
⏭️ Next (next 30–60 days)
Section titled “⏭️ Next (next 30–60 days)”| Initiative | Why now |
|---|---|
| Public docs site (docs.cmmd.ai) | Astro Starlight, separate from Confluence — full plan ready |
| Workspace SSO | Enterprise unblock — see Security Posture |
| Mobile native app (iOS/Android) | Increase Sidekick reach beyond desktop |
| More Apex tiers | Code-specialist, Vision — see Model Card |
| Status page (status.cmmd.ai) | Trust signal + on-call infra — see On-call |
| Public API + OpenAPI docs | Power-user / integration use cases |
🌅 Later (90+ days)
Section titled “🌅 Later (90+ days)”| Initiative | Why later |
|---|---|
| Marketplace open developer SDK | Need Composio v3 stable first |
| Billing self-serve | Manual onboarding works at current scale |
| Multi-org for individuals | Pattern is multi-workspace, not multi-org |
| i18n / multi-language | English-only viable for ICP through year 2 |
| Enterprise admin / SCIM | Not yet revenue-blocking |
How we decide what’s next
Section titled “How we decide what’s next”Against The 30-Second Rule — does it make Connection / Clarity / Action faster or deeper? If not, deprioritize.
Against the Vision & Strategy principles — does it make CMMD calmer? Or noisier?
Against revenue / retention — does it unblock a paying or near-paying customer? Move it up.
What does NOT go on the roadmap
Section titled “What does NOT go on the roadmap”- Individual bugs (Jira)
- Refactors with no user-facing outcome (engineering work, not product) — track in Decision Log if load-bearing
- Internal tooling (engineering)
- Customer success or marketing initiatives
Related
Section titled “Related”- Vision & Strategy — the why behind the roadmap
- App Catalog — current state of every app
- Decision Log (ADRs) — load-bearing architectural decisions shaping the roadmap