App Catalog

Every app inside CMMD has a durable reference page here.

The apps

App	What it does	Status	Sidekick-accessible?
Sidekick	Conversational AI: modes, tools, threads, context	GA	(is the AI)
Brain	Documents, memory, core knowledge	GA	Read + write
Comms	Channels, threads, email — unified inbox	GA	Read + write
Calendar	Events, scheduling, recurring routines	GA	Read + write
Tasks	Task list + Top Tasks daily routine	GA	Read + write
Projects	Multi-week containers for threads + tasks + docs	GA	Read + write
Strategy & Goals	OKRs, scorecards, weekly check-ins	GA	Read
CRM	Contacts, companies, deal pipeline	GA	Read + write
Accounting	Invoices, P&L, expense categories	Beta	Read
Marketplace	App toggles + integration installs	GA	—
Feedback	Bug/feedback intake	GA	Write
Dashboard	The home view + Sidekick section	GA	—
Settings	Per-user + per-workspace config	GA	(limited write)
Forge IDE	Dev environment sub-product	Alpha	(sub-product)

14 apps, all documented. Every page follows the same shape — what/why, surface, data model, Sidekick integration, analytics events.

How an app gets here

Every CMMD app should have one page in this catalog. The page covers:

1. One-paragraph what & why
2. User-facing surface — screens, key actions, what success looks like
3. Data model — at a high level (tables, relationships)
4. Sidekick integration — what context the app feeds; what tools Sidekick can call
5. Analytics events — what we measure
6. Owned by — engineer + PM
7. Status — GA / Beta / Alpha / Deprecated

Sidekick integration check

Every new feature must be Sidekick-accessible. Three questions before merging:

1. Can Sidekick see this? (Context provider exists in server/services/sidekick/providers/)
2. Can Sidekick create / modify this? (Tool handler in server/services/sidekick/tool-handlers/)
3. Do the labels exist? (TOOL_LABELS, EXECUTING_LABELS, TOOL_PHASE_LABELS, SUMMARY_LABELS, STEP_LABELS, TOOL_ICONS)

If not, file the work as part of the feature — not “we’ll add it later.”