Community Core Operations

Konduo Community Core provides the shared operating layer for plugin-based resource registration, access control, audit records, alert workflows, metric linkage, dashboards, and diagnostics. Domain-specific behavior belongs to plugins; Core keeps registration, rendering, permissions, and lifecycle behavior consistent across those plugins.

Primary Responsibilities

1. Register and manage resource, metric source, and alert channel plugins.
2. Handle users, roles, resource permissions, and audit records through one common model.
3. Render resource dashboards, diagnostics, and alert-rule pages from host-rendered schemas.
4. Run plugin health checks, alert evaluation, and delivery sessions through shared workflows.
5. Connect resource-owned logical metrics to concrete metric source queries through mapping packs.

Operating Flow

• Review available resource plugins, metric sources, and alert channels in admin settings.
• Register resources with plugin-specific connection settings and metric linkage.
• Run connection tests and resource health checks after registration.
• Use dashboards and diagnostics together to review current state, historical risk, and metric coverage.
• Tune alert rules, routes, workflows, and delivery history per resource.

Boundaries

• Core owns shared lifecycle, permissions, audit, alert workflow, and UI hosting.
• Plugins own domain configuration schemas, diagnostic evidence, logical metrics, mapping packs, and management actions.
• Sensitive credentials are used only at the storage and execution boundary and must not be exposed in health or diagnostic payloads.
• Plugin-specific UI behavior should be exposed through schemas and contributions, not hard-coded into Core.

Related Documents

• docs/community-edition-boundary.md
• docs/plugin-extension-point-policy.md
• docs/frontend-plugin-ui-contract.md
• docs/plugin-diagnostics-contract.md
• docs/manual-source-contract.md