Enterprise Core Operations

Konduo Enterprise Core overlays license control, HA, advanced audit, external authentication, the MCP gateway, anomaly analysis, relationship analysis, and compliance checks on top of Community Core. Shared resource and plugin contracts stay in CE; Enterprise-only behavior is connected through overlay and contribution points.

Main Responsibilities

1. Gate Enterprise feature availability through license status and entitlements.
2. Protect HA write paths through PostgreSQL-backed leader election and membership.
3. Expose MCP catalog, resource, and tool endpoints as read-oriented operator interfaces.
4. Connect anomaly rules, correlation analysis, relationship graphs, and log evidence to resource workflows.
5. Surface external auth providers, audit logs, API server logs, and compliance checks in Enterprise settings.

Operations Flow

• Check license and HA status before relying on Enterprise-only capabilities.
• Keep a local administrator account when registering external auth providers, and validate login gates separately from RBAC mapping.
• Restrict MCP through API key or OAuth scopes, and confirm resource/tool descriptors remain read-oriented.
• Link metric sources, log sources, and relation evidence so anomaly analysis has enough context.
• For releases, verify CE base version, EE patch suffix, manual image, and license bootstrap artifacts together.

Boundary

• Enterprise behavior belongs in enterprise/ overlays, patches, and contributions, not directly in CE.
• MCP descriptors, anomaly rules, HA, license, advanced security, and advanced analytics docs belong in EE sources.
• State-changing workflows must keep their RBAC, audit, and confirmation boundaries; MCP descriptors should not bypass them.

Related Documents

• enterprise/docs/manual-source-contract.md
• enterprise/docs/editions/plugin-boundary.md
• enterprise/docs/auth-provider-architecture.md
• enterprise/docs/instance-relations-contract.md
• enterprise/docs/runbooks/release-readiness-checklist.md