Rihards Gailums
66ce42ea37
Three corrections grounded in the UAPF SSOT specification (UAPFormat/ UAPF-specification, specification/01-concepts.md, 04-folder-structure.md, 05-level-composition.md, 10-conformance-checklist.md), which had not been read in full before the initial workspace build. 1. Level relabel. The FG3 sub-process stubs fg3-2, fg3-3 and fg3-6 had been marked level: 4 by template inheritance from fg3-1 at Step 4 of the build, despite carrying no BPMN and no resources. Per the spec conformance checklist this fails the L4 requirement. The three are composition placeholders, which the spec models as L3 (composed subprocess / variant). Their uapf.yaml is now level: 3 with cornerstones.bpmn: false — conformant: L1-L3 packages MUST NOT duplicate L4 content. The three real executables fg3-1, fg3-4 and fg3-5 remain L4. 2. BPMN Diagram Interchange. All five .bpmn files in the workspace now carry a bpmndi:BPMNDiagram with BPMNShape and BPMNEdge elements produced by a swim-lane left-to-right auto-layout, so the diagrams preview in bpmn.io, Camunda Modeler and ProcessGit's web view. The spec doesn't require DI (its own examples have none) but practical reviewability does. 3. Transcoder. tools/register-transcoder gains bpmn_di.py — also runnable standalone for retrofitting existing BPMN files. transcode.py now imports it and emits DI by default for newly generated skeletons. sample-output/3.5.2.skeleton.bpmn and 3.5.3.skeleton.bpmn regenerated with DI; the logical-model content is byte-identical to the previous commit, only DI is added. docs/methodology.md updated: adds an explicit Workspace-structure section grounding L0-L4 in the SSOT spec, a Conformance-correction section documenting the Step-4 mislabel and its fix, and drops the now-untrue 'no DI' line from limitations. Validation after the change, full L1-L4 sweep: uapf-cli validate green on all 10 packages (domains/gramatvediba, fg1-fg6, fg3, fg3-1..fg3-6); xmllint clean on all 8 .bpmn/.dmn; every .bpmn has BPMNDiagram present.
vk-gramatvediba
UAPF workspace for the Valsts Kase / Vienotais pakalpojumu centrs (VPC) accounting processes — a transcription of the six published accounting function groups (FG1–FG6) into the Unified Algorithmic Process Format.
Built for the Latvian AI regulatory sandbox proof-of-concept. It demonstrates algorithmising a real, published public-sector process description as version-controlled, machine-executable, auditable UAPF packages.
Conformance
This workspace targets UAPF specification v2.2.0
(https://github.com/UAPFormat/UAPF-specification). It follows the normative
folder structure (enterprise/, domains/, processes/), the package layout
(uapf.yaml plus cornerstone folders), and the includes-based composition
rule — higher levels reference lower levels and executable artifacts are never
copied.
Layout
| Path | Level | Contents |
|---|---|---|
enterprise/enterprise.yaml |
L0 | Enterprise index — references every domain and package |
domains/ |
L1 | Domain compositions (the accounting domain) |
processes/ |
L2–L4 | Function-group, sub-process and atomic executable packages |
tools/ |
— | Workspace tooling (package archive build, transcription) |
docs/ |
— | Conventions and proof-of-concept documentation |
See docs/conventions.md for how the VK function groups map onto UAPF levels.
Source material
The packages here are transcribed from the Valsts Kase publication Grāmatvedības uzskaites procesu apraksts (created 2024-06-03, updated 2026-03-27): six process schemas and six process registers. The transcription preserves step identity, responsibility (RACI), the systems used, and SLAs; it does not alter the documented process. Where a schema and its register disagree, the discrepancy is recorded rather than silently resolved.
Status
FG3 build. The workspace structure, the L0 enterprise index, the L1 accounting domain and the six L2 function-group packages are in place. FG3 is composed down to its six L4 sub-process packages, and FG3-1 (Rēķina/ kredītrēķina saņemšana) is built out as an executable L4 package with BPMN and DMN. FG2 and FG4–FG6 detailing and the FG3-2…FG3-6 executable builds follow in subsequent steps.
Scope note
This proof-of-concept validates methodology and auditability — that a public-sector process can be expressed as conformant, executable, traceable UAPF, and run with a complete audit chain. Accounting bookkeeping is not, in itself, a high-risk AI use case under the EU AI Act; the sandbox value is the algorithmisation and audit method, not the domain.