WEB REVISION:
U00-WEB-20260904-01
TASK MARKER:
U00-WEB-ARCHITECTURE1
MLSP — MASTER LITIGATION SPECIALIST PROJECT
PAGE ID:
U00
PAGE FUNCTION:
Universal MLSP Control / Architecture / Knowledge-Governance Root
OWNER FUNCTION:
U00 — current active Universal Controller
STATUS:
ACTIVE UNIVERSAL CONTROL
AS-AT:
04 September 2026
1. PURPOSE
MLSP is the controlled architecture used to preserve, analyse, test, develop and apply legal knowledge across universal methodology, specialist legal subjects, judgment analysis and individual projects.
This page is the human-readable root of that architecture.
It is not itself:
a source of law;
a substitute for an Act, judgment, rule or other recognised legal source;
a case evidence repository;
a pleading;
or a substitute for the controlling hard-copy registers.
The actual source always controls.
2. CURRENT CONTROL STATE
CURRENT UNIVERSAL HARDCOPY:
U05 v0.02
STATUS:
CANONICAL / ACCEPTED / CURRENT / FROZEN
CURRENT UNIVERSAL SOFT METHOD STATE:
U00-SOFT-CURRENT-BEST-REGISTER-v0.04
CURRENT MANDATORY HANDDOWN KERNEL:
U00-MHK-v0.02
CURRENT G150 STATUS:
DEVELOPMENT / NON-OPERATIVE AS UNIVERSAL LAW
HARD CONTROL:
HARDCOPY CURRENT
≠
LATEST CURRENT-BEST LEARNING
REGISTER CURRENT
≠
TASK KNOWLEDGE COMPLETE
RESOURCE ACCESS
≠
KNOWLEDGE IMPLEMENTED
PROJECT CURRENT
≠
EVERY ACTIVE TASK CURRENT
3. CORE MLSP ORDER
TRUTH FIRST.
SOURCE FIRST.
EVIDENCE FIRST.
NECESSARY LEGAL REASON FIRST.
REASONS FIRST.
CONSEQUENCE LAST.
The controlling analytical chain is:
SOURCE
→ PROPOSITION
→ NECESSARY LEGAL REASON
→ CASE RATIO
→ BINDING PRINCIPLE AT THE JUSTIFIED LEVEL
→ APPLICATION TO SEPARATELY PROVED FACTS
→ CONSEQUENCE
OUTCOME
≠
RATIO
CASE FACT
≠
EVIDENCE
EVIDENCE
≠
INFERENCE
INFERENCE
≠
LEGAL CONCLUSION
ALLEGATION
≠
PROVED FACT
NOT PROVED
≠
FALSE
OPPOSITE PROVED
is a separate conclusion.
4. UNIVERSAL ARCHITECTURE
U00 — UNIVERSAL CONTROL
│
├── U05 — UNIVERSAL KNOWLEDGE REGISTER
│
│ Current accepted universal hard-copy knowledge.
│
│ https://peacekeepers.org.uk/mlsp/u05/
│
├── G000 — UNIVERSAL METHODOLOGY
│
│ Controls the method used to perform MLSP legal,
│ source, evidence and knowledge work.
│
│ https://peacekeepers.org.uk/mlsp/g000/
│
├── G100 — JUDGMENT SOURCE ARCHIVE
│
│ Custody of actual judgment / judicial-source objects.
│
│ SOURCE CUSTODY
│ ≠
│ JUDGMENT ANALYSIS
│
│ https://peacekeepers.org.uk/mlsp/g100/
│
├── G150 — JUDGMENT ANALYSIS DEVELOPMENT
│
│ Judgment analysis, recursive legal genealogy,
│ ratio-parent analysis, first-precedent development,
│ equitable/juridical-substance abstraction and gaps.
│
│ DEVELOPMENT / NON-OPERATIVE
│
│ https://peacekeepers.org.uk/mlsp/g150/
│
├── G200 — PROPOSITIONS / PINPOINTS
│
│ Controlled propositions and pinpoints which have
│ completed the required promotion route.
│
│ G150 CANDIDATE
│ ≠
│ G200 PROPOSITION
│
│ https://peacekeepers.org.uk/mlsp/g200/
│
├── CTSP — COUNCIL TAX SPECIALIST
│
│ Specialist owner for reusable Council Tax knowledge.
│
│ https://peacekeepers.org.uk/mlsp/ctsp/
│
├── JRSP — JUDICIAL REVIEW / PUBLIC LAW SPECIALIST
│
│ Specialist owner for reusable JR / Public Law knowledge.
│
│ https://peacekeepers.org.uk/mlsp/jrsp/
│
├── CCSP — CONTRACT SPECIALIST
│
│ Specialist owner for reusable Contract knowledge.
│
│ https://peacekeepers.org.uk/mlsp/ccsp/
│
└── LMSP — LEGAL LINKMAP SPECIALIST
Specialist relationship / dependency mapping where
distinct from G150 judgment genealogy.
5. UNIVERSAL / SPECIALIST / CASE BOUNDARY
MLSP separates:
UNIVERSAL METHOD
from
SPECIALIST LEGAL KNOWLEDGE
from
CASE FACTS / EVIDENCE / PROCEDURE
from
FINAL CASE APPLICATION.
The normal ownership route is:
U00
↓
SPECIALIST OWNER
↓
PROJECT / CASE CONTROLLER
↓
CHILD FUNCTION
Reusable case learning travels back upward:
CHILD
↓
CASE / PROJECT CONTROLLER
↓
SPECIALIST OWNER
↓
U00
where genuinely universal.
Hard controls:
CASE FACT
≠
SPECIALIST LAW
SPECIALIST LAW
≠
UNIVERSAL METHOD
CASE DISCOVERY
≠
AUTOMATIC REGISTER ADOPTION
WEB ASSERTION
≠
LEGAL SOURCE
6. CURRENT KNOWLEDGE MODEL
MLSP uses separate but linked knowledge states.
A. ACCEPTED HARDCOPY
Formal accepted releases such as:
U05;
CT05;
and later accepted specialist registers.
B. CURRENT-BEST POST-HARDCOPY LEARNING
Accepted or qualified learning arising after the last hard-copy cut-off.
This remains separately identifiable until incorporated into a later accepted hard-copy release.
C. DEVELOPING / CANDIDATE KNOWLEDGE
Research hypotheses;
MAP propositions;
open genealogy edges;
GAPs;
QFP candidates;
source-blocked propositions;
development-only G150 material.
Hard control:
PRESERVED
≠
ADOPTED
CURRENT-BEST
≠
BINDING LAW
DERIVED PROPOSITION
≠
RATIO
MAP POSITION
≠
LEGAL AUTHORITY
7. ITERATIVE GAP-CLOSURE METHOD
MLSP is designed to improve iteratively.
Every material chat and controller acts both as:
WORKER
and
SENSOR.
During any material task, actively identify:
missing sources;
missing law;
missing evidence;
contradictions;
stale propositions;
missing qualifications;
negative knowledge not inherited;
missing genealogy nodes or edges;
currentness failures;
routing failures;
continuity failures;
method defects;
unpropagated learning.
The gap-closure loop is:
WORK
↓
MATERIAL GAP / DEFECT IDENTIFIED
↓
CLASSIFY
↓
IDENTIFY COMPETENT OWNER
↓
TARGETED SOURCE / ANALYSIS / TEST
↓
ACCEPT / QUALIFY / REJECT /
DEFER / SOURCE-BLOCKED
↓
UPDATE CURRENT KNOWLEDGE
↓
PROPAGATE TO AFFECTED TARGETS
↓
IMPLEMENT
↓
VERIFY
↓
UPDATE CURRENT TXT / HTML
WHERE MATERIAL
↓
CLOSE OR EXPRESSLY PRESERVE GAP
Hard controls:
IDENTIFIED GAP
≠
CLOSED GAP
KNOWN ERROR
+
ACCEPTED PREVENTION
must not be knowingly repeated.
A previously closed gap may reopen if:
new evidence;
new authority;
source correction;
contradiction;
better reasoning;
or a stage/currentness change
materially affects it.
8. FULL-PROCEDURE CONTROL FOR MATERIAL RUNS
Every material MLSP run must consciously traverse the complete applicable procedure.
A stage may return:
PASS
NO MATERIAL DELTA
NOT APPLICABLE
or
SOURCE-BLOCKED.
Full procedure does not mean unnecessary broad re-research.
It means the required gate was considered before proceeding.
The general sequence is:
GATE 0
IDENTITY / RECIPIENT / ROUTING
GATE 1
CURRENTNESS
GATE 2
TASK-KNOWLEDGE CENSUS
GATE 3
SOURCE LOCK
GATE 4
ISSUE / FACT / EVIDENCE DECOMPOSITION
GATE 5
CLEAN LEGAL / JUDGMENT EXTRACTION
GATE 6
JURIDICAL / EQUITABLE-SUBSTANCE ANALYSIS
where applicable
GATE 7
GENEALOGY / KNOWN-KNOWLEDGE REJOIN /
NEGATIVE KNOWLEDGE / GAP ANALYSIS
GATE 8
APPLICATION TO SEPARATELY PROVED FACTS
GATE 9
ADVERSE / QUALIFICATION /
DO-NOT-REVIVE CHECK
GATE 10
NEW LEARNING / MISS / ROOT-CAUSE REVIEW
GATE 11
DEPENDENCY / DISSEMINATION REVIEW
GATE 12
CONTINUITY / SUCCESSOR / AS-AT STATE
GATE 13
REASONED RETURN / EXACT NEXT ACTION
9. KNOWLEDGE INHERITANCE
The existence of knowledge in a register does not prove that a task actually inherited it.
For every material task:
CURRENT REGISTER
↓
TASK FUNCTION
↓
RELEVANT KNOWLEDGE EXTRACTION
↓
CURRENT LEARNING LOCK
↓
RECEIVER OMISSION CHECK
↓
IMPLEMENTATION
↓
PARENT VERIFICATION
Where material, a knowledge object travels with:
PROPOSITION
SOURCE / STANDING
PREDICATES
QUALIFICATION
ADVERSE MATERIAL
NEGATIVE / DO-NOT-REVIVE STATE
OPEN GAP
Hard control:
PROPOSITION WITHOUT ITS MATERIAL QUALIFICATIONS
≠
THE SAME KNOWLEDGE OBJECT.
10. LEGAL GENEALOGY
MLSP judgment and proposition development is not limited to a shallow:
MAP
→ PRINCIPLE
→ RATIO
structure.
Legal genealogy may recurse through unlimited justified levels:
MAP / HIGHER PROPOSITION
↓
PRINCIPLE
↓
SUB-PRINCIPLE
↓
SUB-SUB-PRINCIPLE
↓
SOURCE-SPECIFIC RULE
↓
CASE-SPECIFIC RATIO
↓
NORMALISED RATIO PROPOSITION
↓
LATER APPLICATION / QUALIFICATION
↓
LATER RATIO
↓
FURTHER PROPOSITION
↓
…
A ratio may therefore be both:
a descendant of earlier law;
and
an ancestor of later legal development.
One ratio or proposition may have:
one primary navigation parent;
plus
multiple necessary legal parents;
plus
separate supportive, persuasive or contextual relationships.
Hard controls:
NO ORPHAN RATIO
NO PREDETERMINED MAXIMUM GENEALOGICAL DEPTH
PRIMARY PARENT
≠
JURIDICAL PRIORITY
GENEALOGICAL DEPTH
≠
LEGAL AUTHORITY
COMMON JURIDICAL REASON
≠
DIRECT PRECEDENT ANCESTRY
11. EQUITABLE / JURIDICAL SUBSTANCE
MLSP uses equitable-substance analysis as a controlled substance-over-form abstraction method.
For a case-specific ratio ask:
WHAT IS THE SURFACE CASE FORM?
WHAT IS THE JURIDICAL SUBSTANCE?
WHAT FORM CAN BE REMOVED
WITHOUT REMOVING A MATERIAL LEGAL PREDICATE?
WHAT NECESSARY LEGAL REASON REMAINS?
WHAT IMMEDIATE OR HIGHER PARENT
DOES THAT REASON SUGGEST?
WHAT SOURCE / PEDIGREE SUPPORTS
THE PROPOSED ABSTRACTION?
Hard control:
EQUITABLE SUBSTANCE
MAY IDENTIFY A CANDIDATE BROADER REASON
but
EQUITABLE SUBSTANCE
DOES NOT ITSELF CREATE BINDING AUTHORITY.
12. SOURCE HIERARCHY AND DUE-PROCESS DEPENDENCY
MLSP keeps separate:
SOURCE / AUTHORITY HIERARCHY
and
THE DEPENDENCY CHAIN REQUIRED FOR LAWFUL LEGAL EFFECT.
Source hierarchy asks:
WHAT SOURCE OF LAW CONTROLS?
Due-process dependency asks:
WHAT LEGALLY REQUIRED STEPS MUST EXIST
BEFORE THE CLAIMED LEGAL EFFECT
CAN LAWFULLY ARISE OR BE EXERCISED?
Current developing dependency model:
RECOGNISED SOURCE
↓
LAWFUL ACTOR / CAPACITY
↓
JURISDICTION / POWER
↓
MATERIAL LEGAL PREDICATES
↓
PROCEDURAL TRIGGER / NOTICE
↓
EVIDENCE / PROOF
↓
INDEPENDENT ADJUDICATION
↓
REASONS / NECESSARY LEGAL REASON
↓
INSTITUTIONAL RECORD / AUTHENTICATION
↓
LEGAL EFFECT / STATUS
↓
ENFORCEMENT / REMEDY
↓
REVIEW / CORRECTION
This remains a developing MAP / genealogy subject until its propositions are individually sourced, tested and classified at their proper juridical standing.
13. WEB / TXT / HARDCOPY MODEL
The MLSP website is the primary human-readable current-state interface.
Formal accepted register files may remain in controlled local/offline archive.
The web page records:
the accepted hard-copy baseline;
the current readable state;
post-hardcopy current-best development;
gaps;
qualifications;
and current version/cut-off.
Developing methodology, MAP and genealogy objects may use:
VERSIONED TXT
+
CURRENT HTML
Formal register release remains a separate controlled process.
Hard controls:
HTML CURRENT VIEW
≠
FORMAL HARDCOPY REGISTER
TXT DEVELOPMENT OBJECT
≠
PROMOTED UNIVERSAL LAW
WEB PAGE
≠
PRIMARY LEGAL SOURCE
14. WEB UPDATE / VERIFICATION LOOP
The normal update process is:
VERIFIED WEB CURRENT
↓
PROJECT / CHILD WORK
↓
NEW LEARNING
↓
OWNER REVIEW
↓
COMPLETE REPLACEMENT TXT
↓
U00 / SPECIALIST VALIDATION
WHERE REQUIRED
↓
OPERATOR UPDATES WEB PAGE
↓
OWNER REOPENS EXACT LIVE URL
↓
REVISION / TASK MARKER / CONTENT CHECK
↓
WEB VERIFIED
↓
TODO CLOSED
Where a material approved TXT exists but the web page remains stale:
WEB UPDATE REQUIRED
remains on the operator TODO list until live verification passes.
15. VERSION / HISTORY CONTROL
Accepted parent/source objects are never overwritten.
A material change creates a new controlled version.
The current web view may be replaced with the new approved text.
Prior state remains preserved through:
controlled TXT history;
register/version history;
WordPress revision history;
and relevant transaction provenance.
Hard control:
LATEST
≠
NECESSARILY BEST
A successor version must identify why material predecessor knowledge was:
retained;
merged;
qualified;
rejected;
or superseded.
16. PRIVACY / CASE MATERIAL
The public MLSP web architecture is primarily for:
universal method;
specialist knowledge;
public-use development;
controlled legal genealogy;
and hard-copy/readable knowledge state.
Ordinary case evidence, personal data, private correspondence, litigation strategy and other case-specific material remain within controlled project/source environments unless a separate lawful publication decision is made.
CASE FILE
≠
PUBLIC WEB RESOURCE.
17. CURRENT DEVELOPMENT PRIORITIES
Current development includes:
1. human-readable universal / specialist web architecture;
2. G150 recursive legal genealogy;
3. Ignorance-of-the-Law developing MAP;
4. Due-Process Dependency developing MAP;
5. G000 current-method TXT / HTML state;
6. source-companion TXT architecture;
7. specialist-register readable-state development;
8. iterative gap closure and no-loss propagation;
9. periodic reconciliation of current readable state back into controlled hard-copy releases.
18. CURRENT CONTROL SUMMARY
UNIVERSAL HARDCOPY:
U05 v0.02
UNIVERSAL CURRENT-BEST METHOD:
U00-SOFT-CURRENT-BEST-REGISTER-v0.04
MANDATORY HANDDOWN KERNEL:
U00-MHK-v0.02
G150:
DEVELOPMENT / NON-OPERATIVE
COUNCIL TAX HARDCOPY:
CT05 v0.01-ADD4
WEB FUNCTION:
CURRENT HUMAN-READABLE CONTROL / INDEX / DISTRIBUTION LAYER
CASE DATA:
NOT STORED HERE MERELY BECAUSE A CASE DEPENDS ON MLSP KNOWLEDGE.
19. CURRENT WEB VERIFICATION
CURRENT WEB VERIFICATION:
PENDING — U00 LIVE VERIFICATION AFTER THIS REVISION IS PUBLISHED.
WEB REVISION:
U00-WEB-20260904-01
TASK MARKER:
U00-WEB-ARCHITECTURE1
20. CONTROL NOTE
MLSP is iterative.
The objective is not to pretend that the knowledge base is complete.
The objective is to:
preserve what is known;
identify what is not known;
make gaps visible;
close material gaps by source and reason;
preserve adverse and negative knowledge;
propagate accepted learning;
verify implementation;
and improve the current state without erasing the path by which it was reached.