Expand description
Drift-incident management — semantic side.
Issue #562 phase 9: the AI-coupled pieces of mockforge_core::incidents moved
here. The structural incident manager (IncidentManager), in-memory store
(IncidentStore), and shared types (IncidentSeverity, IncidentStatus,
etc., which live in mockforge_foundation::incidents_types) stay in core /
foundation respectively — they don’t depend on AI primitives.
What’s here:
semantic_manager: tracks semantic drift incidents (cross-linked with structural incidents in core but built on top of the LLM-driven semantic-change taxonomy fromcrate::ai_contract_diff::semantic_analyzer).integrations: Jira / Linear / generic-webhook configuration types used to push incident notifications to external systems.slack_formatter(integrations/slack.rs) andjira_formatter(integrations/jira.rs): payload-formatting helpers for the two built-in integrations. Aliased under the same names as in the legacymockforge_core::incidentslayout so existing call sites that go through the core re-export shim resolve unchanged.
Re-exports§
pub use semantic_manager::SemanticIncident;pub use semantic_manager::SemanticIncidentManager;
Modules§
- integrations
- External system integrations for incidents
- jira_
formatter - Jira webhook formatter for drift incidents
- semantic_
manager - Semantic drift incident manager
- slack_
formatter - Slack webhook formatter for drift incidents