1
0

a UAPF manifest (uapf.yaml) is required in the repository

Rihards Gailums 87bab46b0f Workspace INDEX.md + flag §07 DI non-conformance
Two changes:

1. INDEX.md (new, generated). Workspace-level index that lists every
   package grouped by UAPF level (L0/L1/L2/L3/L4) for navigation. Per
   UAPF specification §01-concepts.md, levels are an aggregation and
   governance scope only and MUST NOT be used to imply modeling
   semantics; per §04-folder-structure.md the SHOULD-recommended
   on-disk layout is enterprise/ + domains/ + processes/ regardless of
   level. INDEX.md is therefore a level-grouped *view* over the
   spec-conformant on-disk layout, not an alternative layout. Generated
   by tools/build-index/build_index.py (new), which walks the workspace
   manifests and emits INDEX.md from current state.

2. docs/methodology.md updated to document the §07 auto-layout DI as a
   known deliberate non-conformance. §07-package-format.md requires
   authored DI (from a conforming OMG modeler) and explicitly forbids
   automatic layout generation as a substitute. The DI in the five
   .bpmn files in this workspace is auto-generated by
   tools/register-transcoder/bpmn_di.py and is therefore non-conformant
   under §07. It is kept for the POC so artefacts preview visually;
   the conformant path is to re-author each .bpmn in Camunda Modeler
   or bpmn-js Studio and recommit, which emits authored DI. New
   *Known non-conformances* section in methodology.md cites §07
   verbatim and explains this rationale. The Pass-1 transcoder section
   and Final-validation-pass section are softened to call out that
   the DI is auto-generated.

uapf-cli validate green on all 13 packages (L1 domains/gramatvediba,
L2 fg1-fg6, L3 fg3-2/3/6, L4 fg3-1/4/5).
2026-05-21 11:12:45 +00:00

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.

Description
No description provided
Readme 142 KiB
Languages
Python 100%