QDG KB

QDG KB stores project knowledge as versioned Markdown in the Odin qdgwiki schema.

Boundary

• QDG KB owns the updatewiki skill, controlled database writes, schema, and version history.
• QDG KB Viewer owns read-only presentation and has no write operations.
• QWebHub owns shared routing, configuration, and the qdgwiki database alias.

Components

• A small Python MCP service used by Codex and Claude.
• The cross-compatible updatewiki skill.
• Three MySQL tables for projects, pages, and immutable page versions.
• A separate QDG KB Viewer Django module mounted by QWebHub at /knowledge-base/.

Development

Run locally over MCP stdio for development and testing. The same service supports streamable HTTP when packaged in a container.

AI-assisted documentation workflow

Developers leverage Codex or Claude to make editorial decisions?not merely append text.

For each updatewiki request, the AI reads the current page, new material, and relevant project evidence. It decides which durable facts are important, where they belong, what should be consolidated, and what transient detail should be omitted. The AI produces the complete revised Markdown page. QDG KB MCP then performs deterministic validation, optimistic-concurrency checking, and immutable version storage; it does not decide what the documentation should say.

This separation gives developers AI assistance for summarising and organising project knowledge while keeping database writes controlled, versioned, and recoverable.