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.
14 lines
834 B
YAML
14 lines
834 B
YAML
kind: uapf.metadata.lifecycle
|
|
status: draft
|
|
created: "2026-05-15T20:30:00Z"
|
|
lastModified: "2026-05-17T00:00:00Z"
|
|
changeHistory:
|
|
- version: "1.0.0"
|
|
date: "2026-05-15"
|
|
summary: "Initial release. Three reserved-namespace capabilities; VDVC output schema."
|
|
author: "uapf-stewards"
|
|
- version: "2.0.0"
|
|
date: "2026-05-17"
|
|
summary: "Full rewrite into a real process. Added the dmn cornerstone with three decision tables (assess-personal-data-risk, gdpr-processing-route, human-validation-gate) carrying the risk, routing and validation-gating algorithm previously hidden in host code. BPMN expanded from 3 to 6 nodes. ai.redact now returns deterministic PII regex signals; ai.extract returns flat aiConfidenceScore and outputPiiErrorCount. Breaking: package structure and outputs changed."
|
|
author: "uapf-stewards"
|