Global000 — Universal MLSP Methodology Used by Every Case

SUPERSEDED CONTROLLED VERSION

This page preserves G000 / MLSP v1.01A as the previous controlled universal baseline.

It was superseded for active universal use by G000 / MLSP v1.02 on 21 July 2026 at 12:00 noon.

Current universal methodology:

https://peacekeepers.org.uk/mslp-universal-v1-02/

The historical body below is preserved as version history. Any wording within that preserved body describing MLSP v1.01A as “current”, “live” or “active” records its status before supersession and must not be read as the present universal baseline.

No existing case is treated as having adopted MLSP v1.02 unless its C00 separately records adopt, defer or decline.

Web revision token: G000-MLSP-v1.01A-HIST-20260721T1326-BST

Page code: G000

Controlled title: Global000 — Universal MLSP Methodology Used by Every Case

Subtitle: Universal Litigation Methodology and Source-Control Protocol

Current live baseline: MLSP v1.01A

Status: Live universal operating baseline

Supersedes for active G000 use: MLSP v1.01

Preserves: All v1.01 procedural modules, research annexes, source copies and worked examples

1. UNIVERSAL MANDATE

G000 is the universal methodology for establishing, controlling, analysing, progressing and closing any litigation, appeal, statutory proceeding, tribunal matter or related legal case-control project.

G000 applies irrespective of jurisdiction, cause of action, procedural application, party status or remedy. No individual case type or procedural route defines or limits the universal method.

Specific procedural routes, jurisdictions, case types and substantive subjects operate as subordinate modules. A project activates only the modules that are sourced and relevant. No module may displace the universal G000 controls.

Every project chat must read G000 before analysing, drafting, classifying evidence or relying on legal authority. G000 replaces reconstruction of the methodology from memory or prior chat history. It does not replace primary law, original case documents or the case-specific control record.

2. CORE RULE

CORE RULE | Truth first. Source first. Evidence first. Ratio/reason first. Reasons first. Consequence last.

3. APPENDIX A SOURCE-TO-CONSEQUENCE METHOD

Every conclusion must pass through the following controlled sequence:

source -> competence -> instrument -> gateway -> rights or interests affected -> procedure and natural justice -> material facts and proof -> authority and lawful reason -> reasons and open justice -> defect classification -> remedy and legal consequence.

No conclusion may be used to prove its own source, competence, factual foundation, procedural validity or consequence. Administrative practice, repetition, status, confidence, label or convenience is not proof of lawful authority.

4. UNIVERSAL CORE AND SUBORDINATE MODULES

The universal core applies in every project. Specialist modules are activated only where the source record establishes that they are relevant.

Layer	Function	Status rule
Universal core	Source preservation; factual and evidential control; chronology; issue architecture; legal gateway control; authority verification; decision and reasons audit; versioning; filing; publication.	Always active.
Procedural modules	Claim issue and service; jurisdiction; default/set aside; strike out; summary judgment; sanctions; amendment; disclosure; interim remedies; trial; appeal; judicial review; enforcement; costs.	Activate only when the procedural gateway is sourced or materially in issue.
Jurisdiction / case-type modules	Civil; public law; tribunal; magistrates court; criminal; family; insolvency; property; employment; statutory enforcement; other specialist forums.	Activate according to forum, enabling legislation and live proceeding.
Subject-matter modules	Instrument interpretation; contract; tort; statutory cause; constitutional/public-law control; data protection; harassment; misrepresentation; trespass; human rights; causation; quantum; interest; remedies.	Activate according to pleaded or proposed issues and supporting evidence.
Research annexes	Preserved detailed research used to supplement a live module.	Never treated as verified authority merely because preserved.
Worked examples	Prior-project illustrations.	Examples only; never imported as facts or law.

5. MODULE ACTIVATION CONTROL

Each module must be assigned one status: inactive, candidate, active, completed, superseded or parked.

A module becomes active only when its trigger, legal source, procedural relevance and required inputs are identified.

Every active module must state its scope, source documents, questions, evidence, authority queue, outputs, filing destination and downstream handoff.

A module may add detail but may not alter, waive or reverse the G000 source-first, no-memory, evidence and verification controls.

6. CONTROLLED WEB ARCHITECTURE

Code	Controlled page	Function	URL
G000	Global000 – Universal MLSP Methodology Used by Every Case	Universal methodology, setup, source-control protocol and module architecture.	https://peacekeepers.org.uk/mslp-universal/
G100	Global100 – Universal Judgment-PDF Archive	Canonical judgment and approved-transcript file archive. Not a proposition-verification register.	https://peacekeepers.org.uk/judgments-2/
G200	Global200 – Universal Propositions of Law / Pinpoint Register	Verified reusable propositions, ratios, limits, quotations and pinpoints.	https://peacekeepers.org.uk/mslp-propositions-of-law/
C00	[Case] – Case00 Master Control Page	Case facts, chronology, posture, version, missing-source and downstream control.	https://peacekeepers.org.uk/[case-slug]-master/
C10	[Case] – Case10 Chat Source Vault	Chat outputs, handbacks, handoffs, packs and archived versions.	https://peacekeepers.org.uk/[case-slug]-source-vault/
C20	[Case] – Case20 Evidence	Original case documents, evidence compilations, provenance and filing status.	https://peacekeepers.org.uk/[case-slug]-evidence/
C30	[Case] – Case30 Authorities / Propositions / Verification / Bundle Status	Case-selected authority propositions, status, limits and bundle destination.	https://peacekeepers.org.uk/[case-slug]-authorities/

7. RESERVED PAGE CODES

C40 is not part of the currently approved coding table. It is reserved and must not be created, named or linked unless separately defined and approved.

Secondary authority material remains controlled through G200 and the case-specific C30 page unless the architecture is formally amended.

8. THREE DISTINCT SOURCE HIERARCHIES

Do not confuse navigation/control pages with primary evidence or primary law.

Hierarchy	Controlled order
Control and navigation	G000 -> C00 -> C20 -> C10 -> C30 -> G200 -> G100.
Factual and evidential	Original court/source document -> authenticated official record -> native file and metadata -> exhibited copy -> derivative compilation -> party summary -> chat summary.
Legal authority	Current legislation and rules from official sources -> approved judgment or authoritative report -> Chat 05 verified proposition in G200/C30 -> G100 stored copy -> secondary commentary.

9. UNIVERSAL CASE LIFECYCLE

Intake and conflict-free case identification.
Source preservation and parent-document registration.
Procedural posture and jurisdiction control.
Chronology and date-field separation.
Evidence indexing, provenance and completeness audit.
Issue and potential-ground discovery.
Procedural and substantive gateway analysis.
Application, decision, judgment and order audit.
Authority verification and proposition control.
Detailed drafting, compression and filing destination control.
Bundle, service, compliance and order implementation.
Public redaction, publication and open-justice control.
Post-decision, appeal, enforcement and archival control.

10. UNIVERSAL CHAT / WORKSTREAM ARCHITECTURE

Workstream	Universal role	Prohibited shortcut
Chat 00	Master case control: facts, evidence, chronology, procedure, versions, conflicts, missing sources, compliance, sanctions, Appendix A and web control.	No final submissions unless expressly instructed.
Chat 01	All potential grounds and issues: pleading delta, amendments, alternatives, overlaps, weak and parked points.	No deletion because a point appears weak or inconvenient.
Chat 02	Relevant law and gateway trees: statutory text, rules, elements, procedural tests, remedy gateways and authority requests.	No party assertion converted into law.
Chat 03	Application, decision, judgment, order and evidence audit against the pleaded case, source record and gateway law.	No assumption that an omission or defect has a consequence before the gateway is identified.
Chat 04A-04Z	Separate issue-specific or ground-specific workstreams allocated after Chat 01.	No uncontrolled proliferation or duplicate ground ownership.
Chat 05	Primary-source authority verification, ratio/obiter, quotations, pinpoints, status, OSCOLA, G200/C30 and bundle approval.	No final use of an unverified authority proposition.
Chat 06	Final drafting, filing, bundle production, draft order, service, compliance and filing-destination consolidation.	No silent compression or loss of preserved points.
Chat 07	Open justice, public redaction, publication, privacy and public-safe derivatives.	No alteration of court-facing substance without controlled instruction.

11. MANDATORY OPERATING PRINCIPLES

Do not rely on memory.
Do not invent documents, dates, hearings, orders, quotations, authorities, pinpoints, facts or transcript content.
Preserve original source files and every superseded version. Never overwrite a source file.
Separate document date, creation/file date, transmission date, service date, filing date and court-seal date.
Distinguish source, fact, evidence, pleading, submission, concession, judgment, ratio, obiter, inference and opinion.
Treat informal hearing notes as transcript-confirmable unless and until an official transcript is obtained.
Preserve all potentially relevant grounds and classify weak, incomplete, overlapping, inconsistent, parked and missing-source points.
Use detailed-first and compressed-second drafting. Record what was removed or compressed.
No authority proposition, quotation or pinpoint is final until Chat 05 verifies the primary source, status, ratio, limits and pinpoint.
No module, chat, party or court label is self-proving. Identify source, competence, gateway, proof, reason and consequence.
State what the source says separately from what a party argues the source means.
Where a required source cannot be found, record the precise missing item and the case-control purpose for which it is needed.

12. NEW CASE SETUP RUN ORDER

Stage 1 – Load the universal method: read the G000 Readme, Project Settings Description, Standalone Continuation Primer and Universal Methodology Primer. Treat Appendix A as always live.

Stage 2 – Create the case web structure: C00, C10, C20 and C30. Link each page to G000, G100 and G200.

Stage 3 – Preserve and index the first source set: do not begin final analysis until the parent-document register, evidence register and missing-source log exist.

Stage 4 – Run Chat 00, then Chat 01, then Chat 02, then Chat 03. Create Chat 04 workstreams only after allocation. Run Chat 05 as soon as candidate authorities arise. Use Chats 06 and 07 only for their controlled functions.

Stage 5 – Activate procedural, jurisdiction and subject-matter modules only where the trigger and source are recorded.

Stage 6 – Update the web pages, clear caches, reopen each page, test every link and complete the verification record.

13. MANDATORY OUTPUT PACK

Impact Assessment.
Main Analysis / Register / Gateway / Ground Document.
Evidence Relied-On Register.
Parent-Document Contents List.
Filing Destination Register.
Missing Source List.
Authority Queue Update where law is used.
Chat 00 Handback.
Downstream Handoff.
Numbered Upload List.
Web Page Update Register covering G000, G100, G200, C00, C10, C20 and C30, including No update required entries.
Separate page-specific Update Note for every affected page.
Web Update Verification Record.
Copy-paste Source Vault wording.
Consolidated Handover.
Readme and ZIP where documents are generated.

14. FILE-NAMING AND DESTINATION CONTROL

Universal files:

MLSP_[PAGE CODE]_[CLASS]_[SEQUENCE]_[DOCUMENT TITLE]_v[VERSION].[extension]

Case files:

[CASE CODE]_[CHAT NUMBER]_[PRIMARY PAGE CODE]_[DOCUMENT TITLE]_v[VERSION].[extension]

The page code identifies the primary upload destination. Upload one controlled binary and cross-link it from secondary pages. Do not create duplicate binaries with different destination codes.

A renamed or corrected file is a new controlled version. Preserve the old file, record its parent and reason for change, update the live link, clear caches and verify the new link.

MLSP_G000_CORE_04_Universal_Litigation_Methodology_and_Source_Control_Protocol_v1.01A.docx
MLSP_G000_PROC_01_Civil_Early_Disposal_CPR13_CPR34_CPR24_Denton_AppendixA_Primer_v1.01.docx
BVJ_00_C00_Master_Case_Control_v1.03.docx
BVJ_00_C10_Consolidated_Handover_v1.03.docx
BVJ_00_C20_Evidence_Register_v1.03.docx
BVJ_05_C30_Authority_Verification_Register_v1.03.docx
BVJ_00_G000_Global000_Page_Update_Note_v1.03.docx

15. FILE CLASSES

Class	Meaning	Use
CORE	Universal methodology and mandatory operating files.	Always live.
PROC	Procedural route module.	Activate only when sourced and relevant.
JUR	Jurisdiction or forum module.	Activate according to forum and enabling law.
SUB	Substantive subject module.	Activate according to pleaded/proposed issue.
ANNEX	Preserved detailed research.	Supplement only; authority verification still required.
TEMPLATE	Reusable register, schedule or drafting template.	Copy into a project and populate.
SOURCE	Preserved original source copy.	Never silently alter.
EXAMPLE	Worked illustration from a prior project.	No factual or legal import without independent verification.

16. UNIVERSAL STARTER INSTRUCTION

UNIVERSAL STARTER INSTRUCTION

Use MLSP v1.01A as the universal operating methodology:

Global200 – Universal propositions of law / pinpoint register

Use G100, the universal judgment-PDF archive:

Global100 – Universal judgment-PDF archive

Use G200, the universal propositions-of-law and pinpoint register:

Global200 – Universal propositions of law / pinpoint register

Use the case-specific pages:

C00 — [Project Master Control URL]
C10 — [Project Chat Source Vault URL]
C20 — [Project Evidence URL]
C30 — [Project Authorities URL]

Do not rely on memory. Apply the Appendix A source-to-consequence
method. Preserve all possible grounds. Activate only sourced modules.
Distinguish source content from party argument. Do not use unverified
case-law propositions, quotations or pinpoints in final filing. Produce
the complete mandatory output pack unless expressly waived.

17. G000 ACTIVE FILE REGISTER

Order	Canonical filename	Class and purpose
00	MLSP_G000_CORE_00_Full_Universal_Methodology_Pack_v1.01A.zip	Full download pack. Archive/download-all only.
01	MLSP_G000_CORE_01_Pack_Readme_v1.01A.docx	Start here; scope, classes, supersession and run order.
02	MLSP_G000_CORE_02_Project_Settings_Description_v1.01A.docx	Universal project settings text.
03	MLSP_G000_CORE_03_Standalone_Seamless_Continuation_Primer_v1.01A.docx	Minimum complete operating baseline for a new session.
04	MLSP_G000_CORE_04_Universal_Litigation_Methodology_and_Source_Control_Protocol_v1.01A.docx	Full universal methodology manual.
05	MLSP_G000_CORE_05_Appendix_A_Standing_Control_Module_v1.01.docx	Always-live Appendix A control module; unchanged source content.
06	MLSP_G000_CORE_06_Generic_Chat_Setup_Prompts_v1.01A.docx	Universal Chat 00-07 and 04A-04Z prompts.
07	MLSP_G000_CORE_07_Authorities_and_Propositions_Control_Guide_v1.01A.docx	G100/G200/C30 authority system and verification guide.
08	MLSP_G000_TEMPLATE_01_Master_Authorities_Register_v1.01.xlsx	Reusable authorities/proposition template; unchanged source content.
09	MLSP_G000_CORE_09_G000_Source_Vault_Update_Note_v1.01A.docx	Upload order and copy-paste G000 update wording.
PROC-01	MLSP_G000_PROC_01_Civil_Early_Disposal_CPR13_CPR34_CPR24_Denton_AppendixA_Primer_v1.01.docx	Existing early-disposal master reclassified as a procedural module.
EXAMPLE-01	MLSP_G000_EXAMPLE_01_BVJ_2026_Test_Run_Setup_Note_v1.01.docx	Worked example only.
SOURCE-01	MLSP_G000_SOURCE_01_Appendix_A_Original_Source_Copy_v1.2.docx	Preserved Appendix A source.
ANNEX-A	MLSP_G000_ANNEX_A_Legal_Instrument_Interpretation_Master_Logical_Bridge_v1.01_preserved.docx	Instrument-interpretation research annex.
ANNEX-B	MLSP_G000_ANNEX_B_CPR24_Summary_Judgment_Master_Logical_Bridge_Additive_v2_v1.01_preserved.docx	CPR 24 detailed module.
ANNEX-C	MLSP_G000_ANNEX_C_CPR24_Integrated_Notes_Additive_Controls_v1.01_preserved.docx	CPR 24 integrated notes.
ANNEX-D	MLSP_G000_ANNEX_D_Proveable_at_Trial_MiniTrial_Quote_Verification_Notes_v1.01_preserved.docx	Trial-proof, mini-trial and quote-verification research.

18. VERSION AND SUPERSESSION CONTROL

MLSP v1.01A is the active G000 universal architecture correction. It supersedes MLSP v1.01 for universal setup, page structure, file classification and chat instructions.

The v1.01 early-disposal primer, Appendix A source, research annexes, template and worked example are preserved and reclassified; they are not silently rewritten or discarded.

The earlier BVJ_00_G000 draft correction pack is superseded and must not be uploaded as the final G000 replacement.

After implementation, clear all site and server caches, reopen G000, test every download and cross-page link, and complete the verification record before marking the update effective.