CodeNexus product

AIDOCS helps teams work with documentation, memory, and MCP-powered runtime flows.

AutoDeployBase remains the main application accelerator. AIDOCS complements it with documentation-aware memory, routing, MCP runtime behavior, and `/aidocs`-driven workflows.

Docs, memory, and routing as one system

AIDOCS is designed to connect durable memory, session context, and deterministic prompt routing instead of treating them as separate tooling layers.

MCP-first runtime behavior

AIDOCS prefers MCP orchestration, explicit entry flows, and runtime-aware tooling over vague prompt-only conventions.

CLI and host integrations

AIDOCS includes a CLI surface and host-aware behavior for Claude and OpenCode, with docs that should explain the differences clearly.

Multilingual action tokens

The product direction already includes multilingual action-token handling and language-pack visibility, which should be documented as first-class operator behavior.

What belongs in AIDOCS docs

Install and configuration

`/aidocs` entry flow and managed mode

Memory and session model

CLI reference

Claude vs OpenCode host integration differences

MCP/runtime architecture and routing behavior

Packaging, release, and public/private boundary guidance

Product boundary

AIDOCS is positioned as a separate CodeNexus product that integrates with AutoDeployBase, rather than as a subsection of the main app.