You've already forked dokumenta-semantiska-analize
Import UAPF package
Rihards
9b3790c1fa
Per UAPF v2.5.0, tests move from sidecar files (tests/algorithms/<card-id>.test.yaml — removed in v2.5.0) into a top-level tests array on each algorithm card. Minimum two entries per card; the Algorithm Card viewer (UAPF chapter 13.16, ProcessGit Preview tab) consumes these as its primary interaction surface. This package's three cards now carry embedded tests: - algo.semantic_document_analysis.pii_redactor (deterministic redactor) — 3 cases: Latvian personas kods inline (positive — three entity types detected), plain administrative text (negative — no PII signals), financial figures with IBAN (mixed — financial yes, personas_kods no). - algo.semantic_document_analysis.vdvc_semantic_extractor (stochastic LLM extractor, EU AI Act high-risk + mandatory oversight) — 2 cases: regulatory construction-permit appeal (in-domain, expected topic + applicable_regulations), non-regulatory thank-you note (out-of-domain, low confidence). Both carry ai_confidence_score tolerance bands appropriate for a stochastic output. - algo.semantic_document_analysis.completion_event_emitter (deterministic CloudEvents emitter) — 2 cases: successful completion event, failure completion event. The emitter does not gate on payload contents, so both succeed. Other changes: - uapf.yaml + manifest.json: version 3.1.0 -> 3.2.0 - README.md: v3.2.0 section added describing embedded tests and the removed sidecar location BPMN file unchanged from v3.1.0 — uapf:algorithmCardRef on each service task per UAPF v2.4.0 + ioSpecification synthesis. Mappings unchanged. DMN tables unchanged. uapf-cli validate against v2.5.0 schemas passes cleanly.
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.2.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
|