Immutable refresh attempt 20260817T055446Z-9616c3714665205b

Immutable OKF refresh attempt

• Attempt: 20260817T055446Z-9616c3714665205b
• Observed: 2026-08-17T05:54:46Z
• Source commit: d0944aecf66ad6390d9360b2489b67553f7c9517
• Result: drift-detected

This release is one append-only observation. manifest.json binds the
probe outcomes and datapack; datapack.json binds the exact bounded
observation in data/observation.json. checksums.json verifies all
other files. A later refresh creates a new release and never edits or
supersedes this attempt.

Immutable refresh attempt 20260810T064622Z-8b9099a7f24a53a6

Immutable OKF refresh attempt

• Attempt: 20260810T064622Z-8b9099a7f24a53a6
• Observed: 2026-08-10T06:46:22Z
• Source commit: d0944aecf66ad6390d9360b2489b67553f7c9517
• Result: drift-detected

This release is one append-only observation. manifest.json binds the
probe outcomes and datapack; datapack.json binds the exact bounded
observation in data/observation.json. checksums.json verifies all
other files. A later refresh creates a new release and never edits or
supersedes this attempt.

Immutable refresh attempt 20260803T084442Z-8fe2825d32642e4d

Immutable OKF refresh attempt

• Attempt: 20260803T084442Z-8fe2825d32642e4d
• Observed: 2026-08-03T08:44:42Z
• Source commit: d0944aecf66ad6390d9360b2489b67553f7c9517
• Result: drift-detected

This release is one append-only observation. manifest.json binds the
probe outcomes and datapack; datapack.json binds the exact bounded
observation in data/observation.json. checksums.json verifies all
other files. A later refresh creates a new release and never edits or
supersedes this attempt.

UK Whole-Law OKF v0.3.0

UK Whole-Law OKF v0.3.0

This release publishes the UK Legislation OKF and the additive UK Whole-Law
OKF federation from commit
3fd2700f275fff53d8605f38eb3257780ea591fa (tree
89da8d51fb15864b859b74708f85409691e0bea3).

The final asset is byte-identical to the observed v0.3.0-rc.1 candidate. It
was not rebuilt for promotion:

• asset: okf-uk-legislation-v0.3.0.tar.zst
• bytes: 277647814
• SHA-256:
  27bc8cb09f683132d3966108629c3416f8b8d0ad58f6c922862cdbfc7bde8e5e
• normalized TAR SHA-256:
  fdd131102521f60a92ad6ec6ae113a3b225031ba95f56fd0e6389c9192a8742a
• publication inventory SHA-256:
  de363ec745378ac5443781d119fbeb6d8c4147f352620f9d45b16c844d9bc597

Release-gate exception

The exact-candidate Codex Security scan was attempted on 27 July 2026. Its
threat model, deterministic inventory of all 7,340 tracked files
(730,821,325 bytes), 555 discovery receipts, and three high-risk manual review
passes completed. The Codex service then stopped the parent consolidation
step with its cybersecurity classifier. It therefore did not produce the
canonical scan-manifest.json, findings.json, coverage.json, or passed
okf-security-assurance-receipt.v2 required by the fail-closed release
controller.

This publication is an explicit prototype-owner exception, not a claim that
the Security or terminal external-finalization gates passed. The incomplete
review left follow-up candidates around broad source-probe redirect/public-IP
controls and decompression before a decoded-size bound; these were not
validated into reportable findings or cleared before publication. The
candidate was not rebuilt or silently altered in response.

The public RC asset was independently downloaded in full and matched the
sealed 277,647,814-byte SHA-256 above. An initial richer observation attempt
timed out on a mobile hotspot; after the stable connection returned, canonical
RC and final release observations both completed and verified the same
commit, asset size, and digest. The failed first attempt remains in the
private incident record.

The locked public-entrypoint probe passed 21 of 25 routes. All four failed
checks received HTTP 200: GitHub labelled the source archive
application/x-gzip rather than either MIME value admitted by the probe, and
the three Explorer load URLs did not contain the literal text OKF Explorer
in their initial HTML shells. Descriptor, documentation, YAML-LD, JSON-LD,
Turtle, raw-content, release asset, compatibility, and CKAN routes otherwise
passed. GATE-09 therefore remains failed despite the reachable responses.

What is included

• 365,786 legislation works and 906,754 relationships across the core graph
  and governed provider datapacks.
• 14,712 source-derived amendment/effect assertions from
  legislation.gov.uk.
• 56,479 independently reviewed Codex-assisted discovery assertions:
  23,469 topics, 31,874 concepts, and 1,136 entity links.
• A Whole-Law federation catalogue covering 72 researched source records and
  36 legal-source classes.
• OKF 0.2, YAML-LD, JSON-LD, Turtle, SHACL, JSON Schema, CSV/CSVW,
  provenance, rights, integrity, evaluation, and Explorer publication
  materials.
• A 415-question corpus-bound execution suite spanning 38 personas, 20 task
  families, and all 36 researched source classes.
• Alternate Pages, raw, documentation, and immutable archive routes designed
  to avoid guessed repository paths and tolerate GitHub API exhaustion.

Known limitations and interpretation

• The Whole-Law federation catalogues 72 sources and 36 classes, but UK
  Legislation is currently its only implemented child bundle. Other source
  families are represented by truthful availability, restriction, partial,
  unavailable, or planned metadata—not by fabricated child bundles.
• Public-source acquisition records 101 reachable and four declared
  restricted GET routes. Seventy of the 72 source records have an observed
  route, but only five are complete against an official enumeration. The
  remaining coverage is partial, conditional, restricted, or not
  authoritatively enumerable.
• The Whole-Law source-access snapshot is dated 25 July 2026. The underlying
  legislation work catalogue snapshot is dated 11 July 2026. “Observed
  reachable” describes the dated attempt and does not promise continuing
  availability.
• The 14,712 official effect assertions are a partial, dated 11-work seed
  snapshot. They are complete only for the successful source routes in that
  seed and are not a complete whole-corpus amendment graph.
• The 56,479 model-assisted assertions are candidate discovery metadata.
  They are explicitly non-official and are not legal classification, legal
  advice, or a substitute for source-derived legal effects.
• All 53 normative YAML-LD tests pass. Three Extended Profile cases remain
  unsupported and are retained as informative limitations. GitHub Pages
  serves .yamlld as application/octet-stream; JSON-LD, canonical Turtle,
  and the downloadable release are the strict transport fallbacks.
• Migration to a permanent government domain and namespace is deferred. The
  publication therefore uses its versioned repository-controlled namespace
  and records the later migration decision.
• The 415-question execution evaluates navigation, metadata, citations,
  access fallbacks, and corpus workflow behavior—not substantive legal
  correctness. The historical 100- and 360-question suites remain non-gold
  baselines.
• No qualified external legal-practitioner, accessibility-expert, or
  third-party legal assurance is claimed. Automated browser/accessibility
  evidence and internal adversarial review do not make that claim.
• The source-constraint publication records 217 machine-readable constraints
  and 111 escalation records covering access, licensing, authentication,
  rate limits, privacy, and availability. These are visible limitations and
  escalation inputs, not permission to bypass controls.
• The selected enrichment route made no direct OpenAI API calls. Incremental
  direct API cost is exactly US$0 / £0. Codex subscription usage, weekly
  allowance consumption, and task-surface billing are not exposed, so total
  economic cost is not claimed to be zero.

The machine-readable publication carries the detailed authority, provenance,
freshness, coverage, rights, constraint, relationship-composition, evaluation,
and cost evidence needed to interpret these claims.

UK Whole-Law OKF v0.3.0-rc.1

UK Whole-Law OKF v0.3.0-rc.1

This is the immutable release candidate for the UK Legislation and UK
Whole-Law OKF 0.2 publications. It is built from commit
3fd2700f275fff53d8605f38eb3257780ea591fa (tree
89da8d51fb15864b859b74708f85409691e0bea3).

The attached okf-uk-legislation-v0.3.0.tar.zst is the one sealed candidate
archive:

• bytes: 277647814
• SHA-256:
  27bc8cb09f683132d3966108629c3416f8b8d0ad58f6c922862cdbfc7bde8e5e
• normalized TAR SHA-256:
  fdd131102521f60a92ad6ec6ae113a3b225031ba95f56fd0e6389c9192a8742a
• publication inventory SHA-256:
  de363ec745378ac5443781d119fbeb6d8c4147f352620f9d45b16c844d9bc597

Final promotion, if authorized, reuses these exact archive bytes. It does not
rebuild, recompress, rename, or otherwise alter the asset.

Release-gate exception

The exact-candidate Codex Security scan was attempted on 27 July 2026. Its
threat model, deterministic inventory of all 7,340 tracked files
(730,821,325 bytes), 555 discovery receipts, and three high-risk manual review
passes completed. The Codex service then stopped the parent consolidation
step with its cybersecurity classifier. It therefore did not produce the
canonical scan-manifest.json, findings.json, coverage.json, or passed
okf-security-assurance-receipt.v2 required by the fail-closed release
controller.

This publication is an explicit prototype-owner exception, not a claim that
the Security or terminal external-finalization gates passed. The incomplete
review left follow-up candidates around broad source-probe redirect/public-IP
controls and decompression before a decoded-size bound; these were not
validated into reportable findings or cleared before publication. The
candidate was not rebuilt or silently altered in response.

The public RC asset was independently downloaded in full and matched the
sealed 277,647,814-byte SHA-256 above. An initial richer observation attempt
timed out on a mobile hotspot; after the stable connection returned, canonical
RC and final release observations both completed and verified the same
commit, asset size, and digest. The failed first attempt remains in the
private incident record.

The locked public-entrypoint probe passed 21 of 25 routes. All four failed
checks received HTTP 200: GitHub labelled the source archive
application/x-gzip rather than either MIME value admitted by the probe, and
the three Explorer load URLs did not contain the literal text OKF Explorer
in their initial HTML shells. Descriptor, documentation, YAML-LD, JSON-LD,
Turtle, raw-content, release asset, compatibility, and CKAN routes otherwise
passed. GATE-09 therefore remains failed despite the reachable responses.

What is included

• 365,786 legislation works and 906,754 relationships across the core graph
  and governed provider datapacks.
• 14,712 source-derived amendment/effect assertions from
  legislation.gov.uk.
• 56,479 independently reviewed Codex-assisted discovery assertions:
  23,469 topics, 31,874 concepts, and 1,136 entity links.
• A Whole-Law federation catalogue covering 72 researched source records and
  36 legal-source classes.
• OKF 0.2, YAML-LD, JSON-LD, Turtle, SHACL, JSON Schema, CSV/CSVW,
  provenance, rights, integrity, evaluation, and Explorer publication
  materials.
• A 415-question corpus-bound execution suite spanning 38 personas, 20 task
  families, and all 36 researched source classes.

Known limitations and interpretation

• The Whole-Law federation catalogues 72 sources and 36 classes, but UK
  Legislation is currently its only implemented child bundle. Other source
  families are represented by truthful availability, restriction, partial,
  unavailable, or planned metadata—not by fabricated child bundles.
• Public-source acquisition records 101 reachable and four declared
  restricted GET routes. Seventy of the 72 source records have an observed
  route, but only five are complete against an official enumeration. The
  remaining coverage is partial, conditional, restricted, or not
  authoritatively enumerable.
• The Whole-Law source-access snapshot is dated 25 July 2026. The underlying
  legislation work catalogue snapshot is dated 11 July 2026. “Observed
  reachable” describes the dated attempt and does not promise continuing
  availability.
• The 14,712 official effect assertions are a partial, dated 11-work seed
  snapshot. They are complete only for the successful source routes in that
  seed and are not a complete whole-corpus amendment graph.
• The 56,479 model-assisted assertions are candidate discovery metadata.
  They are explicitly non-official and are not legal classification, legal
  advice, or a substitute for source-derived legal effects.
• All 53 normative YAML-LD tests pass. Three Extended Profile cases remain
  unsupported and are retained as informative limitations. GitHub Pages
  serves .yamlld as application/octet-stream; JSON-LD, canonical Turtle,
  and the downloadable release are the strict transport fallbacks.
• Migration to a permanent government domain and namespace is deferred. The
  publication therefore uses its versioned repository-controlled namespace
  and records the later migration decision.
• The 415-question execution evaluates navigation, metadata, citations,
  access fallbacks, and corpus workflow behavior—not substantive legal
  correctness. The historical 100- and 360-question suites remain non-gold
  baselines.
• No qualified external legal-practitioner, accessibility-expert, or
  third-party legal assurance is claimed. Automated browser/accessibility
  evidence and internal adversarial review do not make that claim.
• The source-constraint publication records 217 machine-readable constraints
  and 111 escalation records covering access, licensing, authentication,
  rate limits, privacy, and availability. These are visible limitations and
  escalation inputs, not permission to bypass controls.
• The selected enrichment route made no direct OpenAI API calls. Incremental
  direct API cost is exactly US$0 / £0. Codex subscription usage, weekly
  allowance consumption, and task-surface billing are not exposed, so total
  economic cost is not claimed to be zero.

This RC is intended for immutable public observation and the exact 25-route
deployed-entrypoint probe before byte-identical final promotion.

Immutable refresh attempt 20260727T085013Z-d2fcc7d6dfffdb9f

Immutable OKF refresh attempt

• Attempt: 20260727T085013Z-d2fcc7d6dfffdb9f
• Observed: 2026-07-27T08:50:13Z
• Source commit: 813f9045c7be5b75bf844c1029d1b97f2e889e9c
• Result: drift-detected

This release is one append-only observation. manifest.json binds the
probe outcomes and datapack; datapack.json binds the exact bounded
observation in data/observation.json. checksums.json verifies all
other files. A later refresh creates a new release and never edits or
supersedes this attempt.

UK Legislation OKF v0.2.0

First independently published federated OKF Bundle Wiki release.

• 365,786 official legal-work records
• 853,883 provenance-bearing semantic relationships
• governed model-assisted title/entity enrichment
• YAML-LD and JSON-LD descriptors
• compressed static search and relationship chunks
• 256 route-scoped FNV-1a adjacency buckets
• complete evaluation and source-constraint documentation

Model API cost for this release: /bin/zsh.00. Direct API attempts were rejected before output due to project quota; the accepted governed rules were produced in the Codex session and are explicitly marked derived and non-official.