5 Commits

Author	SHA1	Message	Date
Rihards	59c87ee9a4	feat(3.1.0): align with UAPF v2.4.0 — algorithm card refs move to BPMN task ... 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.	2026-05-20 14:23:16 +00:00
UAPF Steward	dd69a04355	rewrite 2.0.0: real process — extract the algorithm into DMN ... 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.	2026-05-17 20:00:36 +00:00
Rihards	3f1d62c748	Add diagram interchange (DI) to cornerstone BPMN ... UAPF-specification v2.1.0 makes cornerstone diagram interchange mandatory (SEM-011). This file was hand-authored as logic only. Adds the bpmndi/dc/di namespaces and a complete BPMNDiagram (5 shapes, 4 edges, deterministic linear layout). The <bpmn:process> logic is byte-identical.	2026-05-17 12:52:44 +00:00
Rihards	dbcff8bedc	Adopt UAPF v2.0.0 cornerstone naming: .bpmn.xml/.dmn.xml -> .bpmn/.dmn ... UAPF-specification v2.0.0 mandates OMG-standard cornerstone extensions. Renamed cornerstone files and updated references in README / docs / processgit.mcp.yaml. Content of the BPMN/DMN files is unchanged.	2026-05-17 08:04:36 +00:00
Rihards	ae0c646021	v1.0.0: dev.uapf.semantic-document-analysis ... UAPF v1.1 SSOT-conformant Level 4 process package — reusable semantic document analysis, shareable across DMS / intake / mailroom systems. Structure: - uapf.yaml (kind: uapf.package, level 4) + manifest.json engine-compat - bpmn/semantic-document-analysis.bpmn.xml — 3 service tasks invoking reserved UAPF-IP capabilities ai.redact@1, ai.extract@1, event.emit@1 - resources/mappings.yaml — task->target bindings with I/O contracts - resources/schemas/vdvc-semantic-summary.schema.json — output contract - resources/guardrails.yaml — GDPR + EU AI Act constraints - metadata/ownership.yaml + metadata/lifecycle.yaml - docs/, fixtures/, tests/eval-set.json Validates clean against UAPFormat/UAPF-specification schemas.	2026-05-16 09:32:55 +00:00