CMMD Internal Docs

Internal reference

Start with the question. Move to the source.

CMMD’s private knowledge base is organized around the work: product truth, operating paths, decisions, failure memory, and team context.

149internal pages47fix memos5runbooks

⌘Search across internal knowledgeRunbooks, decisions, app specs, fix memos, policy, and team context.⌘ K

I need to

01Get orientedStart Here, glossary, docs operating model, and wiki rules.02Respond to productionRunbooks for CI, incidents, database deploys, releases, and browser rollout.03Understand a failureFix memos across auth, migrations, realtime, APIs, and app behavior.04Find a product surfaceApp catalog, ownership boundaries, product scope, and active surfaces.

Product systems

AppsCatalog and surface ownershipForgeIDE roadmap, egress, flowsApexLocal LLM architecture and decisions

Operating memory

ADRsArchitecture decisions and rationaleFix memosKnown failures and preventionStandardsNon-negotiable engineering rules

Company context

StrategyVision, roadmap, product principlesGTMMessaging, sales, launch, successPeople & opsRoles, hiring, onboarding, policy

Boundary

Public docs explain. Internal docs decide.

Keep release-safe concepts in public docs. Keep failure analysis, roadmap nuance, operating policy, and internal product truth here.

Review boundary