Benjamin Admin
ecae5bc7f1
Before the next Journey: the LANGUAGE. With 5 knowledge objects but no vocabulary, the same reise gets named four different ways (ISO9001->MaschinenVO vs Quality Management->Product Safety vs ...). The spec answers ONE question: which terms are IDENTITIES and which are REPRESENTATIONS of the same meaning? - spec docs-src/architecture/domain-vocabulary-spec-v1.md (PROPOSAL): identity hierarchy (Requirement RQ / Capability MCAP [Registry 2C] / regulation-source-target / Journey Class MJRN [PROVISIONAL] / Journey instance / Playbook MPLB); canonical name + aliases; capability vocabulary = the Capability Registry (not rebuilt); reorder Vocabulary -> Transition #2 -> #3 -> Rule of Three. - knowledge/vocabulary/regulations.yaml: regulation/standard IDENTITIES (id + canonical + aliases). SOLVES the regulation-ID normalization the KPIs flagged: CRA == "Cyber Resilience Act" == "Regulation (EU) 2024/2847" all resolve to `cra`; ISO9001/QMS -> iso9001; etc. Shared artifact (@Legal-KG/@Execution please adopt). - knowledge/vocabulary/journey_classes.yaml (PROVISIONAL): clusters our transitions into classes (Information Security -> Product Cybersecurity; Quality Management -> Product Compliance/Safety). Finding: ISO9001->MaschinenVO is an INSTANCE of an existing class (like ISO9001->CRA, ISO13485->MDR), not a new kind -> avoids duplication. Journey Class is a new abstraction -> its own Rule of Three (no MJRN minting yet). - reference suite: both KPIs now read aliases from regulations.yaml instead of hard-coded maps; the "Regelwerk-ID-Normalisierung" line flips TODO -> PASS. KPI numbers unchanged (vocab is a superset). - Side effect = Requirements Intelligence: a Tender "Security Patch Procedure" resolves to MCAP-0017. 7 vocabulary tests (17 with domain programs), check-loc 0. Knowledge data + spec + reference harness = non-runtime -> no deploy (ADR-001). No new module, no runtime change, no minting (Freeze). Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>
31 lines
1.6 KiB
YAML
31 lines
1.6 KiB
YAML
# Domain Vocabulary — Journey CLASSES (PROVISIONAL). A class clusters journey instances that are
|
|
# "the same reise". So we do NOT write a new journey for every certification when many share a class.
|
|
# PROVISIONAL: Journey Class is a NEW abstraction -> its OWN Rule of Three (>= 3 instances per class
|
|
# before minting MJRN ids). Endpoints reference regulation vocabulary ids (see regulations.yaml).
|
|
|
|
id: VOCAB-journey-classes-v1
|
|
status: provisional
|
|
classes:
|
|
- id: infosec-to-product-cyber # provisional id, NOT a minted MJRN
|
|
name: "Information Security → Product Cybersecurity"
|
|
from_kind: information_security
|
|
to_kind: product_cybersecurity
|
|
instances:
|
|
- {from: iso27001, to: cra} # ✅ modelled (TP-ISO27001-CRA-v1)
|
|
- {from: tisax, to: cra} # ⏳ Rule-of-Three transition #3
|
|
- {from: iec62443, to: cra} # ⏳
|
|
|
|
- id: qm-to-product-compliance
|
|
name: "Quality Management → Product Compliance/Safety"
|
|
from_kind: quality_management
|
|
to_kind: product_compliance_safety
|
|
instances:
|
|
- {from: iso9001, to: cra} # ✅ modelled (TP-ISO9001-CRA-v1)
|
|
- {from: iso9001, to: maschinenvo} # ⏳ Rule-of-Three transition #2 — INSTANCE of this class, not a new kind
|
|
- {from: iso13485, to: mdr} # same CLASS, different domain (medical) — proves the class generalises
|
|
|
|
note: >
|
|
Befund: ISO9001→MaschinenVO ist KEINE neue Journey-Art, sondern eine INSTANZ der Klasse
|
|
„Quality Management → Product Compliance/Safety" (wie ISO9001→CRA, ISO13485→MDR). Das ist genau die
|
|
Duplikation, die das Vokabular verhindert.
|