{
  "schemaVersion": 1,
  "reviewedAt": "2026-10-16",
  "positioning": "Trusted Digital Infrastructure",
  "capabilityBoundary": "proposed / requires scope validation",
  "sourceUrls": [
    "https://rmoz.sa/en",
    "https://rmoz.sa/en/use-cases",
    "https://rmoz.sa/en/platform",
    "https://rmoz.sa/en/whitepaper"
  ],
  "groups": [
    {
      "id": "government",
      "title": "Government & public services",
      "intro": "Build better handoffs between agencies while keeping each official source and disclosure rule accountable.",
      "items": [
        {
          "id": "permits",
          "phase": "design",
          "route": "platform/registries-and-verification",
          "title": "Licences and permits",
          "summary": "Plan issuance, renewal, suspension and status checks for authorised business licences.",
          "input": "Official licence reference, issuer, validity period and change events.",
          "control": "The issuing authority approves each change; commercial and personal details stay private.",
          "outcome": "A limited, current validity check with a correction and revocation route."
        },
        {
          "id": "civil-credentials",
          "phase": "design",
          "route": "platform/identity-and-credentials",
          "title": "Civil and public credentials",
          "summary": "Evaluate verifiable references to official certificates without exposing identity records.",
          "input": "Authorised certificate issuer, scoped document identifier and revocation state.",
          "control": "Consent, data classification, human review and selective disclosure are required.",
          "outcome": "A verifier may check the issuer and record status without reading the underlying document."
        },
        {
          "id": "procurement",
          "phase": "design",
          "route": "platform/smart-contracts",
          "title": "Public procurement and contracts",
          "summary": "Trace tender milestones and approvals with clearly assigned institutional responsibilities.",
          "input": "Tender ID, bid events, authorised reviewers and contract version references.",
          "control": "Access by role, conflict-of-interest handling and auditable human award decisions.",
          "outcome": "An attributable review and change history—not automated procurement authority."
        },
        {
          "id": "judicial-evidence",
          "phase": "design",
          "route": "trust/security-and-governance",
          "title": "Judicial evidence custody",
          "summary": "Describe evidence handoffs and preservation checks for authorised legal processes.",
          "input": "Case reference, custodian, evidence manifest and each documented handoff.",
          "control": "Confidential storage, lawful access, retention rules and verified chain of custody.",
          "outcome": "An audit-ready sequence of references; admissibility remains a legal decision."
        }
      ]
    },
    {
      "id": "enterprise",
      "title": "Enterprise operations",
      "intro": "Connect operational systems first; introduce shared proofs only where handoffs are hard to reconcile.",
      "items": [
        {
          "id": "invoice-reconciliation",
          "phase": "design",
          "route": "platform/apis-and-interoperability",
          "title": "Invoice and receipt reconciliation",
          "summary": "Match a supplier invoice to an approved receipt and track exceptions across systems.",
          "input": "ERP invoice ID, purchase order, goods receipt and approved corrections.",
          "control": "Named data owners, idempotent events, duplicate detection and exception review.",
          "outcome": "A matched-reference history; no payment or settlement is performed."
        },
        {
          "id": "supply-chain",
          "phase": "design",
          "route": "use-cases/export-shipment-verification",
          "title": "Product and shipment traceability",
          "summary": "Join product identity, origin statements, custody handoffs and recall references.",
          "input": "Product or lot serial, issuer statement and signed shipment handoffs.",
          "control": "Physical checks and evidence ownership; GS1/EPCIS mapping only where authorised.",
          "outcome": "A versioned provenance timeline, not proof that the physical product is genuine."
        },
        {
          "id": "contract-approvals",
          "phase": "design",
          "route": "platform/smart-contracts",
          "title": "Digital contract approvals",
          "summary": "Follow contract drafts, approval stages, signature references and amendments.",
          "input": "Versioned agreement, responsible parties, consent and approval evidence.",
          "control": "Human authorisation and approved signature providers; no assumed legal e-signature.",
          "outcome": "A clearer audit trail with disputes and amendments handled explicitly."
        },
        {
          "id": "loyalty",
          "phase": "design",
          "route": "sectors/retail",
          "title": "Loyalty and rewards records",
          "summary": "Explore attributable rewards balances and controlled programme rules.",
          "input": "Programme issuer, points events, redemption rights and expiration policy.",
          "control": "Customer consent, fair expiry, fraud review and a non-transferable default.",
          "outcome": "A traceable programme record; transferable value requires separate legal review."
        }
      ]
    },
    {
      "id": "financial",
      "title": "Regulated financial concepts",
      "intro": "Plan payment, settlement and tokenisation workflows with authorised institutions; no financial operation is implied.",
      "items": [
        {
          "id": "interbank",
          "phase": "regulated",
          "route": "platform/blockchain-infrastructure",
          "title": "Interbank settlement design",
          "summary": "Map institutional settlement instructions, confirmation responsibilities and reconciliation.",
          "input": "Authorised payment instruction, counterparties, limits and reference events.",
          "control": "Licensed operator, risk controls, accounting, disputes and settlement-finality legal review.",
          "outcome": "A proposed workflow architecture, not an operating payment rail."
        },
        {
          "id": "iso20022",
          "phase": "regulated",
          "route": "platform/apis-and-interoperability",
          "title": "ISO 20022 message integration",
          "summary": "Evaluate message mapping between bank systems and accountable transaction records.",
          "input": "Approved message schemas, identifiers, source ledger and reconciliation events.",
          "control": "Bank-owned interface contracts, field validation, retention and replay protection.",
          "outcome": "An integration blueprint; no live SARIE, SADAD or bank connection is asserted."
        },
        {
          "id": "biometric-pos",
          "phase": "regulated",
          "route": "sectors/banking",
          "title": "Privacy-first biometric POS design",
          "summary": "Explore palm/vein verification as a private identity-provider step, separate from payment execution.",
          "input": "Consent, approved identity match outcome, transaction reference and merchant policy.",
          "control": "No raw biometric templates on a public ledger; minimise linkable references and require a licensed payment provider.",
          "outcome": "A privacy and approval pattern, not an available biometric payment service."
        },
        {
          "id": "sukuk",
          "phase": "regulated",
          "route": "use-cases/investment-asset-tokenization",
          "title": "Tokenised sukuk and asset rights",
          "summary": "Explore instrument terms and lifecycle events only after establishing the underlying rights.",
          "input": "Issuer authority, legal rights, eligibility, disclosures and appointed custodians.",
          "control": "CMA or other applicable approvals, Shariah review, investor protections and independent custody.",
          "outcome": "A scoped research case; no securities offer, issuance, yield or trading facility."
        }
      ]
    }
  ]
}