تخطَّ إلى المحتوىSkip to content
Tools & resources · Saudi hosting

What changed, and why?

A dated editorial history of the proposed policy, references, and tools. A source change requires review before it becomes an automated rule.

Clearer evidence and a connected journey

saudi-hosting-sources-2026-10-03.1 → saudi-hosting-sources-2026-10-03.2

  • Ten additional excerpts checked: R03, R05 and R09–R16. Corrected the CST guide URL and verified the CCC-2:2024 changes annex. These include technical and international comparison references, not only Saudi legal texts.
  • The register now exposes document status, dates and review limits. The MCIT contact reference remains pending after access denial; NDMO and sector mapping remain incomplete. No automated regulatory category was added.
  • Shared navigation now connects the hub, detailed guide, worksheets and NCA tool. Prompts identify their policy, source bundle and register, while the site flags overdue editorial rechecks.
  • Developer package 0.1.0-beta.2 carries the updated sources and compares reports across both beta versions. Native Codex discovery and tool invocation were tested with explicit project settings and no model call.

Scope policy saudi-hosted-draft-1.0 is unchanged. The previous bundle and inherited references remain preserved for comparison; this is a limited editorial review, not legal sign-off.

Initial local review edition

  • Proposed policy saudi-hosted-draft-1.0: six fictional cases with one engine shared by the lab and local tool.
  • Source bundle saudi-hosting-sources-2026-10-03.1: 16 references preserved; narrow boundaries checked for R02, R04, R06, R07, and R08. Other references remain pending.
  • Developer-beta CLI and MCP with sanitized reports and snapshot comparison. Production verification and legal classification remain outside scan results.
  • Explicit unknown handling in the existing navigator, connected to the current Excel workbooks and detailed guide.
  • Prepared for local review. Files in this edition do not imply a package-registry publication or approval of the proposal.

Updating a reference does not establish its applicability to a particular service. Future entries must identify the locator, reason and affected rules while preserving the prior version.