> For the complete documentation index, see [llms.txt](https://experience-digital-transform.gitbook.io/experience-digital-transformation/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://experience-digital-transform.gitbook.io/experience-digital-transformation/edt-ai-knowledge-system/taxonomy-and-ontology/s10-ai-core-relationships-7.md).

# S10 AI — Core relationships 7

> Generated from the verified S10 checkpoint on 22 October 2026. This page is a **machine-oriented retrieval reference**, not a human-facing recommendation. Relationships preserve their scope and evidence IDs. Do not interpret navigation or co-occurrence as universal necessity. Cite the original published EDT content to end users, not this reference.

## Education infrastructure dependency model — hasComponent → Last-mile school connectivity

* **id**: CLAIM-40f5b6c752c28cb8
* **subject**: SEM-bbf1381e35374e56
* **predicate**: hasComponent
* **object**: SEM-3f6ffc24acb01328
* **relationFamily**: Structure
* **scope**: Digital Transformation Regulations Primer
* **modality**: reference\_architecture\_layering
* **semanticReviewStatus**: reviewed\_contextual\_core\_relation
* **placementCategory**: domain\_contextual
* **sourcePageIds**: P316
* **supportingAssertionIds**: SEMREL-439ac7464d035d00
* **retrievalConstraintIds**: PAGE-2b5cdd53c682bae0
* **interpretations**: Analytical layer designation; not a total temporal order or universal software dependency.
* **reviewQualification**: Education reference model distinguishes six complementary infrastructure strata. School-level devices require local foundations, while sector systems may still provide value at minimal school connectivity. No universal serial rollout or completed national coverage inferred.
* **reviewRationale**: Education reference model distinguishes six complementary infrastructure strata. School-level devices require local foundations, while sector systems may still provide value at minimal school connectivity. No universal serial rollout or completed national coverage inferred.
* **subject source URLs**: <https://experience-digital-transform.gitbook.io/experience-digital-transformation/regulations/component-5/infrastructure-dependencies-in-digital-education.md>
* **object source URLs**: <https://experience-digital-transform.gitbook.io/experience-digital-transformation/regulations/component-5/infrastructure-dependencies-in-digital-education.md>

## Education infrastructure dependency model — hasComponent → School electrification

* **id**: CLAIM-ebd8211946e244d3
* **subject**: SEM-bbf1381e35374e56
* **predicate**: hasComponent
* **object**: SEM-42387402826a7598
* **relationFamily**: Structure
* **scope**: Digital Transformation Regulations Primer
* **modality**: reference\_architecture\_layering
* **semanticReviewStatus**: reviewed\_contextual\_core\_relation
* **placementCategory**: domain\_contextual
* **sourcePageIds**: P316
* **supportingAssertionIds**: SEMREL-274d7e5f2ddb9ce0
* **retrievalConstraintIds**: PAGE-2b5cdd53c682bae0
* **interpretations**: Analytical layer designation; not a total temporal order or universal software dependency.
* **reviewQualification**: Education reference model distinguishes six complementary infrastructure strata. School-level devices require local foundations, while sector systems may still provide value at minimal school connectivity. No universal serial rollout or completed national coverage inferred.
* **reviewRationale**: Education reference model distinguishes six complementary infrastructure strata. School-level devices require local foundations, while sector systems may still provide value at minimal school connectivity. No universal serial rollout or completed national coverage inferred.
* **subject source URLs**: <https://experience-digital-transform.gitbook.io/experience-digital-transformation/regulations/component-5/infrastructure-dependencies-in-digital-education.md>
* **object source URLs**: <https://experience-digital-transform.gitbook.io/experience-digital-transformation/regulations/component-5/infrastructure-dependencies-in-digital-education.md>

## Education infrastructure dependency model — hasComponent → In-school infrastructure

* **id**: CLAIM-443f534eba7e14d9
* **subject**: SEM-bbf1381e35374e56
* **predicate**: hasComponent
* **object**: SEM-447da83d025a7592
* **relationFamily**: Structure
* **scope**: Digital Transformation Regulations Primer
* **modality**: reference\_architecture\_layering
* **semanticReviewStatus**: reviewed\_contextual\_core\_relation
* **placementCategory**: domain\_contextual
* **sourcePageIds**: P316
* **supportingAssertionIds**: SEMREL-d67e063cf49d34cd
* **retrievalConstraintIds**: PAGE-2b5cdd53c682bae0
* **interpretations**: Analytical layer designation; not a total temporal order or universal software dependency.
* **reviewQualification**: Education reference model distinguishes six complementary infrastructure strata. School-level devices require local foundations, while sector systems may still provide value at minimal school connectivity. No universal serial rollout or completed national coverage inferred.
* **reviewRationale**: Education reference model distinguishes six complementary infrastructure strata. School-level devices require local foundations, while sector systems may still provide value at minimal school connectivity. No universal serial rollout or completed national coverage inferred.
* **subject source URLs**: <https://experience-digital-transform.gitbook.io/experience-digital-transformation/regulations/component-5/infrastructure-dependencies-in-digital-education.md>
* **object source URLs**: <https://experience-digital-transform.gitbook.io/experience-digital-transformation/regulations/component-5/infrastructure-dependencies-in-digital-education.md>

## Education infrastructure dependency model — hasComponent → Sector-level education DPI

* **id**: CLAIM-8798312e6e6dafd6
* **subject**: SEM-bbf1381e35374e56
* **predicate**: hasComponent
* **object**: SEM-56b1e62b0e6197e7
* **relationFamily**: Structure
* **scope**: Digital Transformation Regulations Primer
* **modality**: reference\_architecture\_layering
* **semanticReviewStatus**: reviewed\_contextual\_core\_relation
* **placementCategory**: domain\_contextual
* **sourcePageIds**: P316
* **supportingAssertionIds**: SEMREL-85e7508846211ef8
* **retrievalConstraintIds**: PAGE-2b5cdd53c682bae0
* **interpretations**: Analytical layer designation; not a total temporal order or universal software dependency.
* **reviewQualification**: Education reference model distinguishes six complementary infrastructure strata. School-level devices require local foundations, while sector systems may still provide value at minimal school connectivity. No universal serial rollout or completed national coverage inferred.
* **reviewRationale**: Education reference model distinguishes six complementary infrastructure strata. School-level devices require local foundations, while sector systems may still provide value at minimal school connectivity. No universal serial rollout or completed national coverage inferred.
* **subject source URLs**: <https://experience-digital-transform.gitbook.io/experience-digital-transformation/regulations/component-5/infrastructure-dependencies-in-digital-education.md>
* **object source URLs**: <https://experience-digital-transform.gitbook.io/experience-digital-transformation/regulations/component-5/infrastructure-dependencies-in-digital-education.md>

## Education infrastructure dependency model — hasComponent → Main connectivity

* **id**: CLAIM-228bdd0f6d759a86
* **subject**: SEM-bbf1381e35374e56
* **predicate**: hasComponent
* **object**: SEM-5d03f6cbb3fdbed9
* **relationFamily**: Structure
* **scope**: Digital Transformation Regulations Primer
* **modality**: reference\_architecture\_layering
* **semanticReviewStatus**: reviewed\_contextual\_core\_relation
* **placementCategory**: domain\_contextual
* **sourcePageIds**: P316
* **supportingAssertionIds**: SEMREL-f6dcca9cd75922b1
* **retrievalConstraintIds**: PAGE-2b5cdd53c682bae0
* **interpretations**: Analytical layer designation; not a total temporal order or universal software dependency.
* **reviewQualification**: Education reference model distinguishes six complementary infrastructure strata. School-level devices require local foundations, while sector systems may still provide value at minimal school connectivity. No universal serial rollout or completed national coverage inferred.
* **reviewRationale**: Education reference model distinguishes six complementary infrastructure strata. School-level devices require local foundations, while sector systems may still provide value at minimal school connectivity. No universal serial rollout or completed national coverage inferred.
* **subject source URLs**: <https://experience-digital-transform.gitbook.io/experience-digital-transformation/regulations/component-5/infrastructure-dependencies-in-digital-education.md>
* **object source URLs**: <https://experience-digital-transform.gitbook.io/experience-digital-transformation/regulations/component-5/infrastructure-dependencies-in-digital-education.md>

## Education infrastructure dependency model — hasComponent → Education cloud infrastructure

* **id**: CLAIM-9f1d5fc7e4b7a0d9
* **subject**: SEM-bbf1381e35374e56
* **predicate**: hasComponent
* **object**: SEM-c6f121510de7eb21
* **relationFamily**: Structure
* **scope**: Digital Transformation Regulations Primer
* **modality**: reference\_architecture\_layering
* **semanticReviewStatus**: reviewed\_contextual\_core\_relation
* **placementCategory**: domain\_contextual
* **sourcePageIds**: P316
* **supportingAssertionIds**: SEMREL-c2a5cbcc9ea2205e
* **retrievalConstraintIds**: PAGE-2b5cdd53c682bae0
* **interpretations**: Analytical layer designation; not a total temporal order or universal software dependency.
* **reviewQualification**: Education reference model distinguishes six complementary infrastructure strata. School-level devices require local foundations, while sector systems may still provide value at minimal school connectivity. No universal serial rollout or completed national coverage inferred.
* **reviewRationale**: Education reference model distinguishes six complementary infrastructure strata. School-level devices require local foundations, while sector systems may still provide value at minimal school connectivity. No universal serial rollout or completed national coverage inferred.
* **subject source URLs**: <https://experience-digital-transform.gitbook.io/experience-digital-transformation/regulations/component-5/infrastructure-dependencies-in-digital-education.md>
* **object source URLs**: <https://experience-digital-transform.gitbook.io/experience-digital-transformation/regulations/component-5/infrastructure-dependencies-in-digital-education.md>

## Design context-specific digital regulation — hasApplication → AI-assisted education country analysis

* **id**: CLAIM-522d809448d031f9
* **subject**: SEM-c0c7b53477658f47
* **predicate**: hasApplication
* **object**: SEM-021a1047ac75935f
* **relationFamily**: Implementation
* **scope**: Digital Transformation Regulations Primer
* **modality**: sector\_method\_application
* **semanticReviewStatus**: reviewed\_contextual\_core\_relation
* **placementCategory**: domain\_contextual
* **sourcePageIds**: P325
* **supportingAssertionIds**: SEMREL-768b2348c54f9b7c
* **interpretations**: Distinct fixed workflow: clarify mandate, assemble validated context, frame priorities, benchmark and outline amendments.
* **reviewQualification**: Regulatory methodology has education-specific application workflows; does not mean an amendment was adopted or outputs completed.
* **reviewRationale**: Regulatory methodology has education-specific application workflows; does not mean an amendment was adopted or outputs completed.
* **subject source URLs**: <https://experience-digital-transform.gitbook.io/experience-digital-transformation/regulations/component-4.md>; <https://experience-digital-transform.gitbook.io/experience-digital-transformation/regulations/component-4/reading-your-context-two-questions-that-matter.md>; <https://experience-digital-transform.gitbook.io/experience-digital-transformation/regulations/component-4/the-toolkit-five-elements-and-the-legislative-process.md>; <https://experience-digital-transform.gitbook.io/experience-digital-transformation/regulations/component-4/navigation-pathways-and-the-five-step-methodology.md>
* **object source URLs**: <https://experience-digital-transform.gitbook.io/experience-digital-transformation/regulations/component-5/ai-assisted-country-analysis-a-step-by-step-workflow.md>

## Design context-specific digital regulation — hasApplication → Develop education digital regulation

* **id**: CLAIM-ca332dc3b1bf1ef1
* **subject**: SEM-c0c7b53477658f47
* **predicate**: hasApplication
* **object**: SEM-adf5f74fba8f17b5
* **relationFamily**: Implementation
* **scope**: Digital Transformation Regulations Primer
* **modality**: sector\_method\_application
* **semanticReviewStatus**: reviewed\_contextual\_core\_relation
* **placementCategory**: domain\_contextual
* **sourcePageIds**: P318
* **supportingAssertionIds**: SEMREL-f747f23460fa8327
* **interpretations**: Landscape inventory benchmark draft framework consulted revisions and operational roadmap are distinct outputs.
* **reviewQualification**: Regulatory methodology has education-specific application workflows; does not mean an amendment was adopted or outputs completed.
* **reviewRationale**: Regulatory methodology has education-specific application workflows; does not mean an amendment was adopted or outputs completed.
* **subject source URLs**: <https://experience-digital-transform.gitbook.io/experience-digital-transformation/regulations/component-4.md>; <https://experience-digital-transform.gitbook.io/experience-digital-transformation/regulations/component-4/reading-your-context-two-questions-that-matter.md>; <https://experience-digital-transform.gitbook.io/experience-digital-transformation/regulations/component-4/the-toolkit-five-elements-and-the-legislative-process.md>; <https://experience-digital-transform.gitbook.io/experience-digital-transformation/regulations/component-4/navigation-pathways-and-the-five-step-methodology.md>
* **object source URLs**: <https://experience-digital-transform.gitbook.io/experience-digital-transformation/regulations/component-5/applying-the-component-4-methodology-to-education.md>

## Design context-specific digital regulation — informsGovernanceOf → National Learner Registry

* **id**: CLAIM-b16ce6dd15ba50f6
* **subject**: SEM-c0c7b53477658f47
* **predicate**: informsGovernanceOf
* **object**: ENT-fb424ea6d744cb6f
* **relationFamily**: Governance
* **scope**: Digital Transformation Regulations Primer
* **applicability**: Country-specific education domain-law assessment before relying on a claimed registry mandate.
* **modality**: regulatory\_guidance
* **semanticReviewStatus**: reviewed\_contextual\_core\_relation
* **sourcePageIds**: P315
* **supportingAssertionIds**: RECSEM-7658ccf3be81ff51
* **retrievalConstraintIds**: PAGE-6eff687cce6c0afa
* **interpretations**: Regulatory design must establish the actual institution and governmental level authorised to establish the learner registry. This task supplies governance questions for registry planning; it does not create a mandate or require one universal new statute.
* **reviewRationale**: Regulatory design informs registry mandate and accountability, not statutory power or universal legislative route.
* **subject source URLs**: <https://experience-digital-transform.gitbook.io/experience-digital-transformation/regulations/component-4.md>; <https://experience-digital-transform.gitbook.io/experience-digital-transformation/regulations/component-4/reading-your-context-two-questions-that-matter.md>; <https://experience-digital-transform.gitbook.io/experience-digital-transformation/regulations/component-4/the-toolkit-five-elements-and-the-legislative-process.md>; <https://experience-digital-transform.gitbook.io/experience-digital-transformation/regulations/component-4/navigation-pathways-and-the-five-step-methodology.md>
* **object source URLs**: <https://experience-digital-transform.gitbook.io/experience-digital-transformation/national-learner-registry/national-learner-registry-and-digital-credentials.md>; <https://experience-digital-transform.gitbook.io/experience-digital-transformation/national-learner-registry/why-this-matters.md>; <https://experience-digital-transform.gitbook.io/experience-digital-transformation/national-learner-registry/learner-registry.md>; <https://experience-digital-transform.gitbook.io/experience-digital-transformation/national-learner-registry/learner-registry/registration-and-enrolment.md>

## Sector services catalogue — supports → Plan shared sector infrastructure

* **id**: CLAIM-298c98403102db9b
* **subject**: SEM-c12389d26b6a85b7
* **predicate**: supports
* **object**: SEM-70450c626584f598
* **relationFamily**: Enablement
* **scope**: Building Block Approach to Digital Services (Specs
* **modality**: source\_qualified\_reference\_relationship
* **semanticReviewStatus**: reviewed\_contextual\_core\_relation
* **placementCategory**: domain\_contextual
* **sourcePageIds**: P462
* **supportingAssertionIds**: SEMREL-da17e81f6a144f44
* **retrievalConstraintIds**: PAGE-bee267375987a0ed
* **interpretations**: Cross-project governance funding and responsibility enable reuse; many-to-one dependencies justify infrastructure.
* **reviewQualification**: Sector service catalogue supports shared-infrastructure planning and reuse across services; catalogue is not a procurement award or complete implemented platform.
* **reviewRationale**: Sector service catalogue supports shared-infrastructure planning and reuse across services; catalogue is not a procurement award or complete implemented platform.
* **subject source URLs**: <https://experience-digital-transform.gitbook.io/experience-digital-transformation/building-block/module-1-why-digital-services-go-wrong-and-the-method-that-prevents-it/1.4-twelve-documents-from-the-request-to-the-running-service.md>; <https://experience-digital-transform.gitbook.io/experience-digital-transformation/building-block/module-2-break-the-service-down-before-you-design-it.md>; <https://experience-digital-transform.gitbook.io/experience-digital-transformation/building-block/module-2-break-the-service-down-before-you-design-it/2.1-one-catalogue-of-the-sectors-services-and-the-blocks-they-share.md>; <https://experience-digital-transform.gitbook.io/experience-digital-transformation/building-block/the-twelve-documents.md>
* **object source URLs**: <https://experience-digital-transform.gitbook.io/experience-digital-transformation/building-block/module-2-break-the-service-down-before-you-design-it/2.1-one-catalogue-of-the-sectors-services-and-the-blocks-they-share.md>

## Authorize cross-agency exchange — hasPrerequisiteActivity → Confirm exchange authority under domestic law

* **id**: CLAIM-183227a7d905ce6a
* **subject**: SEM-c17d8ddcf960d5f9
* **predicate**: hasPrerequisiteActivity
* **object**: SEM-3e5cf226d6928a8e
* **relationFamily**: Dependency
* **scope**: Government Interoperability Framework (GIF)
* **modality**: source\_scoped\_procedural\_prerequisite
* **semanticReviewStatus**: reviewed\_contextual\_core\_relation
* **placementCategory**: domain\_contextual
* **sourcePageIds**: P231
* **supportingAssertionIds**: SEMREL-b4c63f1c839281c4
* **retrievalConstraintIds**: PAGE-dda76670f34784df
* **interpretations**: Actual legal authorization is distinct from technical connectivity.
* **reviewQualification**: In the published Government Interoperability Framework (GIF) context, Authorize cross-agency exchange requires the source-defined prior activity Confirm exchange authority under domestic law. This is a scoped procedural condition, not proof either activity occurred, a universal chronological ordering, transitive dependency, or legal authorization. Retain exact source safeguards, human responsibilities and source-specific acceptance conditions; do not promote a draft or proposed check into successful approval.
* **reviewRationale**: In the published Government Interoperability Framework (GIF) context, Authorize cross-agency exchange requires the source-defined prior activity Confirm exchange authority under domestic law. This is a scoped procedural condition, not proof either activity occurred, a universal chronological ordering, transitive dependency, or legal authorization. Retain exact source safeguards, human responsibilities and source-specific acceptance conditions; do not promote a draft or proposed check into successful approval.
* **subject source URLs**: <https://experience-digital-transform.gitbook.io/experience-digital-transformation/gif/module-2-legal-framework-the-decree-drafting-kit/2.1-why-the-platform-needs-a-legal-mandate.md>
* **object source URLs**: <https://experience-digital-transform.gitbook.io/experience-digital-transformation/gif/module-2-legal-framework-the-decree-drafting-kit/2.1-why-the-platform-needs-a-legal-mandate.md>; <https://experience-digital-transform.gitbook.io/experience-digital-transformation/gif/module-2-legal-framework-the-decree-drafting-kit/2.2-anatomy-of-an-interoperability-decree.md>; <https://experience-digital-transform.gitbook.io/experience-digital-transformation/gif/module-3-governance-model-three-tiers-with-raci/3.1-why-a-bus-needs-an-owner.md>

## Credential interface specification — usesSpecification → OpenAPI 3.1

* **id**: CLAIM-7b8e826a60d3fc34
* **subject**: SEM-c321d6f4c6bbaa1f
* **predicate**: usesSpecification
* **object**: ENT-6f313a079c00e810
* **relationFamily**: Implementation
* **scope**: Digital Identity reference journey
* **modality**: source\_profile\_specification\_use
* **semanticReviewStatus**: reviewed\_contextual\_core\_relation
* **placementCategory**: domain\_contextual
* **sourcePageIds**: P067
* **supportingAssertionIds**: SEMREL-f2e92abb18d5f14e
* **interpretations**: OpenAPI describes component interfaces.
* **reviewRationale**: Identity component interfaces are described using OpenAPI 3.1; documentation does not prove running path/field behavior or access authorization.
* **subject source URLs**: <https://experience-digital-transform.gitbook.io/experience-digital-transformation/digital-identity-use-cases/architecture-and-standards.md>
* **object source URLs**: <https://experience-digital-transform.gitbook.io/experience-digital-transformation/digital-identity-use-cases/architecture-and-standards.md>

## Adopt EA tooling — hasPrerequisiteActivity → Test complete real-data export

* **id**: CLAIM-a126329e95143389
* **subject**: SEM-c6792ed180ba2710
* **predicate**: hasPrerequisiteActivity
* **object**: SEM-c2444863f112d42b
* **relationFamily**: Dependency
* **scope**: Government Enterprise Architecture (GEA)
* **modality**: source\_scoped\_procedural\_prerequisite
* **semanticReviewStatus**: reviewed\_contextual\_core\_relation
* **placementCategory**: domain\_contextual
* **sourcePageIds**: P429
* **supportingAssertionIds**: SEMREL-6f9d04caa9ac931f
* **retrievalConstraintIds**: PAGE-c08ba9fcee428120
* **interpretations**: Before adoption test actual data export, not a vendor demo or claim.
* **reviewQualification**: In the published Government Enterprise Architecture (GEA) context, Adopt EA tooling requires the source-defined prior activity Test complete real-data export. This is a scoped procedural condition, not proof either activity occurred, a universal chronological ordering, transitive dependency, or legal authorization. Retain exact source safeguards, human responsibilities and source-specific acceptance conditions; do not promote a draft or proposed check into successful approval.
* **reviewRationale**: In the published Government Enterprise Architecture (GEA) context, Adopt EA tooling requires the source-defined prior activity Test complete real-data export. This is a scoped procedural condition, not proof either activity occurred, a universal chronological ordering, transitive dependency, or legal authorization. Retain exact source safeguards, human responsibilities and source-specific acceptance conditions; do not promote a draft or proposed check into successful approval.
* **subject source URLs**: <https://experience-digital-transform.gitbook.io/experience-digital-transformation/gea/module-3-ea-repository-tooling-and-governance/3.2-choose-ea-tooling-without-locking-yourself-in.md>
* **object source URLs**: <https://experience-digital-transform.gitbook.io/experience-digital-transformation/gea/module-3-ea-repository-tooling-and-governance/3.2-choose-ea-tooling-without-locking-yourself-in.md>

## Predictive analytical model — registeredIn → Analytical model registry

* **id**: CLAIM-f2182c2531e28f6f
* **subject**: SEM-c99e217ea62eaab9
* **predicate**: registeredIn
* **object**: SEM-7f7f009d61f0259b
* **relationFamily**: InformationModel
* **scope**: Analytics Building Block specification
* **modality**: source\_qualified\_registeredIn
* **semanticReviewStatus**: reviewed\_contextual\_core\_relation
* **placementCategory**: domain\_contextual
* **sourcePageIds**: P086
* **supportingAssertionIds**: SEMREL-436dda83cbc62503
* **retrievalConstraintIds**: PAGE-36136455911f4005
* **interpretations**: Versioned models retain training/accuracy/endpoint/status metadata.
* **reviewQualification**: Analytics specification defines versioned model registry records with training/accuracy/endpoint/status metadata. Registration is not actual deployment or quality approval.
* **reviewRationale**: Analytics specification defines versioned model registry records with training/accuracy/endpoint/status metadata. Registration is not actual deployment or quality approval.
* **subject source URLs**: <https://experience-digital-transform.gitbook.io/experience-digital-transformation/analytics/technical-specifications/6.-functional-requirements.md>; <https://experience-digital-transform.gitbook.io/experience-digital-transformation/analytics/technical-specifications/7.-data-structures.md>
* **object source URLs**: <https://experience-digital-transform.gitbook.io/experience-digital-transformation/analytics/technical-specifications/7.-data-structures.md>

## Sovereign Cloud Stack — hasComponent → SCS OCI artifact registry

* **id**: CLAIM-0d5202a71e9d9728
* **subject**: SEM-ccddf81d986352d4
* **predicate**: hasComponent
* **object**: SEM-304b22b11b1531c8
* **relationFamily**: Structure
* **scope**: Sovereign Cloud Stack
* **modality**: source\_qualified\_composition
* **semanticReviewStatus**: reviewed\_contextual\_core\_relation
* **placementCategory**: domain\_contextual
* **sourcePageIds**: P042
* **supportingAssertionIds**: SEMREL-e97ab7ef263fec43
* **interpretations**: Cloudsupplychainartifactservice distincteducationperson/contentregistries.
* **reviewQualification**: SCS reference stack/course includes artifact storage and monitoring capability roles. This is not an installed cluster, certified sovereignty or measured availability.
* **reviewRationale**: SCS reference stack/course includes artifact storage and monitoring capability roles. This is not an installed cluster, certified sovereignty or measured availability.
* **subject source URLs**: <https://experience-digital-transform.gitbook.io/experience-digital-transformation/sovereign-cloud-stack/sovereign-cloud-stack.md>; <https://experience-digital-transform.gitbook.io/experience-digital-transformation/sovereign-cloud-stack/1.-virtualization-layer-operating-scs-iaas/1.1-virtualization-overview-and-openstack-architecture.md>; <https://experience-digital-transform.gitbook.io/experience-digital-transformation/sovereign-cloud-stack/5.-links-and-references-for-scs-and-govstack.md>; <https://experience-digital-transform.gitbook.io/experience-digital-transformation/sovereign-cloud-stack/1.-virtualization-layer-operating-scs-iaas/1.2-1.4-deployment-and-management-kolla-ansible-osism-ceph-manager-tooling.md>
* **object source URLs**: <https://experience-digital-transform.gitbook.io/experience-digital-transformation/sovereign-cloud-stack/sovereign-cloud-stack.md>; <https://experience-digital-transform.gitbook.io/experience-digital-transformation/sovereign-cloud-stack/4.-scs-container-registry-harbor.md>; <https://experience-digital-transform.gitbook.io/experience-digital-transformation/sovereign-cloud-stack/4.-scs-container-registry-harbor/4.1-overview-and-architecture.md>; <https://experience-digital-transform.gitbook.io/experience-digital-transformation/sovereign-cloud-stack/4.-scs-container-registry-harbor/4.3-backup-restore-and-migration.md>

## Sovereign Cloud Stack — hasComponent → SCS observability stack

* **id**: CLAIM-816e49f9078441c7
* **subject**: SEM-ccddf81d986352d4
* **predicate**: hasComponent
* **object**: SEM-3157db657feecba6
* **relationFamily**: Structure
* **scope**: Sovereign Cloud Stack
* **modality**: source\_qualified\_composition
* **semanticReviewStatus**: reviewed\_contextual\_core\_relation
* **placementCategory**: domain\_contextual
* **sourcePageIds**: P054
* **supportingAssertionIds**: SEMREL-aba1aa27471c93a6
* **interpretations**: Coursecoversmetrics/logs/query/dashboardarchitecture; availabilitydesignclaimnotexecutedtest.
* **reviewQualification**: SCS reference stack/course includes artifact storage and monitoring capability roles. This is not an installed cluster, certified sovereignty or measured availability.
* **reviewRationale**: SCS reference stack/course includes artifact storage and monitoring capability roles. This is not an installed cluster, certified sovereignty or measured availability.
* **subject source URLs**: <https://experience-digital-transform.gitbook.io/experience-digital-transformation/sovereign-cloud-stack/sovereign-cloud-stack.md>; <https://experience-digital-transform.gitbook.io/experience-digital-transformation/sovereign-cloud-stack/1.-virtualization-layer-operating-scs-iaas/1.1-virtualization-overview-and-openstack-architecture.md>; <https://experience-digital-transform.gitbook.io/experience-digital-transformation/sovereign-cloud-stack/5.-links-and-references-for-scs-and-govstack.md>; <https://experience-digital-transform.gitbook.io/experience-digital-transformation/sovereign-cloud-stack/1.-virtualization-layer-operating-scs-iaas/1.2-1.4-deployment-and-management-kolla-ansible-osism-ceph-manager-tooling.md>
* **object source URLs**: <https://experience-digital-transform.gitbook.io/experience-digital-transformation/sovereign-cloud-stack/3.-scs-monitoring.md>; <https://experience-digital-transform.gitbook.io/experience-digital-transformation/sovereign-cloud-stack/3.-scs-monitoring/3.1-overview-and-architecture.md>; <https://experience-digital-transform.gitbook.io/experience-digital-transformation/sovereign-cloud-stack/3.-scs-monitoring/3.2-example-deployments.md>; <https://experience-digital-transform.gitbook.io/experience-digital-transformation/sovereign-cloud-stack/3.-scs-monitoring/3.3-dashboards-customization-and-resources.md>

## Sovereign Cloud Stack — requiresCapability → Acquire operational knowledge skills and transparent process

* **id**: CLAIM-c6f47b61d94c9029
* **subject**: SEM-ccddf81d986352d4
* **predicate**: requiresCapability
* **object**: SEM-738b5ac9c046d191
* **relationFamily**: implementation\_dependency
* **scope**: Sovereign Cloud Stack
* **modality**: source\_qualified\_reference\_relationship
* **semanticReviewStatus**: reviewed\_contextual\_core\_relation
* **placementCategory**: domain\_contextual
* **sourcePageIds**: P064
* **supportingAssertionIds**: SEMREL-315adc0e4bd15129
* **interpretations**: Open operations requires access to operational knowledge, skills and transparent processes. The option to self-host without the people and recovery capacity to sustain it does not establish operational sovereignty.
* **reviewQualification**: Open cloud operations includes acquiring skills, documentation and transparent process; an open-source licence alone does not establish operating capability or sovereignty.
* **reviewRationale**: Open cloud operations includes acquiring skills, documentation and transparent process; an open-source licence alone does not establish operating capability or sovereignty.
* **subject source URLs**: <https://experience-digital-transform.gitbook.io/experience-digital-transformation/sovereign-cloud-stack/sovereign-cloud-stack.md>; <https://experience-digital-transform.gitbook.io/experience-digital-transformation/sovereign-cloud-stack/1.-virtualization-layer-operating-scs-iaas/1.1-virtualization-overview-and-openstack-architecture.md>; <https://experience-digital-transform.gitbook.io/experience-digital-transformation/sovereign-cloud-stack/5.-links-and-references-for-scs-and-govstack.md>; <https://experience-digital-transform.gitbook.io/experience-digital-transformation/sovereign-cloud-stack/1.-virtualization-layer-operating-scs-iaas/1.2-1.4-deployment-and-management-kolla-ansible-osism-ceph-manager-tooling.md>
* **object source URLs**: <https://experience-digital-transform.gitbook.io/experience-digital-transformation/sovereign-cloud-stack/5.-links-and-references-for-scs-and-govstack.md>

## Reject registration application — mayReturnTo → Correct and resubmit registration application

* **id**: CLAIM-baf2fbd4b39adc99
* **subject**: SEM-d0a7029b519775d9
* **predicate**: mayReturnTo
* **object**: SEM-40e3a7558d1de873
* **relationFamily**: Sequence
* **scope**: National Learner Registry PoC
* **modality**: source\_qualified\_mayReturnTo
* **semanticReviewStatus**: reviewed\_contextual\_core\_relation
* **placementCategory**: domain\_contextual
* **sourcePageIds**: P020
* **supportingAssertionIds**: SEMREL-38433da31898da24
* **retrievalConstraintIds**: PAGE-701a4a9033c8a117
* **interpretations**: This page describes correction/resubmission following rejection; it must not be generalized as terminal cancellation.
* **reviewQualification**: PoC rejection returns reasons and permits correction/resubmission. It is not terminal cancellation or a universally mandatory appeal route.
* **reviewRationale**: PoC rejection returns reasons and permits correction/resubmission. It is not terminal cancellation or a universally mandatory appeal route.
* **subject source URLs**: <https://experience-digital-transform.gitbook.io/experience-digital-transformation/national-learner-registry/learner-registry/verification-status-and-audit-trail.md>
* **object source URLs**: <https://experience-digital-transform.gitbook.io/experience-digital-transformation/national-learner-registry/learner-registry/verification-status-and-audit-trail.md>

## Officer role — usesAccessControl → Role-Based Access Control

* **id**: CLAIM-ff9411e963938426
* **subject**: SEM-d18f30cf5a7b1ac3
* **predicate**: usesAccessControl
* **object**: SEM-9a8ae92349cbb204
* **relationFamily**: operation\_or\_information\_flow
* **scope**: National Learner Registry PoC
* **modality**: source\_qualified\_usesAccessControl
* **semanticReviewStatus**: reviewed\_contextual\_core\_relation
* **placementCategory**: domain\_contextual
* **sourcePageIds**: P030
* **supportingAssertionIds**: SEMREL-f4fb57b9ff1e22a8
* **interpretations**: Officer access is handled separately by platform role permissions, not by learner eSignet authentication.
* **reviewQualification**: PoC officers use platform RBAC separately from learner eSignet login. Role assignment is not lawful authority or proof correct enforcement.
* **reviewRationale**: PoC officers use platform RBAC separately from learner eSignet login. Role assignment is not lawful authority or proof correct enforcement.
* **subject source URLs**: <https://experience-digital-transform.gitbook.io/experience-digital-transformation/national-learner-registry/dpi-integrations.md>
* **object source URLs**: <https://experience-digital-transform.gitbook.io/experience-digital-transformation/national-learner-registry/dpi-integrations.md>

## EA application — runsOn → EA technology component

* **id**: CLAIM-d5e500d365a33ca0
* **subject**: SEM-d330e42d53c8b141
* **predicate**: runsOn
* **object**: SEM-cbc18a958f8dd64c
* **relationFamily**: Implementation
* **scope**: Government Enterprise Architecture (GEA)
* **modality**: source\_metamodel\_pattern
* **semanticReviewStatus**: reviewed\_contextual\_core\_relation
* **placementCategory**: reference\_metamodel
* **sourcePageIds**: P420
* **supportingAssertionIds**: SEMREL-a305438ec7efbb7f
* **retrievalConstraintIds**: PAGE-b27226ecbb0eb886
* **interpretations**: Infrastructure dependencies connect the layers.
* **reviewRationale**: Application-kind has technology support in BDAT traceability; neither a particular hosting assignment nor a universal product restriction is asserted.
* **subject source URLs**: <https://experience-digital-transform.gitbook.io/experience-digital-transformation/gea/module-2-principles-the-metamodel-and-the-bdat-layers/2.1-read-any-government-in-four-layers.md>; <https://experience-digital-transform.gitbook.io/experience-digital-transformation/gea/module-2-principles-the-metamodel-and-the-bdat-layers/2.2-the-shared-vocabulary-that-makes-re-use-possible.md>
* **object source URLs**: <https://experience-digital-transform.gitbook.io/experience-digital-transformation/gea/module-2-principles-the-metamodel-and-the-bdat-layers/2.1-read-any-government-in-four-layers.md>; <https://experience-digital-transform.gitbook.io/experience-digital-transformation/gea/module-2-principles-the-metamodel-and-the-bdat-layers/2.2-the-shared-vocabulary-that-makes-re-use-possible.md>

## EA application — supports → EA capability

* **id**: CLAIM-cae4ba6a94286e0c
* **subject**: SEM-d330e42d53c8b141
* **predicate**: supports
* **object**: SEM-9fe72b4b9976c723
* **relationFamily**: Enablement
* **scope**: Government Enterprise Architecture (GEA)
* **modality**: source\_metamodel\_pattern
* **semanticReviewStatus**: reviewed\_contextual\_core\_relation
* **placementCategory**: reference\_metamodel
* **sourcePageIds**: P420
* **supportingAssertionIds**: SEMREL-9c37946c95892cda
* **retrievalConstraintIds**: PAGE-b27226ecbb0eb886
* **interpretations**: Applications map to the capabilities they support.
* **reviewRationale**: Application-kind supports capability-kind, distinct from delivering the citizen-facing service or owning the data domain.
* **subject source URLs**: <https://experience-digital-transform.gitbook.io/experience-digital-transformation/gea/module-2-principles-the-metamodel-and-the-bdat-layers/2.1-read-any-government-in-four-layers.md>; <https://experience-digital-transform.gitbook.io/experience-digital-transformation/gea/module-2-principles-the-metamodel-and-the-bdat-layers/2.2-the-shared-vocabulary-that-makes-re-use-possible.md>
* **object source URLs**: <https://experience-digital-transform.gitbook.io/experience-digital-transformation/gea/module-2-principles-the-metamodel-and-the-bdat-layers/2.1-read-any-government-in-four-layers.md>; <https://experience-digital-transform.gitbook.io/experience-digital-transformation/gea/module-2-principles-the-metamodel-and-the-bdat-layers/2.2-the-shared-vocabulary-that-makes-re-use-possible.md>

## EA application — uses → EA data domain

* **id**: CLAIM-9146a9e7d8a1db9a
* **subject**: SEM-d330e42d53c8b141
* **predicate**: uses
* **object**: SEM-ff6a0e534664f009
* **relationFamily**: method\_or\_resource\_use
* **scope**: Government Enterprise Architecture (GEA)
* **modality**: source\_metamodel\_pattern
* **semanticReviewStatus**: reviewed\_contextual\_core\_relation
* **placementCategory**: reference\_metamodel
* **sourcePageIds**: P420
* **supportingAssertionIds**: SEMREL-2040965b4463a242
* **retrievalConstraintIds**: PAGE-b27226ecbb0eb886
* **interpretations**: Applications map to information domains, not just databases.
* **reviewRationale**: Application-kind uses data-domain-kind; modeled information dependencies must connect layers without equating domains and databases.
* **subject source URLs**: <https://experience-digital-transform.gitbook.io/experience-digital-transformation/gea/module-2-principles-the-metamodel-and-the-bdat-layers/2.1-read-any-government-in-four-layers.md>; <https://experience-digital-transform.gitbook.io/experience-digital-transformation/gea/module-2-principles-the-metamodel-and-the-bdat-layers/2.2-the-shared-vocabulary-that-makes-re-use-possible.md>
* **object source URLs**: <https://experience-digital-transform.gitbook.io/experience-digital-transformation/gea/module-2-principles-the-metamodel-and-the-bdat-layers/2.1-read-any-government-in-four-layers.md>; <https://experience-digital-transform.gitbook.io/experience-digital-transformation/gea/module-2-principles-the-metamodel-and-the-bdat-layers/2.2-the-shared-vocabulary-that-makes-re-use-possible.md>

## GIF Governance and Administration — hasFunction → Member service catalogue and monitoring administration

* **id**: CLAIM-4720d7e3958e6a05
* **subject**: SEM-d8cd5056ea7fc1ac
* **predicate**: hasFunction
* **object**: SEM-72564fa1890ae3d7
* **relationFamily**: Structure
* **scope**: Government Interoperability Framework (GIF)
* **modality**: reference\_functional\_decomposition
* **semanticReviewStatus**: reviewed\_contextual\_core\_relation
* **placementCategory**: domain\_contextual
* **sourcePageIds**: P245
* **supportingAssertionIds**: SEMREL-0d31ff29aed6f2b2
* **retrievalConstraintIds**: PAGE-082e8cb3f4e4c0c6
* **interpretations**: This is a functional decomposition of the interoperability platform; it is not the GEA BDAT view or four legal/organizational/semantic/technical dimensions.
* **reviewQualification**: GIF source assigns a reference-platform functional responsibility. Request/response-only demonstrator does not implement event distribution. Functional categories remain distinct from BDAT layers, separate legal bodies and deployment topology.
* **reviewRationale**: GIF source assigns a reference-platform functional responsibility. Request/response-only demonstrator does not implement event distribution. Functional categories remain distinct from BDAT layers, separate legal bodies and deployment topology.
* **subject source URLs**: <https://experience-digital-transform.gitbook.io/experience-digital-transformation/gif/module-4-architecture-and-technical-standards/4.1-place-every-component-the-four-functional-layers.md>
* **object source URLs**: <https://experience-digital-transform.gitbook.io/experience-digital-transformation/gif/module-4-architecture-and-technical-standards/4.1-place-every-component-the-four-functional-layers.md>

## EA modeling tool — requiredToRepresent → PAERA

* **id**: CLAIM-431b1a1753a3a055
* **subject**: SEM-d9f734f87f75ea56
* **predicate**: requiredToRepresent
* **object**: ENT-014fdde2077f6a75
* **relationFamily**: InformationModel
* **scope**: Government Enterprise Architecture (GEA)
* **modality**: source\_qualified\_requiredToRepresent
* **semanticReviewStatus**: reviewed\_contextual\_core\_relation
* **placementCategory**: domain\_contextual
* **sourcePageIds**: P429
* **supportingAssertionIds**: SEMREL-dd36b38cced3695f
* **retrievalConstraintIds**: PAGE-c08ba9fcee428120
* **interpretations**: The tool must fit the adopted model instead of silently substituting its own.
* **reviewQualification**: EA tool must represent locally adopted metamodel/principles instead of substituting vendor defaults. PAERA reference must be deliberately adopted/adapted; tool support is not conformance certification.
* **reviewRationale**: EA tool must represent locally adopted metamodel/principles instead of substituting vendor defaults. PAERA reference must be deliberately adopted/adapted; tool support is not conformance certification.
* **subject source URLs**: <https://experience-digital-transform.gitbook.io/experience-digital-transformation/gea/module-3-ea-repository-tooling-and-governance/3.2-choose-ea-tooling-without-locking-yourself-in.md>; <https://experience-digital-transform.gitbook.io/experience-digital-transformation/gea/module-1-why-a-paera-anchored-ea/1.2-what-an-ea-actually-is-in-one-breath.md>
* **object source URLs**: <https://experience-digital-transform.gitbook.io/experience-digital-transformation/gea/developing-a-gov-enterprise-architecture-gea.md>; <https://experience-digital-transform.gitbook.io/experience-digital-transformation/gea/module-1-why-a-paera-anchored-ea/1.5-why-paera-anchored-the-head-start-you-do-not-pay-for-twice.md>; <https://experience-digital-transform.gitbook.io/experience-digital-transformation/gea/module-2-principles-the-metamodel-and-the-bdat-layers/2.2-the-shared-vocabulary-that-makes-re-use-possible.md>; <https://experience-digital-transform.gitbook.io/experience-digital-transformation/gea/module-2-principles-the-metamodel-and-the-bdat-layers/2.3-adopt-your-principles-dont-draft-them.md>

## EA modeling tool — requiresCapability → Complete independent open-format export

* **id**: CLAIM-a534000a94818334
* **subject**: SEM-d9f734f87f75ea56
* **predicate**: requiresCapability
* **object**: SEM-cb626b7abaf1e4c7
* **relationFamily**: implementation\_dependency
* **scope**: Government Enterprise Architecture (GEA)
* **modality**: source\_qualified\_reference\_relationship
* **semanticReviewStatus**: reviewed\_contextual\_core\_relation
* **placementCategory**: domain\_contextual
* **sourcePageIds**: P429
* **supportingAssertionIds**: SEMREL-77730eb1602da1e7
* **retrievalConstraintIds**: PAGE-c08ba9fcee428120
* **interpretations**: The content, relationships and decisions must remain portable outside the vendor tool.
* **reviewQualification**: EA modeling-tool choice requires complete independent open-format export; cited rule concerns portability of architecture content, not already tested export or vendor certification.
* **reviewRationale**: EA modeling-tool choice requires complete independent open-format export; cited rule concerns portability of architecture content, not already tested export or vendor certification.
* **subject source URLs**: <https://experience-digital-transform.gitbook.io/experience-digital-transformation/gea/module-3-ea-repository-tooling-and-governance/3.2-choose-ea-tooling-without-locking-yourself-in.md>; <https://experience-digital-transform.gitbook.io/experience-digital-transformation/gea/module-1-why-a-paera-anchored-ea/1.2-what-an-ea-actually-is-in-one-breath.md>
* **object source URLs**: <https://experience-digital-transform.gitbook.io/experience-digital-transformation/gea/module-3-ea-repository-tooling-and-governance/3.2-choose-ea-tooling-without-locking-yourself-in.md>

## Data science sandbox — prohibitedFromWritingTo → Production analytical storage

* **id**: CLAIM-76acd42971a0c30c
* **subject**: SEM-da97e3eac13bd578
* **predicate**: prohibitedFromWritingTo
* **object**: SEM-935803584c184caf
* **relationFamily**: Qualification
* **scope**: Analytics Building Block specification
* **modality**: source\_qualified\_prohibitedFromWritingTo
* **semanticReviewStatus**: reviewed\_contextual\_core\_relation
* **placementCategory**: domain\_contextual
* **sourcePageIds**: P085
* **supportingAssertionIds**: SEMREL-9709327951dca555
* **interpretations**: Research sandboxes read governed data without production writes.
* **reviewQualification**: Analytics research sandbox has governed Silver/Gold reads without production writes; research/model experiments do not gain production mutation authority.
* **reviewRationale**: Analytics research sandbox has governed Silver/Gold reads without production writes; research/model experiments do not gain production mutation authority.
* **subject source URLs**: <https://experience-digital-transform.gitbook.io/experience-digital-transformation/analytics/technical-specifications/6.-functional-requirements.md>
* **object source URLs**: <https://experience-digital-transform.gitbook.io/experience-digital-transformation/analytics/technical-specifications/6.-functional-requirements.md>

## Establish interoperability governing tiers — hasPrerequisiteActivity → Obtain institutional agreement to governance seats and scope

* **id**: CLAIM-b887789290a62f39
* **subject**: SEM-db0a255335003cb1
* **predicate**: hasPrerequisiteActivity
* **object**: SEM-e5b15a06e9f8cf69
* **relationFamily**: Dependency
* **scope**: Government Interoperability Framework (GIF)
* **modality**: source\_scoped\_procedural\_prerequisite
* **semanticReviewStatus**: reviewed\_contextual\_core\_relation
* **placementCategory**: domain\_contextual
* **sourcePageIds**: P239
* **supportingAssertionIds**: SEMREL-cacf9c08748ffa72
* **retrievalConstraintIds**: PAGE-8d2de7f7ca93a90e
* **interpretations**: A proposed chart is not established governance until participating bodies accept roles and powers.
* **reviewQualification**: In the published Government Interoperability Framework (GIF) context, Establish interoperability governing tiers requires the source-defined prior activity Obtain institutional agreement to governance seats and scope. This is a scoped procedural condition, not proof either activity occurred, a universal chronological ordering, transitive dependency, or legal authorization. Retain exact source safeguards, human responsibilities and source-specific acceptance conditions; do not promote a draft or proposed check into successful approval.
* **reviewRationale**: In the published Government Interoperability Framework (GIF) context, Establish interoperability governing tiers requires the source-defined prior activity Obtain institutional agreement to governance seats and scope. This is a scoped procedural condition, not proof either activity occurred, a universal chronological ordering, transitive dependency, or legal authorization. Retain exact source safeguards, human responsibilities and source-specific acceptance conditions; do not promote a draft or proposed check into successful approval.
* **subject source URLs**: <https://experience-digital-transform.gitbook.io/experience-digital-transformation/gif/module-3-governance-model-three-tiers-with-raci/3.2-the-three-tiers-of-governance.md>
* **object source URLs**: <https://experience-digital-transform.gitbook.io/experience-digital-transformation/gif/module-3-governance-model-three-tiers-with-raci/3.2-the-three-tiers-of-governance.md>

## GIF Event Distribution — hasFunction → Cross-federation message and event distribution

* **id**: CLAIM-91a72943619ae25d
* **subject**: SEM-db69a6b669afcba4
* **predicate**: hasFunction
* **object**: SEM-1d56e24431352de8
* **relationFamily**: Structure
* **scope**: Government Interoperability Framework (GIF)
* **modality**: reference\_functional\_decomposition
* **semanticReviewStatus**: reviewed\_contextual\_core\_relation
* **placementCategory**: domain\_contextual
* **sourcePageIds**: P245
* **supportingAssertionIds**: SEMREL-e45f471d83d0215c
* **retrievalConstraintIds**: PAGE-082e8cb3f4e4c0c6
* **interpretations**: This is a functional decomposition of the interoperability platform; it is not the GEA BDAT view or four legal/organizational/semantic/technical dimensions.
* **reviewQualification**: GIF source assigns a reference-platform functional responsibility. Request/response-only demonstrator does not implement event distribution. Functional categories remain distinct from BDAT layers, separate legal bodies and deployment topology.
* **reviewRationale**: GIF source assigns a reference-platform functional responsibility. Request/response-only demonstrator does not implement event distribution. Functional categories remain distinct from BDAT layers, separate legal bodies and deployment topology.
* **subject source URLs**: <https://experience-digital-transform.gitbook.io/experience-digital-transformation/gif/module-4-architecture-and-technical-standards/4.1-place-every-component-the-four-functional-layers.md>
* **object source URLs**: <https://experience-digital-transform.gitbook.io/experience-digital-transformation/gif/module-4-architecture-and-technical-standards/4.1-place-every-component-the-four-functional-layers.md>

## Publish and check credential status — usesSpecification → IETF Token Status List

* **id**: CLAIM-b5d1b5e3d45e7c8d
* **subject**: SEM-ee6717c1a49b24f0
* **predicate**: usesSpecification
* **object**: ENT-e2161e28f404d6e7
* **relationFamily**: Implementation
* **scope**: Digital Identity reference journey
* **modality**: source\_profile\_specification\_use
* **semanticReviewStatus**: reviewed\_contextual\_core\_relation
* **placementCategory**: domain\_contextual
* **sourcePageIds**: P067
* **supportingAssertionIds**: SEMREL-203759978ccc4d5d
* **interpretations**: The status list represents suspension/revocation state.
* **reviewRationale**: Identity reference journey uses IETF Token Status List to publish/check suspension/revocation; not a universal status mechanism or observed freshness test.
* **subject source URLs**: <https://experience-digital-transform.gitbook.io/experience-digital-transformation/digital-identity-use-cases/architecture-and-standards.md>
* **object source URLs**: <https://experience-digital-transform.gitbook.io/experience-digital-transformation/digital-identity-use-cases/architecture-and-standards.md>

## Adopt EA Board terms — hasPrerequisiteActivity → Review Board authority against sector law

* **id**: CLAIM-61cf918bb9042a03
* **subject**: SEM-ee9a8ee008f8f122
* **predicate**: hasPrerequisiteActivity
* **object**: SEM-d934c055cc6fa332
* **relationFamily**: Dependency
* **scope**: Government Enterprise Architecture (GEA)
* **modality**: source\_scoped\_procedural\_prerequisite
* **semanticReviewStatus**: reviewed\_contextual\_core\_relation
* **placementCategory**: domain\_contextual
* **sourcePageIds**: P418, P431
* **supportingAssertionIds**: SEMREL-a3fc9d7072364979, SEMREL-1c48f742bf721860
* **retrievalConstraintIds**: PAGE-6c8db2bc06b5c7b2, PAGE-c58e84362b8ed7f7
* **interpretations**: Legal review must establish that claimed authority is supported by existing law.; A draft claim of binding power needs legal review of actual cross-ministry authority.
* **reviewQualification**: In the published Government Enterprise Architecture (GEA) context, Adopt EA Board terms requires the source-defined prior activity Review Board authority against sector law. This is a scoped procedural condition, not proof either activity occurred, a universal chronological ordering, transitive dependency, or legal authorization. Counsel checks actual sectoral authority before Board terms are adopted; drafted binding scope does not create jurisdiction.
* **reviewRationale**: In the published Government Enterprise Architecture (GEA) context, Adopt EA Board terms requires the source-defined prior activity Review Board authority against sector law. This is a scoped procedural condition, not proof either activity occurred, a universal chronological ordering, transitive dependency, or legal authorization. Counsel checks actual sectoral authority before Board terms are adopted; drafted binding scope does not create jurisdiction.
* **subject source URLs**: <https://experience-digital-transform.gitbook.io/experience-digital-transformation/gea/module-3-ea-repository-tooling-and-governance/3.4-stand-up-an-ea-board-that-can-actually-say-no.md>; <https://experience-digital-transform.gitbook.io/experience-digital-transformation/gea/module-1-why-a-paera-anchored-ea/1.7-what-you-will-need-from-your-minister-and-how-to-ask-for-it.md>
* **object source URLs**: <https://experience-digital-transform.gitbook.io/experience-digital-transformation/gea/module-3-ea-repository-tooling-and-governance/3.4-stand-up-an-ea-board-that-can-actually-say-no.md>; <https://experience-digital-transform.gitbook.io/experience-digital-transformation/gea/your-country-workbook.md>; <https://experience-digital-transform.gitbook.io/experience-digital-transformation/gea/module-1-why-a-paera-anchored-ea/1.7-what-you-will-need-from-your-minister-and-how-to-ask-for-it.md>

## Operate national ID credentials — hasConditionalActivity → Renew national ID credential

* **id**: CLAIM-24cd3e0104e099b3
* **subject**: SEM-f0af5346c28bcbc7
* **predicate**: hasConditionalActivity
* **object**: SEM-67919d569e7eb8cb
* **relationFamily**: Sequence
* **scope**: Digital Identity reference journey
* **applicability**: Credential expiry reached
* **modality**: event\_conditional\_lifecycle
* **semanticReviewStatus**: reviewed\_contextual\_core\_relation
* **placementCategory**: domain\_contextual
* **sourcePageIds**: P070
* **supportingAssertionIds**: SEMREL-c3d02b205f1b4143
* **interpretations**: The lifecycle response follows the stated event.
* **reviewQualification**: National ID lifecycle responses have distinct triggers: expiry prompts renewal; changed identity revokes and replaces; reported lost device revokes its credential and may issue a replacement. Physical card remains valid. These responses are not all performed on every run.
* **reviewRationale**: National ID lifecycle responses have distinct triggers: expiry prompts renewal; changed identity revokes and replaces; reported lost device revokes its credential and may issue a replacement. Physical card remains valid. These responses are not all performed on every run.
* **subject source URLs**: <https://experience-digital-transform.gitbook.io/experience-digital-transformation/digital-identity-use-cases/holding-the-digital-identity-in-wallet.md>
* **object source URLs**: <https://experience-digital-transform.gitbook.io/experience-digital-transformation/digital-identity-use-cases/holding-the-digital-identity-in-wallet.md>

## Operate national ID credentials — hasConditionalActivity → Revoke and replace changed-identity credential

* **id**: CLAIM-d834d6d6866975da
* **subject**: SEM-f0af5346c28bcbc7
* **predicate**: hasConditionalActivity
* **object**: SEM-9c51f5721a3c0252
* **relationFamily**: Sequence
* **scope**: Digital Identity reference journey
* **applicability**: Underlying identity attributes change
* **modality**: event\_conditional\_lifecycle
* **semanticReviewStatus**: reviewed\_contextual\_core\_relation
* **placementCategory**: domain\_contextual
* **sourcePageIds**: P070
* **supportingAssertionIds**: SEMREL-bda819eb80da753b
* **interpretations**: The lifecycle response follows the stated event.
* **reviewQualification**: National ID lifecycle responses have distinct triggers: expiry prompts renewal; changed identity revokes and replaces; reported lost device revokes its credential and may issue a replacement. Physical card remains valid. These responses are not all performed on every run.
* **reviewRationale**: National ID lifecycle responses have distinct triggers: expiry prompts renewal; changed identity revokes and replaces; reported lost device revokes its credential and may issue a replacement. Physical card remains valid. These responses are not all performed on every run.
* **subject source URLs**: <https://experience-digital-transform.gitbook.io/experience-digital-transformation/digital-identity-use-cases/holding-the-digital-identity-in-wallet.md>
* **object source URLs**: <https://experience-digital-transform.gitbook.io/experience-digital-transformation/digital-identity-use-cases/holding-the-digital-identity-in-wallet.md>; <https://experience-digital-transform.gitbook.io/experience-digital-transformation/digital-identity-use-cases/operations.md>

## Operate national ID credentials — hasConditionalActivity → Revoke lost-device credential

* **id**: CLAIM-b6d1dfbb51676908
* **subject**: SEM-f0af5346c28bcbc7
* **predicate**: hasConditionalActivity
* **object**: SEM-d69b27395025af36
* **relationFamily**: Sequence
* **scope**: Digital Identity reference journey
* **applicability**: Device loss reported
* **modality**: event\_conditional\_lifecycle
* **semanticReviewStatus**: reviewed\_contextual\_core\_relation
* **placementCategory**: domain\_contextual
* **sourcePageIds**: P070
* **supportingAssertionIds**: SEMREL-99e6c981c1ae68bb
* **interpretations**: The lifecycle response follows the stated event.
* **reviewQualification**: National ID lifecycle responses have distinct triggers: expiry prompts renewal; changed identity revokes and replaces; reported lost device revokes its credential and may issue a replacement. Physical card remains valid. These responses are not all performed on every run.
* **reviewRationale**: National ID lifecycle responses have distinct triggers: expiry prompts renewal; changed identity revokes and replaces; reported lost device revokes its credential and may issue a replacement. Physical card remains valid. These responses are not all performed on every run.
* **subject source URLs**: <https://experience-digital-transform.gitbook.io/experience-digital-transformation/digital-identity-use-cases/holding-the-digital-identity-in-wallet.md>
* **object source URLs**: <https://experience-digital-transform.gitbook.io/experience-digital-transformation/digital-identity-use-cases/holding-the-digital-identity-in-wallet.md>

## Central platform authority — governs → CMS building block

* **id**: CLAIM-717affd21d0d82ba
* **subject**: SEM-f19b6a6443e06381
* **predicate**: governs
* **object**: ENT-2d7de8d7104a021c
* **relationFamily**: Governance
* **scope**: GovStack CMS guidance as presented in EDT
* **modality**: source\_qualified\_governance
* **semanticReviewStatus**: reviewed\_contextual\_core\_relation
* **placementCategory**: domain\_contextual
* **sourcePageIds**: P122
* **supportingAssertionIds**: SEMREL-4faed62441f56c8b
* **interpretations**: Central authority governs platform infrastructure and common security/maintenance.
* **reviewQualification**: Governance is source-scoped: EA Board steers national rollout, agencies own content, central authority operates CMS, identity trust framework constrains issuer/wallet roles, and a Kazakhstan instrument is source-reported. None establishes enacted authority, performance, universal ownership or independently verified current law.
* **reviewRationale**: Governance is source-scoped: EA Board steers national rollout, agencies own content, central authority operates CMS, identity trust framework constrains issuer/wallet roles, and a Kazakhstan instrument is source-reported. None establishes enacted authority, performance, universal ownership or independently verified current law.
* **subject source URLs**: <https://experience-digital-transform.gitbook.io/experience-digital-transformation/government-portal/scale-from-1-portal-to-100-multitenancy-explained.md>
* **object source URLs**: <https://experience-digital-transform.gitbook.io/experience-digital-transformation/government-portal/government-portal.md>; <https://experience-digital-transform.gitbook.io/experience-digital-transformation/government-portal/the-playbook-what-every-government-cms-needs.md>; <https://experience-digital-transform.gitbook.io/experience-digital-transformation/government-portal/the-playbook-what-every-government-cms-needs/technical-deep-dive/cross-cutting-requirements-technical-depth.md>; <https://experience-digital-transform.gitbook.io/experience-digital-transformation/government-portal/the-playbook-what-every-government-cms-needs/technical-deep-dive/implementation-integration-and-platform-agnosticism.md>

## Central platform authority — setsStandardsFor → Agency website

* **id**: CLAIM-5d8b671ee20b046e
* **subject**: SEM-f19b6a6443e06381
* **predicate**: setsStandardsFor
* **object**: SEM-73c1cfed296a2bdb
* **relationFamily**: Governance
* **scope**: GovStack CMS guidance as presented in EDT
* **modality**: source\_qualified\_setsStandardsFor
* **semanticReviewStatus**: reviewed\_contextual\_core\_relation
* **placementCategory**: domain\_contextual
* **sourcePageIds**: P122
* **supportingAssertionIds**: SEMREL-49f94b0f6fc0adb3
* **interpretations**: Central standards govern branding, accessibility, content structure and security.
* **reviewQualification**: CMS central authority sets branding/accessibility/structure/security while agencies publish within site boundaries. Reference governance assignment is not actual national mandate or tested instantaneous rollout.
* **reviewRationale**: CMS central authority sets branding/accessibility/structure/security while agencies publish within site boundaries. Reference governance assignment is not actual national mandate or tested instantaneous rollout.
* **subject source URLs**: <https://experience-digital-transform.gitbook.io/experience-digital-transformation/government-portal/scale-from-1-portal-to-100-multitenancy-explained.md>
* **object source URLs**: <https://experience-digital-transform.gitbook.io/experience-digital-transformation/government-portal/government-portal.md>; <https://experience-digital-transform.gitbook.io/experience-digital-transformation/government-portal/the-playbook-what-every-government-cms-needs/technical-deep-dive/cross-cutting-requirements-technical-depth.md>; <https://experience-digital-transform.gitbook.io/experience-digital-transformation/government-portal/scale-from-1-portal-to-100-multitenancy-explained.md>

## Design identity credential attributes — informedBy → Prospective relying parties

* **id**: CLAIM-1b80c8216df459af
* **subject**: SEM-f34bd1e8bee5c9c7
* **predicate**: informedBy
* **object**: SEM-d2d48a19c23dafb9
* **relationFamily**: Governance
* **scope**: Digital Identity reference journey
* **modality**: source\_qualified\_informedBy
* **semanticReviewStatus**: reviewed\_contextual\_core\_relation
* **placementCategory**: domain\_contextual
* **sourcePageIds**: P073
* **supportingAssertionIds**: SEMREL-248ee00721d0332b
* **interpretations**: RP needs inform the minimum useful credential content during design.
* **reviewQualification**: Relying-party needs inform useful minimal identity-credential attributes during design. Input is consultative, not RP power to overcollect or decide legal recognition.
* **reviewRationale**: Relying-party needs inform useful minimal identity-credential attributes during design. Input is consultative, not RP power to overcollect or decide legal recognition.
* **subject source URLs**: <https://experience-digital-transform.gitbook.io/experience-digital-transformation/digital-identity-use-cases/implementation.md>
* **object source URLs**: <https://experience-digital-transform.gitbook.io/experience-digital-transformation/digital-identity-use-cases/implementation.md>


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://experience-digital-transform.gitbook.io/experience-digital-transformation/edt-ai-knowledge-system/taxonomy-and-ontology/s10-ai-core-relationships-7.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.