1
0

Architecture-as-Code 0.1.0: tikai dati un definīcijas; jomu katalogs (21 VARAM joma), JSON shēma, B09 datu līgums, pārbaudītājs

- kultūras un valodu tehnoloģiju joma → domains/kultura-valoda, avota PDF → sources/kultura-valoda
- izņemts KISC MCP servera kods, Docker un servera identitātes datnes (paliek KISC projekta repozitorijā)
- domenas.yaml, schemas/arhitektura-0.1.schema.json, contracts/B09-digitalas-parvaldes-arhitekturas.odcs.yaml, tools/validate.py

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_016679RwmHsuTFfxt26wP6rk
This commit is contained in:
2026-10-11 11:52:49 +00:00
parent 8fb6c52e44
commit 3574c8133f
95 changed files with 668 additions and 7880 deletions

View File

@@ -0,0 +1,20 @@
# Regeneration (kultura-valoda)
This repo is SSOT. The human-readable architecture document is regenerated from registers.
## Steps
1) Ensure registers are complete (non-empty):
- tools/qa/check_nonempty_registers.sh
2) Regenerate the document using the repo generator (see package scripts / build tooling).
- Output must be: KISC-merkarhitektura-apraksts.md
3) Run doc completeness checks:
- tools/qa/check_generated_doc_headings.sh KISC-merkarhitektura-apraksts.md
- tools/qa/check_stakeholder_count.sh KISC-merkarhitektura-apraksts.md
## Rule
If regeneration fails QA, fix the registers or generator template.
Do not delete or “simplify” registers to make QA pass.

View File

@@ -0,0 +1,53 @@
# TRACEABILITY — KISC Kultūras un valodu tehnoloģiju jomas mērķarhitektūra
This file maps the original human-readable source (PDF/presentation) sections to:
1) the SSOT registers in this repository, and
2) the regenerated machine-readable output (Markdown/PDF).
If any repo path in this table is missing or empty, the regenerated document is NOT considered equivalent.
---
## Sources
- Source A: "MērķARH_Kultura_Valoda_V02_18.06.2025.pdf"
- Source B: "ARH_kulturas_valodu_jomu_PREZENT_V0.4_4.06.pdf"
---
## Section mapping
| Source section | Meaning (what must be preserved) | SSOT repo path(s) | Regenerated doc heading |
|---|---|---|---|
| 1.1 Ievads | Purpose, context, why the document exists | `domains/kultura-valoda/registers/00-meta/intro.md` (or generator inline section) | `1.1 Ievads` |
| 1.2 Iesaistītās puses | Full list of institutions + roles | `domains/kultura-valoda/registers/03-organizations/organizations.yaml` + `domains/kultura-valoda/registers/00-meta/domain.yaml` | `1.2 Iesaistītās puses` |
| 1.3 Saīsinājumi | Abbreviation list | `domains/kultura-valoda/registers/00-meta/abbreviations.yaml` | `1.3 Saīsinājumi` |
| 1.4 Saistītie dokumenti | List of strategies/laws/platforms and relevance | `domains/kultura-valoda/registers/00-meta/related-documents.yaml` | `1.4 Saistītie dokumenti` |
| 2. Esošās situācijas raksturojums | Current state summary | `domains/kultura-valoda/registers/01-current-state/current-state.md` (or equivalent) | `2. Esošā situācija` |
| 3. Nākotnes redzējums | Target vision, objectives M1–M6 | `domains/kultura-valoda/registers/02-goals/goals.yaml` | `3. Nākotnes redzējums` |
| 4.1 Juridiskais skats | Legal/regulatory constraints grouped | `domains/kultura-valoda/registers/00-meta/legal-acts.yaml` | `4.1 Juridiskais skats` |
| 4.2 Biznesa skats | Functions, services | `domains/kultura-valoda/registers/04-functions/` + `domains/kultura-valoda/registers/05-services/` | `4.2 Biznesa skats` |
| 4.3 Semantiskais skats | Data/semantics principles, vocabularies | `domains/kultura-valoda/registers/06-information-resources/` + `domains/kultura-valoda/registers/00-meta/terms.yaml` | `4.3 Semantiskais skats` |
| 4.4.1 Lietojumprogrammu skats | Systems/applications | `domains/kultura-valoda/registers/07-systems/` | `4.4.1 Lietojumprogrammu skats` |
| 4.4.2 Integrācija | Integration approach + dependencies | `domains/kultura-valoda/registers/07-integrations/` (if exists) + `domains/kultura-valoda/registers/08-roadmap/interactions.yaml` | `4.4.2 Integrācija` |
| 4.4.3 IKT infrastruktūra | Infrastructure approach | `domains/kultura-valoda/registers/10-infrastructure/` (or equivalent) | `4.4.3 IKT infrastruktūra` |
| 5.1 Pasākumu plāns | Roadmap actions with owners/deps/outputs | `domains/kultura-valoda/registers/08-roadmap/roadmap.yaml` | `5.1 Pasākumu plāns` |
| 5.2 Mijiedarbība ar citām jomām | Cross-domain interactions | `domains/kultura-valoda/registers/08-roadmap/interactions.yaml` | `5.2 Mijiedarbība ar citām jomām` |
| 5.3 Riski | Risk register with mitigation | `domains/kultura-valoda/registers/09-risks/risks.yaml` | `5.3 Riski` |
---
## Acceptance criteria (no-loss)
A regeneration is considered equivalent if ALL conditions hold:
1. All SSOT files listed above exist.
2. Registers that are YAML contain non-empty `items:` lists.
3. The regenerated document includes all headings listed in the table.
4. The regenerated document includes stakeholder organizations beyond only KM/KISC/LNB.
5. The regenerated document includes roadmap + risks (non-empty).
If any condition fails, treat regeneration as NOT equivalent and fix the registers or generator template.
✅ This file is deliberately strict and “traditional”: it behaves like a proper controlled-document trace matrix.