feat(docs): update mapping governance to target HRIO erv or pub stages

- Revised the start stage for mappings to allow work only after the HRIO package reaches the `erv` (external review) stage.
- Added clarification on targeting mature HRIO stages (`erv` or `pub`) and excluding `int` or `irv` stages.
- Updated quick-check checklist to reflect changes in the mapping strategy.
- Added warning in mapping strategy documentation to emphasize targeting only mature HRIO packages.

Author: pedropaulofb

docs/method/mapping-governance.md

@@ -20,11 +20,11 @@ This policy defines how the Health-RI SSSOM Mapping Set is governed, validated,
 
 #### Start stage for mappings
 
-At the current maturity level, mapping work may begin once the relevant HRIO package reaches `irv` (internal review). Our target policy is to allow mappings only after the package is in `pub` (published). Stage definitions are described in the [Ontology Lifecycle and Validation Policy](./ontology-validation.md).
+At the current maturity level, mapping work may begin once the relevant HRIO package reaches `erv` (external review). Our target policy is to prefer mappings to `pub` (published) packages when possible. Mappings MUST NOT target concepts from packages in `int` (internal) or `irv` (internal review). Stage definitions are described in the [Ontology Lifecycle and Validation Policy](./ontology-validation.md).
 
 !!! info "Mapping stability depends on HRIO maturity"
 
-    If the target HRIO package is still in internal review, mappings may need revision after publication. Prefer mapping against `pub` packages when possible, and expect supersession when meanings evolve.
+    If the target HRIO package is still in external review, mappings may need revision after publication. Prefer mapping against `pub` packages when possible, and expect supersession when meanings evolve.
 
 ### In Scope
 
@@ -186,6 +186,7 @@ flowchart LR
     !!! success "Curator quick-check"
 
         - [ ] Required columns
+        - [ ] Target HRIO stage: `object_id` belongs to a package in stage `erv` or `pub`
         - [ ] Allowed HRIV predicates and valid (optional) `predicate_modifier`
         - [ ] CURIE/URI hygiene (resolves with 2xx/3xx where applicable)
         - [ ] `replaces` points to an existing record

docs/method/mapping-schema.md

@@ -185,6 +185,7 @@ Both methods ensure your contribution is reviewed and incorporated into the offi
 Before submitting, please verify the following to ensure your contribution is complete and compliant with the schema:
 
 - All **mandatory** contributor fields are present and correctly formatted.
+- The `object_id` you choose is an HRIO concept in a package at stage `erv` or `pub` (do not map to `int` or `irv` packages).
 - All `subject_label` and `object_label` fields you provide are language-tagged (e.g., `Patient@en`, `Patiënt@nl`).
 - Any optional values provided use valid identifiers (e.g., ORCID IDs, resolvable URIs, SEMAPV terms).
 

docs/method/mapping-strategy.md

@@ -71,6 +71,10 @@ Theories of formal semantics tell us that an OWL class gets its meaning from two
 
 Our common semantic reference model (HRIO) provides the shared meanings to which external concept definitions can be mapped. When another ontology defines `ont:Human`, it may be semantically aligned with our `hrio:Person`. To make this relationship explicit, a **`hriv:hasExactMeaning`** link can be asserted—either by the Health-RI mapping team (e.g., in SSSOM format), or by the owners of the external ontology within their artifact—signifying that the external concept's intended semantics are fully and precisely defined by that linked HRIO meaning.
 
+!!! warning "Target only mature HRIO packages"
+
+    Create mappings only to HRIO concepts in packages at stage `erv` or `pub`. Do not create mappings to concepts in packages at stage `int` or `irv`. Stage definitions are described in the [Ontology Lifecycle and Validation Policy](./ontology-validation.md).
+
 There are two possible approaches for creating and maintaining such mappings:
 
 - **Mappings performed by the Health-RI team:** In this case, mappings are created by Health-RI's semantic modeling team and provided in [SSSOM](https://w3id.org/sssom/) format. This is the default strategy when the external ontology or resource is publicly available or beyond Health-RI's editorial control (e.g., national standards, web-accessible vocabularies). These mappings are *non-invasive*, meaning they do not alter the original artifacts but describe their alignment externally. For details on how these mappings are published, versioned, and curated, see the [SSSOM Mapping Set](./mapping-schema.md).