Enterprise IT Architecture
Engineering Guide: Extending WeKnora via MCP & Isolated Control Planes Without Forking Core
How to deliver upgrade-safe enterprise AI knowledge systems by combining non-invasive MCP plugins, role-isolated resource publishing, and an independent commercial control plane.
Disclosure: Derived directly from verified deployment and rollback engineering practices in our baseline stack.
Business Challenge
Hard-forking open-source core schemas for commercial billing or custom workflows blocks upstream security patches and risks cross-contaminating community and tenant data.
Architecture & Components
- Independent Commercial Control Plane (organization-to-instance mapping & audit trail)
- Resource Hub anonymous read-only REST/MCP + role-isolated Publisher MCP
- Isolated Harness workers querying WeKnora via read-only plugin
Implementation Workflow
- Strict database role separation across public read, staged publishing, and commercial CRM.
- Zero-downtime independent container rollbacks via Caddy upstream switching.
- Mandatory human-in-the-loop gates for external writes and file automation.