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.
FG3-1 — Rēķina/kredītrēķina saņemšana par precēm/pakalpojumiem
Level 4 atomic executable process for the receipt and processing of supplier invoices and credit invoices for goods and services — the FG3 demonstrator taken to executable depth.
- UAPF level: L4 (atomic executable)
- Package id:
vk.gramatvediba.fg3-1 - Included by:
processes/fg3(function group FG3). - Source: Valsts Kase Grāmatvedības uzskaites procesu apraksts — FG3 schema and process register.
Process
bpmn/rekina-sanemsana.bpmn (Process_RekinaSanemsana) transcribes the
invoice-receipt flow across three lanes mapped from the source RACI columns:
- Nodarbinātais — invoice arrives (e-invoice via e-address, or paper).
- VPC — registration in the DVS, formal checking, contract/PO matching, routing, posting and payment-order preparation; manual review where needed.
- Iestāde — substantive approval by the responsible officer.
Flow: register in DVS → formal check → match to contract/PO → routing decision → substantive approval → post → prepare payment order. Two terminating outcomes: posted and queued for payment, or returned to the supplier.
Decision
dmn/rekina-parbaude.dmn (Decision_RekinaMarsrutesana) is a FIRST
hit-policy decision table that sets the routing variable marsruts from three
inputs:
| Input | Values |
|---|---|
formalaParbaude |
atbilst, neatbilst |
ligumaSasaiste |
pilna, dalena, nav |
dokumentaTips |
rekins, kreditrekins |
Outcomes: return (failed formal check), manual-review (no/partial contract
match, or any credit invoice), process (formally valid, full match, plain
invoice). The Task_NoteiktMarsrutu business-rule task evaluates it.
Resources
resources/mappings.yaml binds every BPMN user task and the DMN decision to a
target in resources/roles.yaml / resources/agents.yaml. Human steps are
manual; the AI agent agent.rekinu-asistents is bound assisted to the
formal check, contract matching and the routing decision — it suggests, the
accountant decides. No step is autonomous.
Transcription note
The process structure, lanes, systems and SLAs are transcribed from the
published FG3-1 schema and register. Step identifiers here use stable BPMN/DMN
element ids; reconciliation of these against the source register's process nr. numbering is a tracked follow-up and any schema/register discrepancy is
to be recorded rather than silently resolved (see docs/conventions.md).
Status
Draft. The package is structurally complete and validates against the UAPF
2.2.0 schemas; lifecycle status advances to review once the source-numbering
reconciliation is signed off.