BURKE v JACOBS [2026] — CASE30 AUTHORITIES / PROPOSITIONS / VERIFICATION / BUNDLE STATUS

Page code: C30
Controlled title: BvJ 2026 — Case30 Authorities / Propositions / Verification / Bundle Status
URL: https://peacekeepers.org.uk/bvj-2026-authorities/
Current active baseline: BVJ_00_C30_Authorities_Page_Index_v1.03

Current web/control revision:
v1.03K6F3A.

Current C00 decision child:
BVJ_00_C00_Chat02_v1.03K6E2_Qualified_Acceptance_Section65_v1.03K6F2A_Adoption_and_Chat03_Reauthorisation_Control_Patch_v1.03K6F3.docx

Current authority/application workstream:

Chat 03 v1.03K6F3 —
source-level application, order and evidence audit authorised /
pending verified user launch.

Accepted law/gateway parent:

Chat 02 v1.03K6E2 —
qualified accepted / inactive / reopenable.

Status:

Chat 02 v1.03K6E2. Chat 03 v1.03K6F3 authorised/pending verified launch. No authority promoted,  C30 Verified or Bundle Approved.

Chats 04–05 locked.

Governed by:

G000 / MLSP v1.02 — component v1.02A;

G100 v1.01 — component v1.01B;

G200 v1.01 — component v1.01A;

CORE 10;

Burke G150 local pilot v1.03K5B.

Web revision token:
BVJ-C30-v1.03K6F3A-20260726T2236-BST

 

1. PURPOSE AND BOUNDARY

C30 controls the selection, classification, verification, citation and bundle status of authorities proposed for use in Burke v Jacobs [2026].

A source link on this page does not establish that a proposition, quotation or pinpoint is correct. No authority is approved for final filing unless Chat 05 verifies the primary source, current status, exact proposition, ratio/obiter classification, quotation, pinpoint, limitations and later treatment, and then marks the authority C30 Verified and Bundle Approved for the identified filing.

Canonical judgment and approved-transcript files belong in G100. Universally reusable verified propositions and pinpoints belong in G200. BVJ evidence belongs in C20. Chat analyses and implementation records belong in C10. C00 records master status but does not independently verify authority propositions.

2. UNIVERSAL AND CASE CONTROL PAGES

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

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

G200: https://peacekeepers.org.uk/g200-v1-01-propositions-of-law/

C00 — Case00 Master Control Page: https://peacekeepers.org.uk/bvj-2026-master/

C10 — Case10 Chat Source Vault: https://peacekeepers.org.uk/bvj-2026-source-vault/

C20 — Case20 Evidence: https://peacekeepers.org.uk/bvj-2026-evidence/

C30 — Case30 Authorities / Propositions / Verification / Bundle Status: https://peacekeepers.org.uk/bvj-2026-authorities/

3. STATUS LADDER

  1. Candidate.
  2. Primary source linked.
  3. Primary text checked.
  4. Source and current-status checked.
  5. Proposition and classification checked.
  6. Quotation and pinpoint checked.
  7. Limits, adverse authority and later treatment checked.
  8. C30 Verified under the currently adopted case-specific methodology.
  9. Bundle Approved for an identified filing, document and tab destination.
  10. Suspended / Superseded / Rejected.

C30-V001–C30-V022 and VP-05-001–VP-05-026 are presently controlled as:

SOURCE TEXT AND PRIOR VERIFICATION PRESERVED / FULL PRIMARY-AUTHORITY AND C30 RERUN PENDING

The v1.03I/v1.03J primary-source identities, hashes, quotations, pinpoints, limitations and adverse constructions remain preserved.

No previous proposition, ratio, principle, application or remedy classification is operative merely because it was accepted before v1.03K2.

Chat 05 must reopen the current primary sources and complete the full adopted methodology after Chat 00 accepts Chat 04.

No authority is Bundle Approved.

3.1 — CHAT 05 PRIMARY-SOURCE WORK PRESERVED

Chat 05 completed the v1.03I omnibus primary-authority verification.

C00 accepted and preserved:

  • C30-V001–C30-V022;
  • VP-05-001–VP-05-026;
  • the reconciled statuses of AV-001–AV-052; and
  • the reconciled statuses of VR-02-001–VR-02-015.

The following remain preserved:

  • exact primary source and version;
  • source identity and hash;
  • court, date and procedural stage;
  • quotation and pinpoint;
  • source-status and later-treatment checks;
  • limitations and qualifications;
  • adverse authority and competing construction;
  • factual and procedural source gates.

Preservation of that work does not itself complete the adopted G200 case-specific classification.

3.2 — FULL CHAT 05 / C30 RERUN REQUIRED IN SEQUENTIAL ORDER — v1.03K2A

The former targeted C30 / Chat 05 regression route is superseded.

Chat 05 is locked until Chat 00 has accepted the complete reruns of Chats 01, 02, 03 and 04.

The full Chat 05 rerun must separately record source text, procedural stage, material facts, legal issue, legal source, necessary reason, case-specific ratio, justified principle, obiter/dissent, derived principle, later treatment, transposition, BVJ application, remedy and status.

C00 adopted:

  • G000 / MLSP v1.02 — active component revision v1.02A;
  • G100 v1.01 — active component revision v1.01B; and
  • G200 v1.01 — active component revision v1.01A

on 22 July 2026 at 11:03 BST, with no local variance.

The full Chat 05 / C30 rerun must separately record:

  • inter partes outcome;
  • material facts;
  • legal issue;
  • procedural stage;
  • recognised legal source;
  • proposition of law;
  • legal reason adopted as necessary to decision;
  • case-specific ratio decidendi;
  • binding principle at the justified level of generality;
  • retained material predicates;
  • enacted text and judicial construction;
  • obiter and dissent;
  • derived proposition;
  • quotation and pinpoint;
  • adverse and later authority;
  • limits and exceptions;
  • transposition or analogy;
  • BVJ-specific factual application;
  • right or power;
  • corresponding duty;
  • alleged wrong;
  • cause of action or review route;
  • causation;
  • damage or prejudice;
  • remedy;
  • defence and discretion.

Permission-stage, interlocutory and threshold decisions must not be promoted into final merits determinations.

No factual or evidential gap is cured merely because a legal source or universal proposition has been verified.

No authority is Bundle Approved.

3.3 — MANDATORY CORE 10 CONTROL

Apply the same source discipline, impartiality, reasoning standard and duty to identify apparent breaches to every authority, court, office, party and institution.

A material apparent breach must identify:

  • the person or office;
  • exact duty and source;
  • legal elements;
  • act or omission;
  • evidence;
  • contrary material;
  • required state of mind;
  • classification as proved, arguable, disputed, unverified or source-blocked; and
  • lawful procedural route.

Do not allege dishonesty, bad faith, misconduct, contempt, criminality or breach of oath unless the elements and evidence are separately established.

Every point of law must meet United Kingdom Supreme Court quality.

Every factual and evidential application must meet appellate-court quality.

Reasons must close the chain:

source → proposition → classification → material facts and proof → application → conclusion → consequence.

 

4. CURRENT LINKED SOURCE SET

C30-S001 — Powys County Council v Hurst [2018] EWHC 1684 (Admin). Primary judgment verified.

The binding ratio is confined to the conclusion that a council-tax liability order is not a judgment debt for conversion into the alternative Attachment of Earnings Act / County Court attachment route.

The judgment did not determine the availability of every Schedule 12 power or every CPR Part 84 question.

C30-S002 — Leighton v Bristow & Sutor, J90SA002, 20 September 2023. Approved first-instance transcript verified with express limits.

The exact existence, reasonable-belief and paragraph 26 propositions are recorded in C30-V017.

The case did not decide general liability-order invalidity or the corporate proper-defendant issue.

C30-S003 — Peacekeepers Foundation v LKMC and LCC [2025] EWHC 1493 (Admin). Permission-stage Administrative Court proposition verified with status qualification.

The liability-order reasoning is not a final trial determination.

The reported Court of Appeal status must be refreshed immediately before any filing or bundle use.

C30-S004 — Burke v Bristow & Sutor, claim 543MC655, 7 May 2025. Approved County Court transcript verified for its narrow pleading and proper-defendant proposition.

The related-party issue was expressly not determined.

No estoppel, abuse or prior-case application is permitted while M-021/M-022 remain open.

C30-S005 — TCEA 2007 section 63.

C30-S006 — TCEA 2007 Schedule 12 paragraph 2.

C30-S007 — TCEA 2007 Schedule 12 paragraph 7.

C30-S008 — Taking Control of Goods Regulations 2013 regulation 2.

C30-S009 — Taking Control of Goods Regulations 2013 regulation 7.

C30-S010 — Taking Control of Goods Regulations 2013 regulation 8.

Text availability is not verification of the proposed consequence.

5. REQUIRED SOURCE ADDITIONS

The principal primary-law verification work is complete.

Remaining source and bundle-control requirements include:

– the complete M-021/M-022 prior-case record before estoppel or abuse use;
– the case-specific factual records identified in C00/C20;
– an appellate-status refresh for Peacekeepers immediately before filing;
– the best authorised or reported bundle copy of each older authority selected for use;
– an identified hearing, document and tab destination before Bundle Approval.

No case-specific factual gap is cured merely because the governing legal proposition has been verified.

6. AUTHORITY AND PROPOSITION CONTROL

The preserved v1.03J verification and proposition working statuses are recorded in BVJ_00_C30_Chat05_Verification_and_Proposition_Adoption_Register_v1.03J, subject to the current §3 targeted reclassification status.

Primary-text observations are separated from ratio, obiter, inference, claimant construction and competing construction. In particular, the warrant, consent, paragraph 14, paragraph 15, CPR Part 84, enforcement-agent-office, named-agent, paragraph 7(3), paragraph 26, paragraph 66 and trespass propositions remain separately classified and must not be collapsed into verified law.

The linked v1.03J register ( BVJ_00_C30_Chat05_Verification_and_Proposition_Adoption_Register_v1.03J) remains the preserved historical verification and proposition working-status record. It must be read subject to the current §3 status and does not itself complete the adopted G200 case-specific reclassification.

 

7. LIABILITY-ORDER AND COURT-IDENTITY CONTROL

The verified legal architecture distinguishes:

– the underlying liability;
– judicial satisfaction or adjudication under regulation 34(6);
– the mandatory Rule 66 court record;
– Rule 68 or other evidential proof;
– maker and bench identity;
– bulk-list attribution;
– debtor, account, amount and costs attribution.

The former prescribed Form A/B/C theory is rejected for post-1 October 2003 liability orders.

Open-justice authority verifies the principle that judicial decision-makers should ordinarily be identifiable.

The absence of a name from one derivative extract does not, without more, establish that no adjudication occurred or that the order is automatically
a nullity.

Case-specific proof, attribution, invalidity and cure remain subject to M-015A–M-015L and the exact verified propositions in the adoption register.

8. REJECTED AND SUPERSEDED FORMULATIONS

The page must not state as verified law that: every post-2003 liability order requires a separate physical paper instrument; a certified extract has no statutory evidential status; absence of a judge’s name on the face of an extract automatically nullifies every order; Powys conclusively excludes every Schedule 12 warrant route; paragraph 14 always requires consent; or CPR Part 84 is necessarily unavailable merely because CTAER does not name it. These formulations remain preserved in the rejected/superseded register with controlled replacements.

9. BUNDLE STATUS

No authority is presently Bundle Approved. A G100 source copy or G200 proposition does not automatically authorise its use in BVJ. The final bundle gate requires C30 relevance, context, verified citation, exact proposition, limits and a named bundle/tab destination.

10. PUBLIC C30 CONTROL DOWNLOADS

BVJ_00_C30_Full_Authorities_Page_Control_Pack_v1.03

BVJ_00_C30_Authorities_Page_Index_v1.03

BVJ_00_C30_Authorities_Page_Operating_Protocol_v1.03

BVJ_00_C30_Authority_Proposition_Verification_Register_v1.03

BVJ_00_C10_to_C30_Authority_Queue_Update_v1.03

BVJ_00_C10_to_C30_Legal_Proposition_Classification_Matrix_v1.03

BVJ_00_C10_to_C30_Liability_Order_Constitution_Record_Proof_Register_v1.03

BVJ_00_C10_to_C30_Magistrates_Court_Part18_Record_Access_Register_v1.03

BVJ_00_C10_to_C30_Court_Order_Constitution_Gateway_Register_v1.03

BVJ_00_C10_to_C30_Authority_Chain_Actor_Competence_Register_v1.03

BVJ_00_C30_Bundle_Status_Register_v1.03

BVJ_00_C30_G100_G200_C30_Source_Map_v1.03

BVJ_00_C30_Rejected_Superseded_Propositions_Register_v1.03

10.1 — CHAT 05 ACTIVATION AND VERIFICATION SCOPE

10.1.1 — CHAT 05 DOWNSTREAM HANDOFF

BVJ_00_C30_to_05_Downstream_Handoff_Chat05_Omnibus_Primary_Authority_Verification_v1.03I

10.1.2 — CHAT 05 AUTHORITY PRIORITY AND SCOPE MATRIX

BVJ_00_C30_Chat05_Authority_Verification_Priority_and_Scope_Matrix_v1.03I

10.2 — CHAT 05 COMPLETION AND C30 INGESTION — v1.03J

10.2.1 — C30 VERIFICATION AND PROPOSITION ADOPTION REGISTER

BVJ_00_C30_Chat05_Verification_and_Proposition_Adoption_Register_v1.03J

10.2.2 — CHAT 05 MASTER HANDBACK

The Chat 05 Master Handback, manifest and hash record are filed canonically in C10.

The Master Handback may be cross-linked here for authority-control inspection.

BVJ_05_C30_to_C00_Master_Handback_Chat05_Omnibus_Primary_Authority_Verification_v1.03I

10.3 — UNIVERSAL ADOPTION AND METHODOLOGY REGRESSION STATUS CONTROL — v1.03K1A

BVJ_00_C30_to_C10_Universal_Release_Methodology_Regression_Status_Control_v1.03K1A.docx

HISTORICAL PARENT STATUS

This v1.03K1A control is preserved as the former universal-adoption
and targeted-regression record.

The targeted Chat 05-first route was superseded before launch by the
complete sequential rerun activated under v1.03K2.

Current operation is governed by section 10.4 below.

No authority is Bundle Approved.

10.4 — FULL RERUN AUTHORITY-REVALIDATION STATUS CONTROL — v1.03K2A

BVJ_00_C30_to_C10_Full_Rerun_Authority_Revalidation_Status_Control_v1.03K2A.docx

Status: Prior source verification preserved. Full authority and C30 rerun pending in sequential order. No authority Bundle Approved.

10.5 — CHAT 01 ACCEPTED CANDIDATE CLUSTERS / CHAT 02 LAW AND GATEWAY RERUN — v1.03K6E1

PRESERVED HISTORICAL v1.03K6E1 STAGE RECORD

This section records the former Chat 02 launch stage. It no longer
governs current routing. Current routing is stated in the page header
and section 10.6.

Chat 01 v1.03K6D1 has been qualified accepted under ES-BVJ-0002.

The following remain candidate or pending authority clusters:

– CPR 12, CPR 13.2, CPR 13.3, CPR 3.4, CPR 16, CPR 17 and
conditional CPR 24;

– liability-order complaint, adjudication, maker, official record,
Rule 66/68 extract, attribution and amount;

– CTAER regulation 45 and the Schedule 12 enforcement route;

– section 63 qualification, paragraph 2(3) authorisation,
regulation 8 office function, paragraph 7(3), paragraph 26 and
paragraph 66;

– Burke v Bristow & Sutor, Leighton, Powys, Entick and Southern
Housing;

– Ashby v White, the 1704 writ-of-error materials, Westminster II
chapter 24 and the 1863 saving, Paty and the Aylesbury Men;

– harassment, misrepresentation and UK GDPR / DPA causes and
defences;

– George, Lumba and Vento remedy distinctions;

– technical breach of the peace, separately from wider
constitutional peace;

– abuse, estoppel and prior-case identity, subject to M-021.

Historical Chat 02 v1.03K6E launch controls:

1. BVJ_00_C10_to_02_Downstream_Handoff_Chat02_Final_Relevant_Law_and_Gateway_Tree_Rerun_v1.03K6E.docx

2. BVJ_00_C10_to_02_Chat02_Starter_Prompt_v1.03K6E.txt

3. BVJ_00_C10_Chat02_Launch_Implementation_and_Verification_v1.03K6E.docx

At the v1.03K6E1 stage, Chat 02 was required to identify:

source;
instrument;
legal character;
necessary reason;
ratio;
controlled principle;
derived proposition;
strongest adverse construction;
later treatment;
limits;
Burke transposition;
verification requirement.

At that stage, Chat 02 was not authorised to mark any authority C30
Verified or Bundle Approved.

Chat 05 remains locked pending Chat 00A acceptance of Chat 03 and
Chat 04 and a new versioned Chat 05 handoff.

No legal source cures a missing factual predicate merely because the
source itself is verified.

10.6 — SECTION 65 / PARAGRAPH 66 /
RIGHT–REMEDY VERIFICATION QUEUE — v1.03K6F3A

Operative interpretation control:

BVJ_00_C00_Additive_Section65_Right_Remedy_Ex_Debito_Control_v1.03K6F2A.txt

Current Chat 03 handoff:

BVJ_00_C10_to_03_Downstream_Handoff_Chat03_Final_Source_Level_Application_Order_and_Evidence_Audit_v1.03K6F3.docx

Chat 05 must later verify:

1. whether section 65 displacement extends to purported acts by an
unauthorised person;

2. whether absence of an authorised enforcement agent places an act
outside the statutory field;

3. whether paragraph 66 requires a proved enforcement-agent act
before related-party relief can arise;

4. the legal content of “the enforcement agent’s office” in
regulation 8;

5. the relationship between paragraph 7(3), regulation 8 and the
office–agent–account link;

6. section 63(6)–(7), including “purports to act”, corporate
attribution and mens rea;

7. the exact Ashby and Entick principles and modern limitations;

8. ex debito justitiae as remedial entitlement rather than a cause;

9. nominal, compensatory, non-pecuniary and aggravated damages;

10. whether independent harassment, data, misrepresentation,
trespass, restitution, declaratory or injunctive routes fall outside
section 65.

All propositions remain candidate / pending.

No authority is C30 Verified or Bundle Approved.

Chat 03 must not perform final Chat 05 verification.

11. LEGACY LINKS

Retain the present judgment and legislation links under neutral titles while G100 stable IDs and canonical links are completed. Retain the former MLSP authority guide/template only beneath a “Legacy / superseded control files” heading; the active universal controls are G000 and G200.

MLSP_Master_Authorities_Register_Guide_v1.01

MLSP_Master_Authorities_Register_Template_v1.01

12. IMPLEMENTATION AND VERIFICATION

C30 page-implementation records are retained in the C10 Chat Source Vault under the v1.03 parent implementation pack and the v1.03A implementation correction pack.