You've already forked dokumenta-semantiska-analize
Import UAPF package
dd69a04355
The 1.x package was a single ai.extract call wrapped in three BPMN
service tasks. No decision logic, no dmn cornerstone, no weights — the
risk/routing/validation algorithm lived invisibly in host code. There
was nothing for a runtime to actually execute.
2.0.0 makes it a real process:
- dmn cornerstone added with three decision tables:
* assess-personal-data-risk — PII regex signals -> risk level
* gdpr-processing-route — risk x centralisation -> CENTRAL/LOCAL,
anonymisation, redaction level
* human-validation-gate — confidence thresholds + PII re-scan
-> REJECTED/PENDING_REVIEW/APPROVED_AUTO
- BPMN expanded 3 -> 6 nodes (3 serviceTask + 3 businessRuleTask),
with horizontal DI.
- Task ids, mappings, docs, manifest (dmn:true), uapf.yaml, lifecycle
and eval-set updated; added a PII-bearing fixture.
Only the semantic extraction remains a model step. Risk classification,
GDPR routing and validation gating are now explicit ranked DMN rules —
inspectable, versioned, portable. Breaking change: structure + outputs.
47 lines
1.7 KiB
JSON
47 lines
1.7 KiB
JSON
{
|
|
"kind": "uapf.package",
|
|
"id": "dev.uapf.semantic-document-analysis",
|
|
"name": "Semantic Document Analysis",
|
|
"description": "Level-4 UAPF process for semantic analysis of free-text documents.\n\nThree BPMN service tasks invoke the UAPF-IP capabilities ai.redact@1,\nai.extract@1 and event.emit@1. Three DMN decision tables encode the\ndeterministic algorithm the host previously hid inside application\ncode: assess-personal-data-risk maps PII regex signals to a risk\nlevel; gdpr-processing-route selects CENTRAL vs LOCAL processing,\nanonymisation and redaction level; human-validation-gate applies the\nconfidence thresholds that decide REJECTED / PENDING_REVIEW /\nAPPROVED_AUTO.\n\nOnly the semantic extraction is a model step. Risk classification,\nGDPR routing and the validation gate are explicit ranked rules in\nversioned DMN \u2014 inspectable, auditable, portable. Extraction output\nvalidates against the VDVC v1.1 semantic-summary JSON Schema.\n",
|
|
"level": 4,
|
|
"version": "2.0.0",
|
|
"includes": [],
|
|
"dependencies": {},
|
|
"cornerstones": {
|
|
"bpmn": true,
|
|
"dmn": true,
|
|
"cmmn": false,
|
|
"resources": true
|
|
},
|
|
"paths": {
|
|
"bpmn": "bpmn",
|
|
"dmn": "dmn",
|
|
"cmmn": "cmmn",
|
|
"resources": "resources",
|
|
"metadata": "metadata"
|
|
},
|
|
"exposure": {
|
|
"mcp": {
|
|
"enabled": true,
|
|
"runnable": true,
|
|
"exposedEntrypoints": [
|
|
"Process_SemanticDocumentAnalysis"
|
|
],
|
|
"exposedArtifacts": [
|
|
"manifest",
|
|
"bpmn",
|
|
"dmn",
|
|
"docs"
|
|
]
|
|
}
|
|
},
|
|
"owners": [
|
|
{
|
|
"type": "team",
|
|
"id": "uapf-stewards",
|
|
"contact": "stewards@uapf.dev"
|
|
}
|
|
],
|
|
"lifecycle": "draft"
|
|
}
|