kind: uapf.package id: lv.itsm.incident.triage name: LVRTC Incident Triage description: | Level-4 UAPF process for triaging IT-infrastructure incidents at LVRTC. Six BPMN service tasks invoke the UAPF-IP capabilities intake.normalize@1, ai.classify@1, ai.suggest_priority@1, ai.draft_response@1, incident.update@1 and event.emit@1. Three DMN decision tables encode the deterministic rules previously hidden inside the host: priority maps severity x service-tier x AI-suggestion x classification onto P1-P4; ownership decides whether the case stays inside LVRTC or hands off to an external partner; routing picks the expert group (helpdesk-l1, noc-l1/l2, soc-l2, facility-l2, platform-l2, external-handoff). Classification, priority suggestion and customer response drafting are AI steps; the rules that decide *what* the AI proposes versus *who* handles it live in versioned DMN, not Python. Drafted customer responses are produced in both Latvian and English and require human approval before sending (governed by Algorithm Card algo.incident_triage.draft_response). v1.0.0 targets UAPF v2.5.0: algorithm cards carry embedded `tests` arrays (>=2 per card) per chapter 13.16; BPMN service tasks carry uapf24:algorithmCardRef attributes; resource targets are dispatch endpoints only. level: 4 version: "1.0.0" requires_capabilities: - intake.normalize@1+ - ai.classify@1+ - ai.suggest_priority@1+ - ai.draft_response@1+ - dmn.evaluate@1+ - incident.update@1+ - event.emit@1+ profiles_supported: - uapf-ip-orchestrated guardrails: resources/guardrails.yaml includes: [] dependencies: {} cornerstones: bpmn: true dmn: true cmmn: false resources: true paths: bpmn: bpmn dmn: dmn resources: resources metadata: metadata exposure: mcp: enabled: true runnable: true exposedEntrypoints: - "Process_IncidentTriage" exposedArtifacts: - manifest - bpmn - dmn - docs owners: - type: team id: lvrtc contact: incident-mgmt@lvrtc.lv - type: team id: openitsm-stewards contact: stewards@openitsm.algomation.io lifecycle: draft