You've already forked dokumenta-semantiska-analize
Import UAPF package
Rihards
59c87ee9a4
UAPF v2.4.0 reverses the v2.3.0 decision to place algorithm card references on resource targets. The card belongs on the BPMN task itself, where it is visible as a first-class process element and its inputs/outputs render as visible data objects on the diagram. Changes from v3.0.0: - bpmn/semantic-document-analysis.bpmn: each of 3 service tasks now carries xmlns:uapf24=https://uapf.dev/bpmn/v2.4 + the uapf24:algorithmCardRef attribute pointing at the governing card, plus a <bpmn:ioSpecification> synthesised from the card's io block so inputs/outputs render as visible data objects - resources/mappings.yaml: algorithm_card dropped from each of the 3 targets (they go back to being just dispatch endpoints) - uapf.yaml + manifest.json: version 3.0.0 -> 3.1.0 - README rewritten with v3.1.0 delta + audit-question table Cards themselves are unchanged. DMN files are unchanged.
79 lines
2.1 KiB
YAML
79 lines
2.1 KiB
YAML
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.
|
|
|
|
Three BPMN service tasks invoke the UAPF-IP capabilities ai.redact@1,
|
|
ai.extract@1 and event.emit@1. Three DMN decision tables encode the
|
|
deterministic algorithm the host previously hid inside application
|
|
code: assess-personal-data-risk maps PII regex signals to a risk
|
|
level; gdpr-processing-route selects CENTRAL vs LOCAL processing,
|
|
anonymisation and redaction level; human-validation-gate applies the
|
|
confidence thresholds that decide REJECTED / PENDING_REVIEW /
|
|
APPROVED_AUTO.
|
|
|
|
Only the semantic extraction is a model step. Risk classification,
|
|
GDPR routing and the validation gate are explicit ranked rules in
|
|
versioned DMN — inspectable, auditable, portable. Extraction output
|
|
validates against the VDVC v1.1 semantic-summary JSON Schema.
|
|
|
|
v3.1.0: aligned with UAPF v2.4.0 — Algorithm Card references move
|
|
from resource targets to the BPMN service tasks themselves (via
|
|
uapf24:algorithmCardRef attribute). Each card's io block is also
|
|
denormalised into a <bpmn:ioSpecification> on the task so inputs
|
|
and outputs render as visible data objects on the diagram. The
|
|
cards themselves and the DMN decisions are unchanged from v3.0.0.
|
|
|
|
level: 4
|
|
version: "3.1.0"
|
|
|
|
# ── UAPF-IP integration (capability needs + profile + guardrails) ──
|
|
requires_capabilities:
|
|
- ai.redact@1+
|
|
- ai.extract@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
|
|
cmmn: cmmn
|
|
resources: resources
|
|
metadata: metadata
|
|
algorithms: algorithms
|
|
|
|
algorithm_cards: true
|
|
|
|
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
|