Adds docs/methodology.md — the prose deliverable that ties the
vk-gramatvediba workspace together for the AI regulatory sandbox.
Describes the two-pass transcription pipeline (mechanical transcoder ->
curated refinement), the concrete delta between the transcoder skeletons
and the curated FG3-4/FG3-5 executables (gateways, DMN extraction, link
reconciliation, resource/metadata authoring), the final validation pass
(all .bpmn/.dmn well-formed, all 3 L4 packages pass uapf-cli, transcoder
samples byte-deterministic), and the implications and limitations for the
sandbox. Workspace now closes the 8-step build plan: skeleton, six FG L2
stubs, FG3 L2 + six FG3-x sub-process stubs, FG3-1/FG3-4/FG3-5 executables,
register-to-BPMN transcoder, methodology note.
Adds tools/register-transcoder — a Python tool that reads a published Valsts
Kase accounting-process register (.xlsx/.xlsm) and emits BPMN process
skeletons. For a given sub-process it produces one userTask per register
step, swimlanes from the RACI columns (placing each step in its Responsible
actor's lane), sequence flows reconstructed from the register's own
predecessor/successor step references, and synthesised start/end events per
entry and exit step. Output is an isExecutable=false skeleton — the
deterministic first pass of the transcription pipeline; refinement into a
Level 4 executable package is the human/AI-assisted second pass that produced
the curated FG3-1/FG3-4/FG3-5 packages. Includes a README and sample-output
skeletons emitted from the FG3 register for sub-processes 3.5.2 and 3.5.3.
Upgrades the FG3-5 sub-process from a composition stub to a Level 4 atomic
executable: BPMN process Process_KomandejumaNorekina (trip-request processing,
cancellation branch, expense-report submission and approval, VPC processing,
reconciliation and outcome handling across the Nodarbinatais/Iestade/VPC
lanes), DMN decision Decision_KomandejumaNorekins (FIRST hit policy,
advance-vs-expense reconciliation with carry-forward to a next approved trip),
resource roles/agents/mappings and policies metadata. Transcribed from the
Valsts Kase FG3 register section 3.5.3. Validates against the UAPF 2.2.0
schemas and the uapf-cli validator.
Upgrades the FG3-4 sub-process from a composition stub to a Level 4 atomic
executable: BPMN process Process_SaimnieciskaNorekina (advance request,
settlement submission/approval, VPC processing, reconciliation and outcome
handling across the Nodarbinatais/Iestade/VPC lanes), DMN decision
Decision_AvansaNorekins (FIRST hit policy, advance-vs-expense reconciliation),
resource roles/agents/mappings and policies metadata. Transcribed from the
Valsts Kase FG3 register sections 3.5.2 and 3.5.4. Validates against the
UAPF 2.2.0 schemas and the uapf-cli validator.
Adds the six FG3 sub-process packages (processes/fg3-1 .. fg3-6) and wires
them into the FG3 (L2) package via `includes`; FG3 version 0.1.0 -> 0.2.0.
FG3-1 (Rēķina/kredītrēķina saņemšana par precēm/pakalpojumiem) is built out
as an executable L4 package:
- bpmn/rekina-sanemsana.bpmn - 3-lane process (Nodarbinātais / VPC / Iestāde)
- dmn/rekina-parbaude.dmn - FIRST hit-policy routing decision table
- resources/ - roles, agent and mappings binding every user
task and the decision to a target
- metadata/ - ownership, lifecycle, policies
FG3-2..FG3-6 are draft composition placeholders (L4) pending executable
build-out.
Validated against the UAPF 2.2.0 schemas (manifest, ownership, lifecycle,
policies, resource-mapping, enterprise index): all includes resolve, no
duplicated executable artifacts, BPMN/DMN well-formed, and all resource
mapping references resolve to real BPMN/DMN element ids.
Step 2 of the vk-gramatvediba build (absorbs the planned Step 3 — the
enterprise index now references the domain, since the two are one
coherent unit).
- domains/gramatvediba/ — L1 domain package; includes the six FG packages
- processes/fg1..fg6/ — six L2 function-group packages (composition stubs;
FG3 carries its sub-process inventory and is taken to executable depth
in later steps)
- each package: uapf.yaml + metadata/ownership.yaml + metadata/lifecycle.yaml
+ README
- enterprise/enterprise.yaml now references the L1 domain
All 22 manifests and metadata files validate against the UAPF 2.2.0
schemas; all seven includes / enterprise references resolve.
