Patrick Bass Area: mobieusKnow (audit p6) · Surface: /know/{slug} · Dimension: competitor-gap · Severity: minor
Confluence (inline + page comments), Notion (comments and discussions), and Slab let readers comment on or ask questions about a specific article, turning the KB into a living document. For a community-built wiki this is especially valuable: members can flag inaccuracies, ask follow-ups, or suggest additions without having to file an edit through the moderation queue. mobieusKnow already has a mature forum/post system and notification plumbing to reuse; a lightweight per-article discussion (or a 'Discuss this page' link that opens a linked forum thread) would add the collaborative layer competitors treat as standard, with low new infrastructure.
Evidence
show.php renders article body, contributors, related pages, and TOC (show.php:200-286) but has no comment/discussion thread; there is no knowledge_comments table in schema.sql:3387-3487 and no comment handler in KnowledgeController.php. The only contributor-facing channel is the in-app notification a moderator triggers on approve/reject (KnowledgeController::notifyContributor, line 444-479), which is one-way and edit-scoped, not a discussion.Suggested fix. Add a per-article comment/discussion section on show.php (new knowledge_comments table or a linked forum thread per page), with moderator notification on new comments, reusing the existing markdown render + notification services.
Filed by the automated tenant-app audit and adversarially evidence-verified. Status: verified. Open — not yet actioned.
Patrick Bass
@mobieus
