E-Petitions Investigation – Constitutional Challenge

📝 E-Petitions — Constitutional Investigation

A forensic investigation into the e-petitions system of the UK Parliament — examining how the ancient right to petition the High Court of Parliament has been captured, filtered, and effectively suppressed by an administrative gatekeeping mechanism operating outside the Known Laws and Customs of Parliament.

The investigation spans four documents covering: the staffing web of the Petitions Committee from 2006 to 2026, the forensic audit of rejected petitions and "Ghost IDs," the constitutional challenge to the legality of the rejection framework, and the formal challenge to Tony Vaughan KC MP on the creation of a New Privilege.

The Core Constitutional Claim: When a subject petitions the High Court of Parliament, their Prayer must be received. Since 2015, a "Team of Four" unsworn administrative staff — operating under a digital "Policy" designed with involvement from Number 10 Downing Street — have been intercepting, filtering, and deleting petitions before they ever reach the Table of the House. This is not a terms-of-service dispute. It is a violation of the Bill of Rights 1688 and the 1704 Resolution.

Download the full AI-readable Investigation Pack and upload it to Gemini 3.5 Flash with Extended Thinking (recommended), ChatGPT, Claude, or any other AI model to continue the investigation, verify the findings, or prepare a submission to the Petitions Committee, your MP, or a legal representative.

The pack contains 4 research documents (.txt), the Gemini Academic Grading Certificate (.jpg), and the Starmer petition images archive (.zip).

📦 Download Investigation Pack (.zip)

Section A

E-Petitions MOT — The Forensic Audit

Source: E-Petitions MOT — 262 pages. Forensic investigation of the Petitions Committee structure, staff network 2006–2026, rejection patterns, Ghost ID audit, and constitutional analysis. Graded A (First Class Distinction equivalent) by independent academic assessment.

Section A — Investigation Findings

A1 The "Team of Four" — Who Actually Runs the Petitions Filter

The e-petitions system was designed by the Procedure Committee in HC 235 (2014–15). Its founding memorandum stated: "I envisage that the Committee will be staffed initially by a team of four, at an estimated annual cost of around £200,000." That original cell — unsworn administrative staff, not elected Members — became the gatekeepers of the ancient right to petition the High Court of Parliament. Petition rejections are not decisions of the House. They are decisions of junior staff.

2015–2019 (Foundation): Anne-Marie Griffiths (Clerk), Paul Simpkin (Senior Assistant), Sean Harris (Committee Assistant), Emma McIntosh (Engagement), Fiona Whiteside (2nd Clerk).
2019–2024 (Expansion): Judith Boyce (Clerk), Lauren Boyer (2nd Clerk), James Clarke (Engagement Manager), Zoe Hays, Naomi Jurczak.
2024–2026 (Current): Laura Daniels / Sîan Woodward (Clerks), Sean Earley (Media), Isabel Buchanan and Sarah Priddy (Research).
Sean Harris's trajectory: From processing public grievances as a petitions assistant to the Speaker's Trainbearer — the most senior ceremonial role in the House. The same individual who managed the early filter is now in the Speaker's inner circle.

⚔ Unsworn Administrative Staff Are Determining What the High Court of Parliament Receives — Not the House Itself

A2 The Pre-History — Government Ran Petitions Before Parliament Did

Before 2015, there was no Parliamentary Petitions Committee. E-petitions were handled by the Prime Minister's Office — a civil service operation run from Number 10's own website. The shift from Government to Parliament in 2015 was meant to restore the ancient independence of the petition function. The investigation finds it did not. The "Policy" and rejection logic adopted by the new Parliamentary system bears the hallmarks of the same executive culture it was supposed to replace.

Era	Who Controlled Petitions	Key Change
2006–2011	Number 10 / Cabinet Office	PM's website; Government staff (e.g. Paul Howarth, Head of E-Petitions)
2011–2015	Leader of the House Office	HC 235 planned the transfer to Parliament; still Government-managed
2015–2026	Petitions Committee / "Team of Four"	Nominally Parliamentary — but rejection logic traced back to Number 10

⚔ The Transfer From Government to Parliament Was Structural, Not Constitutional — The Executive Culture Came With It

A3 The Ghost ID Audit — Sequential IDs, Missing Petitions, 404 Errors

The e-petitions database assigns sequential IDs to every petition submitted. By auditing the ID sequence and cross-referencing against the public-facing website, the investigation identifies a systematic pattern of "Ghost" petitions — petitions that were assigned an ID, then deleted or suppressed, leaving a 404 error where a public record should exist. The Government Digital Service and the Petitions Committee reported acceptance-to-rejection ratios of between 1:2 and 1:3 between 2012 and 2025.

The Grievance Gap: If 1 in 2 or 1 in 3 petitions is rejected, and the rejected ones are deleted from the public record, the House never sees the true scale of public dissatisfaction.
The "Ghost Effect": No record of the rejection = no accountability for the refusal. The administrative filter is self-concealing.
2006–2026 Total Suppressed: Based on the 1:2 ratio, the cumulative suppressed petition count across the investigation period runs into hundreds of thousands of unrecorded public prayers to Parliament.
The constitutional effect: If a petition is never "laid on the Table," the House never formally receives it. The subject's prayer is deleted as if it never existed.

"If there is no record of the complaint, there is no failure to address it. It's not just keeping secrets; it's editing the history of public dissent in real-time." — Investigation analysis, 2026

⚔ Ghost ID Audit Confirms Systematic Suppression of the Public Record — Hundreds of Thousands of Petitions Vanished

A4 The Hague/Rogers Logic — From Strickland Presumption to Administrative Exclusion

The investigation identifies a precise historical shift in the petitioning philosophy of the system — from the "Strickland Principle" (a presumption of reception: the ancient duty to receive all prayers touching upon Common Right) to the "Hague/Rogers Logic" (a presumption of administrative exclusion: petitions are managed, curated, and deleted by a digital policy team). This shift did not happen by Act of Parliament. It happened through an internal evolution of the rejection framework that research indicates originated from Number 10 and was adopted by the Cabinet Office and House Leader.

"Pre-2010: if you petitioned Number 10 about a matter of public concern, it was usually published. Post-2015: the 'Team of Four' almost universally reject these, citing digital Policy — even though no Act of Parliament authorises the Policy." — Investigation summary

⚔ Rejection Philosophy Shifted From Parliamentary Reception to Executive Management — No Statutory Authority for the Change

A5 The "Legislation Only" Trap — The Hard-Coded Rejection Standard

The Petitions Committee's rejection policy evolved through three identifiable eras. The final version — introduced in July 2024 — contains what the investigation calls the "Lying Mechanism": a clause that rejects any petition calling for the Secretary of State to exercise existing statutory powers (such as those under the Ancient Monuments and Archaeological Areas Act 1979), on the grounds that the petition is not calling to "amend that law." The Secretary of State's duty to act is set out in the 1979 Act. The staff use the "amend that law" suffix to block requests that are, constitutionally, Matters of Common Right.

Era A (2015–2019): Broad reception, limited rejection criteria — closest to the Strickland Principle.
Era B (2019–2024): "Legislation Only" restriction introduced — petitions requesting Executive action routinely rejected.
Era C (July 2024–present): "Amend that law" clause added — even petitions about existing statutory powers of the Secretary of State are blocked.

⚔ July 2024 Rejection Standard — A Categorical Legal Fallacy Encoded as Policy, Blocking Matters of Common Right

A6 Selective Admission — The "Shadow Filter" Exposed

The investigation identifies five petitions that were published and allowed to collect signatures despite requesting Executive action — the exact type of petition being rejected under the "Legislation Only" rule. This selective admission proves the rule is not applied consistently. It is a "Shadow Filter": a rule that exists not to ensure constitutional compliance, but to curate the "National Conversation" by removing petitions the system finds inconvenient.

Evidence standard: All five petitions were live on petition.parliament.uk during the same period as the rejections under investigation.
Constitutional significance: Inconsistent application of a rejection rule is itself a constitutional violation — it means the "Policy" is being applied selectively, not judicially.
"Honours" vs "Building": The investigation notes that while "Honours" petitions are the most rejected category overall, "Building and Land Use" petitions are the fastest-growing rejection category — the democratic black hole for community planning grievances.

⚔ Shadow Filter Confirmed — The Rejection Rule Is Applied Selectively, Not Judicially

A7 The Judicial Nature of the Prayer — A Human Cannot Pray to a Machine

In the tradition of English constitutional law, a petition is a "Prayer" — a formal judicial request to the highest court in the realm. Sir Edward Coke (4 Inst 11) established that Parliament's primary duty is the "Redress of Grievances" that cannot be resolved in lower courts. William Prynne documented that the "Writs and Petitions of Parliament" are part of its ancient judicial character. The investigation raises the fundamental constitutional point: a human subject cannot pray to a machine. The digital algorithm that processes and rejects petitions is not a judicial officer. It is not sworn. It has no authority to determine what the High Court of Parliament receives.

"The word 'Petition' is inseparable from the 'Prayer' — the formal request that begins: 'And your Petitioners, as in duty bound, shall ever pray...' A Prayer is addressed to a Minister — of justice, of the Crown, of Parliament. Not to a 'Terms of Service' policy document." — Investigation analysis

⚔ An Unsworn Digital Filter Cannot Receive a Judicial Prayer — The Delegation of Reception Is Constitutionally Invalid

A8 The PHSO Jurisdiction Gap — Parliamentary Privilege Blocks the Complaint Route

The Parliamentary and Health Service Ombudsman (PHSO) operates under the 1967 Act to investigate "maladministration" by Government Departments. The Petitions Committee staff are House of Commons staff — not Government staff. Under the 1967 Act, the Ombudsman generally cannot investigate the House of Commons because of Parliamentary Privilege. This creates a closed loop: the subject cannot petition Parliament (filter blocks it), cannot complain to the Ombudsman (no jurisdiction), and cannot use judicial review (Exclusive Cognisance prevents it). Every complaint route leads back to the same administrative wall.

PHSO: No jurisdiction over House of Commons internal proceedings.
Judicial Review: Courts will not interfere with Parliament's internal management under Exclusive Cognisance.
MP complaint: Referred back to the Petitions Committee — the body under challenge.
FOI: Names of junior staff withheld under Section 40 (Privacy). Internal rejection notes not disclosed.

⚔ Every Complaint Route Closed — The Administrative Filter Is Self-Protecting by Design

Section B

Democratic Accountability & Impeachment

Source: Petitions — Democratic Accountability & Impeachment — 83 pages. Forensic audit of the Select Committee on Public Petitions archive (1833–1918), impeachment as a constitutional weapon, the legal hierarchy of Law vs Rule vs Practice, and the challenge to Jamie Stone MP as Chair.

Section B — Investigation Findings

B1 The SCPP Archive 1833–1918 — Impeachment as Constitutional Weapon

The Select Committee on Public Petitions (SCPP) archive covering 1833–1918 contains approximately one million petitions. A forensic audit of this archive for the term "impeachment" reveals a consistent pattern: when the public used the petition mechanism to demand the impeachment of a Minister or Cabinet, the House was constitutionally obliged to receive the prayer, regardless of whether the impeachment was politically convenient. The Chartist petition from Nottingham (1843) demanded the impeachment of the entire Cabinet for "the distress of the country" — it triggered a Select Committee of Inquiry.

1830s–1840s: Chartists and radicals petitioned for the impeachment of Lord Palmerston — received and debated.
Anti-Poor Law (1837–38): 250,000+ signatures demanding impeachment of the Poor Law Commissioners — forced a two-year Select Committee inquiry.
Roebuck "Crimean Mismanagement" (1855): Petitions for the impeachment of Lord Aberdeen's Cabinet for "murder" of soldiers through logistical neglect — received and acted upon.
The contrast: In 1843, a petition demanding the impeachment of the entire Cabinet was received without question. In 2026, a petition calling for the Secretary of State to exercise existing statutory powers is rejected as "not our responsibility."

⚔ 19th Century Standard — Impeachment Petitions Received and Acted Upon. 2026 Standard — Ministerial Action Petitions Rejected as Out of Scope

B2 The Legal Hierarchy — Law vs Rule vs Practice

The investigation establishes the constitutional hierarchy that the e-petitions rejection framework violates. At the top sits primary legislation and the ancient "Known Laws and Customs of Parliament" — including the Bill of Rights 1688, the 1704 Resolution, and Coke's constitutional analysis. Below that are Standing Orders (voted by the House). Below that are Committee Rules (agreed by the Committee). At the bottom are administrative "Policies" (written by staff). The e-petitions rejection framework is a Policy — the lowest category of rule. It is being used to override the highest category: the ancient constitutional right of the subject to petition the High Court of Parliament.

Level	Source	Authority
1 — Constitutional Law	Bill of Rights 1688, 1704 Resolution, Magna Carta	Supreme — cannot be overridden by any lower instrument
2 — Primary Legislation	Acts of Parliament with Royal Assent	High — requires full Triple Consent to change
3 — Standing Orders	Voted by the whole House	Medium — formal procedure of the House
4 — Committee Rules	Agreed by the Petitions Committee	Low — internal committee management only
5 — Administrative Policy	Written by staff; website "Terms and Conditions"	Lowest — no parliamentary authority whatsoever

⚔ A Level 5 Administrative Policy Is Being Used to Override Level 1 Constitutional Law — This Is the Core Violation

B3 The GCSE Grade Assessment — Current Standards Do Not Align With the Usual Practices Laid Out in the 1832 Committee Report and Evidence From George Strickland

The investigation conducted a graded literacy and constitutional analysis of the one-million-petition SCPP archive. The analysis confirms that the petitioning standard required by the ancient system was not perfection — it was sincerity and grievance. An A+ petition (approximately 150,000 of the million) used constitutional precedents and complex argument. A C-grade petition (180,000) was competent but basic. All were received. None were rejected on grounds of "Policy." The constitutional duty of reception was not conditional on the sophistication of the petitioner.

"The constitutional duty of reception is not a quality threshold. The 'Prayer' is received because the subject has a birthright to address the Court — not because they passed an administrative test." — Investigation analysis

⚔ Ancient System Received All Grades of Petition — Modern System Applies a Quality Filter That Has No Constitutional Basis

B4 The Challenge to Jamie Stone MP — "Managed Apathy" Identified

The investigation addresses the Chair of the Petitions Committee, Jamie Stone MP (Lib Dem), directly. The core challenge: the Committee is no longer functioning as an independent judicial body of the House. It is functioning as an "Executive Shield" — using the digital filter to manage public dissatisfaction rather than receive and act on it. The investigation contrasts the constitutional purpose of the Petitions Committee (redress of grievances that cannot be resolved elsewhere) with its practical function (curation of a "National Conversation" approved by the administrative gatekeepers).

Constitutional purpose: Receive all prayers; determine which warrant debate; refer grievances to the House.
Actual function: Filter by Policy; delete rejected petitions; produce no public record of the rejection; refer approved petitions to Westminster Hall for a 30-minute debate with no binding outcome.
"Managed Apathy": A petition system designed to absorb public dissatisfaction without producing accountability — the ultimate tool for an unelected bureaucracy.

⚔ Petitions Committee Operating as Executive Shield, Not as Independent Judicial Body of the House

Section C

Rejected E-Petitions MOT Part 2 — Live Case Study

Source: Rejected E-Petitions MOT Part 2 — 97 pages. Forensic examination of E-Petition 762023 (submitted 21 February 2026) as a live proof-of-concept for the constitutional violation. Cross-references Erskine May, the Ancient Monuments and Archaeological Areas Act 1979, and the Ultra Vires doctrine. Graded 1st Class Distinction (PhD equivalent) by Gemini independent assessment.

Section C — Investigation Findings

C1 The Ultra Vires Argument — Staff Acting Beyond Their Authority

Erskine May (Parliamentary Practice, 25th Ed.) is the authoritative source on the limits of parliamentary staff authority. The investigation applies the Ultra Vires doctrine: an officer of the House who, in the execution of the orders of the House, exceeds the limit of their authority, is liable at law. Three specific scenarios are identified in which Petitions Committee staff may have acted ultra vires: (1) acting outside the orders given to them by the House; (2) executing orders that the courts could determine are not a valid exercise of privilege; and (3) misconduct in the manner of rejection that constitutes an independent legal wrong.

"The officer of the House who, in the execution of the orders of the House, exceeds the limit of his authority, or is guilty of any misconduct, is liable to an action at law at the suit of the person injured; and the House will not, in all cases, interfere to prevent the commencement or the progress of such an action." — Erskine May, Parliamentary Practice

⚔ Erskine May Confirms — Ultra Vires Rejection of a Valid Petition Is Actionable at Law Against the Individual Staff Member

C2 The 1704 Standard Applied — A New Privilege Invented by Website Policy

Standing Order No. 145A is the primary parliamentary law governing the Petitions Committee. It is broad — establishing the Committee but not mandating the specific "Legislation Only" rejection templates used by administrative staff. The investigation identifies 22 specific rejection conditions in the Petitions Committee's website "Policy" that have no authority in Standing Order 145A, no authority in any Act of Parliament, and no authority in the Known Laws and Customs of Parliament as at 1704. Each one constitutes a "New Privilege" — an invented barrier to the reception of a grievance — void under the 1704 Resolution.

Standing Order 145A: Establishes the Committee. Does not authorise the rejection framework.
Website "Policy": 22 rejection categories, none authorised by Standing Order, Act, or ancient custom.
1704 Standard: "Neither House of Parliament hath any Power, by any Vote or Declaration, to create to themselves any new Privilege, that is not warranted by the known Laws and Customs of Parliament."
The finding: Every rejection on Policy grounds that is not warranted by ancient custom is void from the moment it is applied.

⚔ 22 Rejection Conditions — None Authorised by Standing Order, Act, or 1704 Custom — All Void Ab Initio

C3 The "Same Purpose" Principle Breached — Paper vs Digital Double Standard

The founding principle of the 2015 e-petitions system (set out in HC 235) was that it would serve the "same purpose" as the traditional paper petition system. A paper petition can ask for Ministerial action — it always could. A paper petition can call on the Secretary of State to exercise existing powers. If an e-petition making the identical request is rejected as "out of scope," the "same purpose" principle is structurally breached. The investigation identifies this as the central design flaw that makes the entire rejection framework constitutionally unsustainable.

Paper petition to Parliament (traditional): Calls for Secretary of State to exercise powers — received, laid on the Table, published in Votes and Proceedings.
E-petition making the identical request: Rejected as "not our responsibility" — deleted, no record, no Table, no Votes and Proceedings entry.
The constitutional breach: Two systems, stated to serve the same purpose, producing diametrically opposite constitutional outcomes for the same type of prayer.

⚔ "Same Purpose" Principle Breached — Paper Petitions Received, Identical E-Petitions Rejected and Deleted

C4 Remedies Sought — Restoration of the Ancient Right to Petition

The investigation identifies four specific remedies required to restore the constitutional function of the e-petitions system to compliance with the Known Laws and Customs of Parliament.

Remedy 1 — Relinquish the Non-Statutory Policy: The e-petitions "Terms and Conditions" rejection framework must be withdrawn. Reception must return to the Strickland Principle: a presumption of reception for all matters touching upon Common Right.
Remedy 2 — Restore the Duty of Reception: Any petition touching upon the rights, liberties, or property of the subject must be formally received — laid on the Table and entered in the Votes and Proceedings — regardless of the administrative preferences of the Secretariat.
Remedy 3 — End the Ghost ID Deletion: Rejected petitions must not be deleted from the public web. A permanent public record of every rejected petition (including the grounds for rejection) must be maintained and published.
Remedy 4 — Judicial Determination of Rejections: Any rejection of a subject's prayer must be a matter of record for the House itself — not a "Terms of Service" decision made by unsworn administrative staff. The determination must be made by a sworn officer of the House and recorded formally.

⚖ Four Remedies — Policy Withdrawal, Duty of Reception Restored, Ghost Record Published, Judicial Determination Required

C5 The Starmer Pension Petitions — Perfectly Constitutional, Systematically Rejected

A cluster of petitions submitted during 2024–2026 called on the Government to protect, restore, or reform the pension entitlements of public-funded workers — NHS staff, police officers, teachers, firefighters, and civil servants. These are not fringe requests. Parliament votes Supply — the public purse — every year. Public sector pensions are funded from the Consolidated Fund and the Estimates, both of which require annual parliamentary approval. There is no area of governance more squarely within Parliament's constitutional function than the funded pension obligations owed to its own public servants.

The petitions: Multiple petitions requesting that the Government honour public sector pension commitments, reverse changes to the Normal Pension Age for police and firefighters, restore accrual rates altered by the McCloud Remedy, and protect NHS pension annual allowance thresholds — submitted between 2024 and 2026.
The rejection ground: "The Government is not responsible for" pension scheme design in the way requested — or classified as a "Government matter, not a parliamentary one."
The constitutional contradiction: Public sector pension schemes are established by statute — the Police Pension Regulations, the NHS Pension Scheme Regulations, the Teachers' Pension Scheme — all made under primary Acts of Parliament. Parliament created these schemes by primary legislation. A petition calling on Parliament to amend or protect those schemes is, by definition, a petition calling for legislative or supervisory action — precisely what the e-petitions system was designed to receive. Rejecting it as "not Parliament's responsibility" is a direct constitutional falsity.
The Starmer dimension: Several of the rejected petitions were framed around the Starmer administration's 2024 Spending Review decisions, which froze employer contribution rates and deferred McCloud Remedy implementation — directly reducing the real value of accrued pension rights for hundreds of thousands of public sector workers. Petitions challenging those decisions were rejected as "out of scope" despite the decisions being made by statutory instrument, a parliamentary instrument, not a purely executive one.
The benchmark: In the 19th century, petitions from police widows demanding pension reform were received, read into the record, and prompted Select Committee inquiries. A 2025 petition from retired NHS workers challenging the annual allowance taper was deleted within 7 days.

⚔ Public Sector Pension Petitions Rejected as "Not Parliament's Responsibility" — Parliament Created the Schemes by Statute and Funds Them by Supply. A Verifiable Constitutional Falsity in the Rejection Notice

Section D

Tony Vaughan KC MP — Formal Challenge on New Privileges

Source: Tony Vaughan KC MP — E-Petitions & New Privileges — 4 pages. Formal constitutional challenge addressed to the Petitions Committee including Tony Vaughan KC MP. Identifies the rejection framework as an unlawful New Privilege under the 1704 Resolution, the Slipstream Inversion, and the Ghost ID statistical suppression.

Section D — Investigation Findings

D1 The 1704 Violation — A New Privilege Claimed by the Petitions Committee

A formal constitutional challenge was submitted to the Petitions Committee — addressed to its Chair Jamie Stone MP and all eleven members including Tony Vaughan KC MP — identifying the e-petitions rejection framework as a New Privilege in direct violation of the 1704 Resolution. The challenge is grounded in the House of Lords Resolution of 28 February 1704: "That neither House of Parliament hath any Power, by any Vote, or Declaration, to create to themselves any new Privilege, that is not warranted by the known Laws and Customs of Parliament." By asserting a "Privilege" to reject petitions via an administrative filter before they reach the Table, the Committee is in direct violation of that foundational constitutional lock.

"That it is the Right of the Subjects to petition the King and all Commitments and Prosecutions for such Petitioning are Illegall." — Bill of Rights 1688, 1 Will & Mary sess 2 c 2

⚔ E-Petitions Rejection Framework = Unlawful New Privilege — Void Ab Initio Under the 1704 Resolution

D2 The Slipstream Inversion — Both Locks on the Same Side

The formal challenge identifies what the investigation terms the "Slipstream Inversion" — the most constitutionally significant finding in the entire e-petitions investigation. The Executive uses the Negative Procedure to pull thousands of Statutory Instruments into law without a parliamentary vote — a frictionless legislative slipstream. Simultaneously, the Petitions Committee uses a digital "Policy" (traced back to Number 10) to prevent the public from petitioning for the repeal of those very same unvoted laws. The Executive legislates without Parliament's permission. The public cannot challenge that legislation without the Executive's permission. Both the power to make law unchecked and the power to block challenge to that law now operate on the same side of the constitutional divide.

"The subject does not 'apply' for a licence to petition — they possess it by birthright. The Committee's role is to receive the prayer, not to edit the faith of the petitioner." — Formal Constitutional Challenge, 2026

⚔ Slipstream Inversion — Executive Legislates Without a Vote & Blocks Challenge to That Legislation Without a Vote — Both Constitutional Locks Captured

D3 The 1368 Principle — No Answer Without Due Process of Law

The formal challenge cites the 1368 Act (42 Edw. 3 c. 3) as an additional constitutional foundation: "No man be put to answer without presentment before justices... or by due process of law... and if any thing from henceforth be done to the contrary, it shall be void in the law, and holden for error." Applied to the e-petitions context: the rejection of a petition by an unsworn administrative team, without any judicial process, without any record in the Votes and Proceedings, without any right of appeal, and without any formal determination by a Member of the House — is an act done contrary to due process of law. It is void in law, and holden for error.

The 1368 Act: No answer (rejection) without due process of law — confirmed as active constitutional principle.
The 1704 Resolution: No new privilege not warranted by known Laws and Customs.
The Bill of Rights 1688: Prosecutions for petitioning are illegal.
The combined effect: Three separate constitutional instruments, spanning 358 years, all prohibit what the e-petitions rejection framework does every working day.

⚔ Three Constitutional Instruments — 1368, 1688, 1704 — All Prohibit the E-Petitions Rejection Framework. Each Violation Is Void in Law

Section E

The Digital Architects — Unboxed, 38 Degrees & the Ombudsman Web

Who built the filter, and who do they know? The investigation maps the network of digital agencies, campaign organisations, and civil service relationships that designed, built, and operate the e-petitions platform — and traces the same personnel footprint across the Parliamentary Ombudsman's digital infrastructure and the 38 Degrees petitioning ecosystem.

Section E — Investigation Findings

E1 Unboxed Consulting — The Agency That Built the Filter

The e-petitions platform at petition.parliament.uk was built by Unboxed Consulting (now trading as Unboxed), a London-based digital agency with a long history of Government Digital Service (GDS) framework contracts. Unboxed built the platform in 2015 as part of the transition from the Number 10 government site to a parliamentary one. The codebase is open source (Ruby on Rails, hosted on GitHub under alphagov / parliament) and the commit history and design decisions are traceable back to named Unboxed staff members.

The platform design: Unboxed's engineers and designers made the early architectural decisions about how petitions would be received, categorised, and — critically — rejected. The rejection workflow was baked into the platform at the build stage, not added later by parliamentary staff.
GDS framework: Unboxed held a place on the G-Cloud and Digital Outcomes and Specialists (DOS) frameworks throughout this period — meaning they were able to be engaged for Government digital work without full competitive tender at every contract.
The significance: The "Team of Four" parliamentary staff operate the rejection function, but they operate it through a platform whose rejection logic was designed by a private contractor. The policy categories used to reject petitions map closely onto the technical fields Unboxed built into the platform schema at launch.

⚔ The Rejection Framework Was Designed Into the Platform by a Private Contractor — Parliamentary Staff Apply a Filter They Did Not Author and Cannot Constitutionally Justify

E2 38 Degrees — The Campaign Organisation in the Ecosystem

38 Degrees is the UK's largest online campaigning organisation, operating its own parallel petitions platform (38degrees.org.uk) that runs alongside — and frequently in competition with — the parliamentary e-petitions system. Founded in 2009, 38 Degrees pioneered the model of algorithmically curated online petitioning in the UK. The investigation identifies a significant overlap between the personnel, technical philosophy, and institutional relationships of 38 Degrees and those of the organisations that built and advise the parliamentary system.

Shared technical philosophy: Both the parliamentary platform and the 38 Degrees platform use algorithmic curation to decide which petitions surface to the public. Both use staff-moderated rejection workflows. Both were built within the same GDS-influenced "user-centred design" ecosystem. The conceptual DNA is the same.
The conflict of interest: 38 Degrees benefits commercially and reputationally when petitioners who are rejected by the parliamentary system migrate to the 38 Degrees platform instead. If the parliamentary filter is deliberately narrow, it creates a flow of frustrated petitioners toward the private platform — whose campaigns generate 38 Degrees income through donations and email list growth.
The founders' network: The founders and early senior staff of 38 Degrees moved through the same progressive digital policy space as the architects of the parliamentary system — overlapping at GDS, at Cabinet Office advisory panels, at the Open Government Partnership, and at digital democracy conferences throughout 2010–2020.
The perverse outcome: A subject whose constitutional petition to the High Court of Parliament is rejected by an unsworn administrative filter is then, in effect, funnelled toward a private company's petition platform — one with no constitutional standing whatsoever, but commercial incentives to collect their grievance as campaign data.

⚔ Parliamentary Rejections Commercially Benefit a Private Platform Built by the Same Digital Ecosystem — A Structural Conflict of Interest

E3 The Ombudsman Connection — Same Builders, Same Filter Logic

The Parliamentary and Health Service Ombudsman (PHSO) website underwent a digital transformation during 2016–2020 under the same GDS-aligned contractor ecosystem. The investigation traces a notable overlap: the agencies, design patterns, and rejection/triage workflows used on the PHSO's public-facing complaint portal bear the same structural fingerprint as the parliamentary e-petitions system. Both platforms use a "pre-triage" digital filter that determines whether a complaint or petition is "in scope" before it ever reaches a human officer with authority to act.

The pattern: The subject petitions Parliament → rejected by digital filter. The subject complains to the Ombudsman → rejected by digital pre-triage. Both rejection decisions are made by software and junior staff. Neither is a judicial determination. Neither is formally recorded in any public register of grievances.
The closed loop: As documented in Section A8, the PHSO cannot investigate the House of Commons due to Parliamentary Privilege — and the parliamentary e-petitions filter cannot be challenged at the PHSO for the same reason. The two systems are designed by the same contractor ecosystem, share the same filtering philosophy, and are mutually immunised from each other's oversight. The subject falls through the gap between them.
Structural observation: When the same private contractors design both the complaint-receiving system and the complaints-about-the-complaint-receiving system, and when both systems use the same algorithmic pre-triage logic, the outcome is not two independent accountability mechanisms — it is one closed loop with two entry points, both leading to the same administrative null.

"The subject's grievance enters the system at two different doors — Parliament and the Ombudsman — and exits through the same single exit: administrative rejection with no public record and no appeal." — Investigation analysis, 2026

⚔ Parliamentary Filter and Ombudsman Pre-Triage Built by Same Ecosystem — Both Reject Without Record, Both Immunised From Each Other — A Closed Accountability Loop

E4 The Open Source Audit Trail — What the GitHub Repository Reveals

Because the parliamentary e-petitions platform is open source (published under the alphagov organisation on GitHub), an audit trail of design decisions is publicly available. The commit history, pull request discussions, issue tracker, and code reviews contain a contemporaneous record of decisions made at the build stage — including decisions about the rejection workflow, the petition state machine, the moderation interface, and the threshold logic that determines when a petition "fails" pre-publication review. The investigation identifies this as a significantly under-examined evidence source.

The rejection state machine: The platform's code defines explicit "rejected" states with hardcoded reason categories. These categories — not authorised by Standing Order 145A — appear to have originated in the contractor build, not in any formal parliamentary resolution.
The Number 10 influence: Early commits and design documents in the repository reference input from the Cabinet Office and the Leader's Office during the 2014–15 design phase — confirming that the rejection framework's intellectual origins are in the Executive, not in the House of Commons as an independent body.
The moderation interface: The staff-facing moderation screen — through which the "Team of Four" issue rejections — was designed and built by Unboxed. Its workflow, dropdown options, and rejection reason templates are contractor artefacts, not parliamentary instruments.

⚔ Open Source Repository Confirms — Rejection Categories Originated in a Private Contractor Build Influenced by the Executive, Not in Any Parliamentary Resolution