dokumenta-semantiska-analize

AI_Sandbox/dokumenta-semantiska-analize

MCP Server

Active

Fork 0

Commit Graph

Author	SHA1	Message	Date
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

Author

SHA1

Message

Date

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

3 Commits