GLOBAL100 v1.01 – UNIVERSAL JUDGMENT-PDF ARCHIVE

Page code: G100

Controlled title: Global100 — Universal Judgment-PDF Archive

Subtitle: Canonical judicial-decision source library and neutral judgment-record control

Current live baseline: G100 v1.01

Component revision: v1.01B

Governed by: G000 / MLSP v1.02 — active component revision v1.02A

Status: Live universal judgment-archive control baseline

Supersedes for active universal use: G100 v1.00

Previous controlled version:

https://peacekeepers.org.uk/judgments-2/

Case effect: No automatic adoption. Each C00 must separately record adopt, defer or decline.

Current live URL:

https://peacekeepers.org.uk/g100-judgments/

Effective date: 21 July 2026 14:00 BST

Web revision token: G100-v1.01-20260731T2016-BST

Operating standard: G000 CORE 10 applies to every G100 source and record task.

1. PURPOSE

G100 is the universal source archive for canonical copies of judgments, tribunal decisions, approved transcripts, authoritative law reports and limited companion records used across controlled litigation projects.

G100 preserves and identifies the judicial-decision source. It answers:

What is the decision document, where did it come from, what version is canonical, and where are its principal documentary components located?

G100 does not itself determine what legal proposition the decision establishes, classify a passage as ratio or obiter, extract a binding principle of law, approve a quotation or pinpoint, apply the decision to a later case or mark an authority Bundle Approved.

Those functions belong to G200 and the relevant case-specific C30 record.

Every G100 record must remain traceable to its original source, original filename, provenance, document type, source status, file condition, canonical version, duplicate or companion relationship, hash and verification state.

2. SOURCE-FIRST AND RECORD-ONLY CONTROL

SOURCE FIRST | The judicial-decision file is preserved before any proposition, ratio, principle, quotation or later-case application is asserted from it.

Inclusion in G100 does not prove:

that every statement in the decision is ratio;
that the decision is binding on a later court;
that a headnote or editorial summary is accurate;
that a reported quotation is complete;
that an observation survives later authority;
that a permission-stage observation is a final merits determination;
that a derived proposition has been judicially adopted; or
that the decision applies to the facts or remedy in a later case.

G100 may provide neutral documentary navigation. It must not convert navigation metadata into a verified legal proposition.

No title, filename, link label, archive description, institutional practice, commentary or prior case use displaces Appendix A or determines the legal effect of the decision.

3. CONTROLLED PAGE BOUNDARY

Page	Controlled function	What does not belong there
G000	Universal methodology, governance, case setup, source control, authority classification, release control and universal-to-case handoffs.	Uncontrolled judgment archive files, except expressly classified source copies or worked examples.
G100	Canonical judicial-decision files, source metadata, provenance, duplicate and companion control, and neutral analytical navigation.	Verified propositions of law, binding-principle classification, later-case application, remedy selection or Bundle Approved status.
G200	Source-verified propositions of law, case-specific ratios, binding principles of law at the justified level of generality, obiter, dissent, derived propositions, transposition, quotations, limits and pinpoints.	Duplicate source binaries presented as though storage itself verifies the proposition.
C20	Case-specific evidence and litigation-source documents, including local judgment copies not yet promoted to G100.	Universal authority or proposition approval.
C30	Case-selected propositions, authority classification, factual predicates, later-case application, rival analysis, procedural use, remedy bridge and bundle status.	Uncontrolled raw archive dump or silent amendment of G100 or G200.

4. ACCEPTED G100 DOCUMENT TYPES

Type code	Accepted document	Control
JUDGMENT	Official or court-approved written judgment.	Preferred canonical source.
APPROVED-TRANSCRIPT	Approved transcript of oral judgment or reasons.	Canonical where no written judgment exists or the approved transcript is the decision record.
TRIBUNAL-DECISION	Official tribunal determination or decision.	Tribunal, members, date, stage and status must be identified.
LAW-REPORT	Authoritative report or verified historical report where no official judgment is available.	Report citation, provenance and completeness required.
COMPANION-ORDER	Order inseparably linked to the judgment and required to understand the disposition or relief.	Companion only; it does not replace the reasons.
COMPANION-SUMMARY	Official press summary or official case summary.	Companion only; never the canonical proposition source.
SEPARATE-OPINION	Separate concurrence or dissent published independently from the main decision file.	Must be linked to the principal decision and separately classified in G200.
FOREIGN-JUDGMENT	Foreign judicial decision retained for comparative or persuasive use.	Jurisdiction and non-binding status must be explicit.

5. EXCLUDED OR QUARANTINED MATERIAL

Legislation, statutory instruments, rules, practice directions and government guidance belong in G200 source control rather than the G100 judgment archive.
Pleadings, witness statements, skeleton arguments, submissions, correspondence, evidence and case orders without reasons remain in C20 unless a limited companion-order classification applies.
Blogs, Wikipedia pages, practitioner notes, articles, textbooks, academic papers and advocacy analyses are secondary material and are not G100 judgments.
Law Commission papers, parliamentary briefings, administrative forms and other non-judicial historical sources must be preserved in the appropriate source system and linked from G200 where relevant.
Unapproved transcripts, unattributed OCR, incomplete scans and files whose identity, completeness, approval or provenance cannot be established remain quarantined.
A file containing advocacy annotation, conclusions, highlighting, mixed commentary or altered source text must not be designated the clean canonical judgment merely because the underlying decision is authentic.
Annotated or mixed files must be preserved as annotated research copies, legacy items, duplicates or quarantine records while a clean canonical copy is obtained where possible.
Duplicate copies remain preserved, but one canonical public link must be selected and every duplicate linked to the same stable G100 decision ID.

6. SOURCE-STATUS AND FILE-CONDITION CONTROL

Status	Meaning	Permitted use
S1 — OFFICIAL	Judiciary, National Archives, court, tribunal or other official judicial source.	Preferred canonical source.
S2 — APPROVED	Judge-approved transcript or approved judgment supplied through an authorised route.	Canonical where appropriate.
S3 — AUTHORITATIVE REPORT	ICLR or another authoritative report, including verified historical reports.	Canonical where no official decision file is available.
S4 — RELIABLE ARCHIVE	BAILII or another reliable archive reproduction whose identity and completeness are confirmed.	Usable subject to source preference and verification.
S5 — SECONDARY COPY	Readable reproduction, scan, OCR or third-party copy without complete provenance.	Research only; replace before final use where possible.
Q — QUARANTINE	Identity, completeness, approval, provenance, alteration or publication status unresolved.	Not treated as canonical and not used to verify a G200 proposition.

The source-status code must be recorded separately from file condition.

Permitted file-condition descriptions include:

CLEAN;
SEARCHABLE;
IMAGE-ONLY;
OCR-DERIVED;
ANNOTATED;
HIGHLIGHTED;
INCOMPLETE;
REDACTED;
DAMAGED; and
CONDITION-UNKNOWN.

A source may be official but unsuitable as the clean canonical public copy if it has been materially annotated or altered.

7. G100 ID AND FILENAME STANDARD

Every judicial decision receives one stable human-readable G100 identifier:

G100-J0001
G100-J0002
G100-J0003

The G100 ID remains stable when a better source copy is obtained.

The filename begins with the page code and stable decision ID. Fields are separated by underscores. Short-case-name words may be joined by hyphens.

Do not insert advocacy propositions, conclusions, remedy assertions or commentary into filenames.

G100_J0001_2019_UKSC_38_Cape-v-Dring_JUDGMENT_OFFICIAL.pdf

G100_J0002_2023_J90SA002_Leighton-v-Bristow-and-Sutor_APPROVED-TRANSCRIPT_APPROVED.pdf 

G100_J0003_1765_KB_Entick-v-Carrington_LAW-REPORT_AUTHORITATIVE.pdf

G100_J0001_C01_2019_UKSC_38_Cape-v-Dring_COMPANION-SUMMARY_OFFICIAL.pdf

G100_J0001_O01_2019_UKSC_38_Cape-v-Dring_COMPANION-ORDER_OFFICIAL.pdf

G100_J0001_D01_2019_UKSC_38_Cape-v-Dring_DUPLICATE-RETAINED.pdf

The preserved original filename must remain recorded even where a new G100 canonical filename is created.

A new canonical filename creates a new controlled binary. It does not authorise overwriting or deleting the parent file.

8. CANONICAL RECORD REQUIREMENTS

Every canonical G100 record must contain:

stable G100 decision ID;
neutral case or decision title;
neutral citation and report citation where available;
court or tribunal;
jurisdiction;
decision date;
judicial decision-maker or panel;
procedural stage;
document type;
source-status code;
file-condition status;
canonical filename;
preserved parent and original filename;
official source URL;
PeaceKeepers media URL where uploaded;
SHA-256 hash;
byte size;
page count;
searchability or OCR status;
completeness note;
reporting, confidentiality or publication restrictions;
duplicate group;
companion files;
replacement and supersession history;
related G200 proposition IDs;
related case-specific C30 records;
verification status;
reviewer; and
verification date.

9. NEUTRAL JUDGMENT ANALYTICAL MAP

G100 may record a neutral analytical map to help the reader navigate the source document.

The map may identify:

procedural stage;
inter partes outcome;
operative order or disposition;
relief sought;
relief granted, refused or reserved;
location of the material-facts section;
location of the legal issue or questions;
location of candidate reasoning passages;
location of alternative reasoning;
location of observations not apparently required for the outcome;
dissent, concurrence or separate opinion;
companion-order location; and
official summary location.

NAVIGATION-ONLY CONTROL | The analytical map records where material appears. It does not verify:

that the located reasoning was necessary to decision;
the case-specific ratio;
the binding principle of law;
the justified level of generality;
obiter or dissent classification;
later treatment;
Appendix A consistency or displacement; or
application to a later case.

Those classifications require G200 verification and, where relevant, C30 application.

10. OUTCOME, REASON AND PRINCIPLE SEPARATION

The following controls must remain separate:

the canonical judicial-decision source;
the inter partes outcome or operative order;
the material facts and issue addressed;
the location of candidate judicial reasoning;
the proposition of law formulated from the source;
the legal reason verified as necessary to decision;
the case-specific ratio decidendi;
the binding principle of law at the justified level of generality;
obiter, dissent and derived propositions; and
application to the separately proved facts and remedy of a later case.

G100 controls items 1–4 as source and navigation records.

G200 controls items 5–9 through primary-source, hierarchy, ratio, limitation, later-treatment and Appendix A verification.

C30 controls item 10 and the case-specific procedural use, rival application, remedy bridge and Bundle Approved status.

The disposition is not the ratio. A headnote is not the ratio. G100 storage is not ratio verification.

11. RELATIONSHIP WITH G200 AND C30

G100 answers:

What is the canonical judicial-decision source, and where are the documentary components located?

G200 answers:

What proposition of law, necessary reason, case-specific ratio, binding principle, obiter, dissent, derived proposition, quotation, limit, later treatment and transposition has been verified from that source?

C30 answers:

How does the verified authority apply to the separately pleaded and proved facts, procedural stage, rival constructions, cause of action, remedy and bundle requirements of the individual case?

No G100 filename, link label or archive description should contain an argumentative proposition such as:

void orders;
no supremacy;
fatal flaw;
extortion;
automatic nullity;
unlawful court; or
binding proof.

Such descriptions must be removed from the canonical archive title. Any legally supportable proposition must be formulated neutrally, verified in G200 and applied separately in C30.

No case-specific proposition is promoted into G200 merely because it was useful or relied upon in one case. Universal promotion requires UAP control.

12. PUBLIC CANONICAL ARCHIVE INDEX FORMAT

The canonical public archive should be organised by jurisdiction and court, then by year.

Each row should contain:

G100 ID	Neutral case or decision	Citation	Court	Date	Stage	Type	Source status	File condition	Canonical download
G100-J____	[Neutral title]	[Neutral or report citation]	[Court]	YYYY-MM-DD	[Stage]	[Type]	[S1–S5 / Q]	[Condition]	PDF

The public page may retain a searchable legacy section during migration, but it must remain clearly labelled as non-canonical and unverified.

13. LEGACY ARCHIVE MIGRATION STATUS

The pre-control archive contains a large flat list of links. It includes duplicates, non-judgment materials, inconsistent titles, advocacy annotations, multiple source qualities and some external webpages rather than clean judgment PDFs.

No existing source file is to be deleted, overwritten or silently renamed.

During migration:

retain the existing list under the controlled legacy heading;
import each title and URL into the G100 Judgment File Register;
assign a migration classification;
preserve every source and duplicate relationship;
create a new canonical binary only where required;
update the public canonical index; and
record the exact migration delta.

An entry remains legacy or quarantined until its identity, provenance, completeness, document type, stage, status, canonical source and duplicate relationship are confirmed.

14. MIGRATION ORDER

Freeze destructive changes and preserve all current files and links.
Import each legacy title and URL into the G100 Judgment File Register.
Classify the item as canonical candidate, duplicate, companion, annotated copy, non-G100 transfer, quarantine or broken link.
Verify case identity, court, citation, decision date, stage, source provenance, completeness and publication status.
Select the best canonical copy under the source-status and file-condition controls.
Assign or confirm the stable G100 ID.
Create a new G100-coded canonical filename as a new binary where required.
Record the original filename, parent, duplicate group, byte size, SHA-256 and replacement history.
Complete the neutral analytical map without verifying ratio or principle.
Update the public canonical table.
Cross-link verified propositions in G200 and case use in C30.
Only after link and hash verification, remove an obsolete duplicate link from the public legacy display while retaining the underlying source.
Clear caches and complete the G100 web-verification record.

15. CONTRIBUTION AND INTAKE

A request for a missing judgment should identify, so far as possible:

case name;
court or tribunal;
neutral or report citation;
decision date;
procedural stage;
source location; and
reason the decision is required.

A submitted file is not automatically canonical.

It enters the intake register and remains unverified until identity, provenance, completeness, approval, source status, file condition, reporting restrictions and duplicate relationship have been checked.

Personal data, reporting restrictions, statutory prohibitions, anonymity orders and publication restrictions must be reviewed before public upload.

A confidential, restricted or unredacted judicial source may be preserved internally without being made a public G100 download.

16. G100 ACTIVE FILE REGISTER

ACTIVE STATUS | The files below are the active G100 v1.01 control set at component revision v1.01B. The G100 methodology release remains v1.01. The J90SA002 source-identity correction is preserved. No judgment-source binary is altered by this component closure.

Order	Canonical filename	Purpose
00	MLSP_G100_CORE_00_Full_Universal_Judgment_Archive_Control_Pack_v1.01B.zip	Complete active G100 pack.
01	MLSP_G100_CORE_01_Archive_Readme_v1.01B.docx	Start-here Readme.
02	MLSP_G100_CORE_02_Universal_Judgment_Archive_and_Record_Control_Protocol_v1.01B.docx	Judgment archive and record protocol.
03	MLSP_G100_CORE_03_G100_Web_Implementation_and_Verification_v1.01B.docx	Web implementation and verification.
TEMPLATE-01	MLSP_G100_TEMPLATE_01_Judgment_File_Register_v1.01B.xlsx	Judgment file register.
TEMPLATE-02	MLSP_G100_TEMPLATE_02_Judgment_Intake_and_Verification_Form_v1.01B.docx	Intake and verification form.

17. VERSION AND SUPERSESSION CONTROL

G100 v1.01 is the current effective G100 baseline under UVS-0005. It is governed by G000 / MLSP v1.02 and supersedes G100 v1.00 for active universal judgment-archive control.

G100 v1.01 is an operational and schema release forming part of the coordinated UVS-0004 universal release. Its current active component set is CORE 01–03, TEMPLATE 01, TEMPLATE 02 and the complete pack at component revision v1.01B. The earlier v1.01 and v1.01A component files remain preserved as controlled parents.

COMPONENT CORRECTION RECORD | During final source-identity verification, the Leighton worked filename example was found to contain the unrelated neutral citation [2023] EWHC 2355 (KB). The example was corrected to identify claim J90SA002 and no neutral citation.

CORE 01, CORE 02 and CORE 03 and the complete G100 pack were therefore reissued as v1.01A component revisions. The G100 methodology release remains G100 v1.01. All earlier v1.01 component binaries and the v1.01 full pack remain preserved as superseded pre-publication parents and must not be overwritten or represented as the active release set.

It adds or confirms:

neutral judgment analytical mapping;
separation of source, outcome, reasoning, proposition, ratio, principle and later application;
source-status and file-condition separation;
clean-source and annotated-copy control;
procedural-stage metadata;
G100/G200/C30 storage boundaries;
consolidated output files;
parent-preservation and supersession control;
downloaded-hash verification; and
case-adoption control.

G100 v1.01 does not silently alter, delete or rename any judgment file or legacy source.

All v1.00 control files and all judgment-source parents remain preserved.

G100 v1.01 became effective after completion of the following release conditions:

the candidate page text has been approved;
the final control files have been generated;
the local manifest and hashes have been completed;
the new files have been uploaded without overwriting their parents;
the candidate page and links have been updated;
applicable caches have been cleared;
ordinary-browser and private-browser checks have passed;
automated retrieval has been checked where available;
every release-critical file has been downloaded and hash-compared;
G000 / MLSP v1.02 has been formally released;
the G100 UVS and UWR records have been completed; and
the project owner has recorded G100 v1.01 as effective.

Release of G100 v1.01 does not cause any case to adopt it. Each C00 must separately record adopt, defer or decline, together with every affected C30 record and downstream regression requirement.

POST-ACTIVATION COMPONENT CLOSURE | UFB-0010 and UCH-0016 reissue the complete active G100 set as component revision v1.01B so that live status, current URLs, G000 CORE 10, register filenames, manifests and hashes are internally consistent. The G100 methodology release remains v1.01. Every parent remains preserved.

18. G100 v1.01 ACTIVE DOWNLOADS

ACTIVE COMPONENT STATUS | These are the current G100 v1.01 controlled downloads at component revision v1.01B. Public verification is complete only when the downloaded full pack matches the approved SHA-256.

Main download

Universal core and templates

19. UNIVERSAL CROSS-LINKS

Code	Page	URL
G000	Universal MLSP methodology	https://peacekeepers.org.uk/mslp-universal-v1-02/
G100	Universal judgment-PDF archive	https://peacekeepers.org.uk/g100-judgments/
G200	Universal propositions of law and pinpoint register	https://peacekeepers.org.uk/g200-v1-01-propositions-of-law/

The G100 v1.01 page is the current universal judgment-archive page. G100 v1.00 remains publicly preserved at its previous controlled URL as version history.