> A service and toolkit proving CI gates can actually fail, classifying every gate BEHAVIORAL, STRUCTURAL, or DECLARED-GAP. - Canonical: https://hadalinstruments.com/instruments/gate-falsification-kit/ --- [Back to Instruments](https://hadalinstruments.com/instruments/) P21 Integrity Services # Gate Falsification Kit A gate that has only ever passed proves nothing. Anticipated price Anticipated · not ratified · not an offer From £12,000 per engagement An engagement fee has no term to annualise over. Scope, method and deliverable are agreed in writing before work starts, and the figure above is where a single engagement begins rather than where it lands. Open to academic access "Can every gate actually fail?" is a software-engineering research question with a universal answer surface, and vacuous-green CI is endemic well beyond trading. The kit as software only. The commissioned engagement is a person’s time and is not covered at any rate. [Academic access — who qualifies and on what terms](https://hadalinstruments.com/academic/) Nothing on this site is on sale. There is no checkout, no cart and no payment link on any page. Prices publish pre-launch so they can be read, compared and checked rather than requested — [seat bands, group licences and multi-year terms are set out in full below](#commercial). here would have added one landmark per placement, which on the homepage means a landmark list that is mostly disclaimer. --> Standing policy — read this beside the figure - **No promise of profit, ever.** Hadal makes no performance claims and carries no implied edge. Past measurements describe instrument behaviour — never future returns. - **You own risk management.** Hadal cannot control it and does not insure it. Good tools do not fix bad discipline — and this site says so. - **Analytical tools, for discretionary use.** Nothing here is investment advice or a recommendation to trade. Every decision, and every outcome, is yours. The same statement stands in the footer of every page.[Terms](https://hadalinstruments.com/terms/) [Privacy](https://hadalinstruments.com/privacy/) [How it measuresThe Integrity Services suite methodology](https://hadalinstruments.com/methodology/services/)[BoundsWhat it does not establish](#what-it-does-not-do) Published measurements NOT YET PUBLISHED Specification | Value | Catalogue no. | P21 | Suite | [Integrity Services](https://hadalinstruments.com/suites/services/) | Methodology | [How the Integrity Services suite measures](https://hadalinstruments.com/methodology/services/) | Availability | Pre-launch — not on sale | Anticipated price | [from £12,000 per engagement](#anticipated-price) | Delivery | Scoped engagement | Published measurements | NOT YET PUBLISHED | Provenance artifact | NOT YET PUBLISHED | I found this one in my own house. During an internal review of my CI, I discovered that a parity gate — a check I believed was standing guard over a critical invariant — had been green over nothing. It had passed on every run because it was structurally incapable of failing; the condition it claimed to verify was never actually exercised. Every green tick it had ever produced was worthless, and I had been reading those ticks as evidence for months. The lesson generalizes uncomfortably well: **a gate that has only ever passed proves nothing.** Passing is what a working gate does, and it is also what a broken one does. The Gate Falsification Kit is the service and toolkit I built from that discovery: an engagement that treats every gate in your pipeline as a claim to be falsified, not a fixture to be trusted. ## What it does The method is published in the research, and what the engagement adds is that the drilling actually gets done. - **Falsification drills.** For each gate under audit, I plant a violation the gate exists to catch — a real defect of the class it guards against — and observe whether the gate fails. The drills are self-reverting: the planted violation is removed automatically whether or not it is caught, so the exercise leaves no residue in your codebase. A gate that catches its planted violation has demonstrated, not asserted, that it can fail. - **A receipt taxonomy.** Every gate receives one of three classifications. **BEHAVIORAL**: the gate was drilled and observably caught a planted violation — the strongest receipt. **STRUCTURAL**: the gate’s failure path was verified by inspection of its mechanism, but not exercised end to end. **DECLARED-GAP**: the gate could not be drilled or verified, and this is recorded as an open gap — never rounded up to a pass. - **The deliverable: a per-gate receipt ledger.** The engagement produces a ledger listing every gate, its classification, and the drill evidence behind it — a document that turns our CI is green from a mood into a claim with receipts. Aggregate findings across engagements: NOT YET PUBLISHED. - **The toolkit itself.** The drill harness ships with the engagement, so falsification becomes a discipline you re-run — because a gate proven able to fail last quarter can be quietly broken by this quarter’s refactor. ## What it found the last time I ran it on myself The findings here are in-house, from one session on my own estate, 4 August 2026 — not client work, and no aggregate across engagements is published. I list them because each names a *class* of failure that generalises, and because a service that audits gates should be willing to show you its own. - **A gate a single token could satisfy.** A rail required every suppression to name the event that would end it. Its written rule said an empty condition stays “counted as a finding, never a silent permanence”. Its code checked only that the *key existed*. Writing `null` into that field twenty-seven times took the rail from 27 open findings to 5 — the number the honest fix reaches, bought with no substance whatsoever. **The class: the specification and the implementation disagreed, and only the specification had ever been read.** Measured on a scratch copy, restored byte-identical, and the twenty-seven real conditions written by hand instead. - **A gate that punished documenting the defect it enforces.** A scanner forbidding a particular coding shape had no comment handling, so a comment *describing* that shape was reported as an instance of it. The rail was fining engineers for writing the explanation. **The class: a gate that fires on known-good input teaches the team to wave the next alarm through** — precisely what makes an always-red channel worthless. The same defect then appeared in a second, unrelated rail: it is a property of line-regex scanning, not of one script. - **A completeness check that reported clean because it could not look.** A collector whose entire purpose was catching an undiscovered component reported `complete: true` while structurally unable to see anything outside its own directory. Nothing was wrong with the code it ran; it simply never ran anywhere else, and said “complete” regardless. **The class: “could not check” sharing a code path with “checked and found nothing”** — the most common route by which a green tick stops meaning anything. - **And one gate that worked, which matters as much.** Midway through, I edited a file while the suite was running. The suite fingerprints the whole tree, refused the commit with `MID-RUN-TREE-MUTATION`, and named the file. It caught its own auditors. That is a BEHAVIORAL receipt, and it is why the taxonomy has three tiers rather than pass/fail: a ledger where everything fails is as uninformative as one where everything passes. ## What it does not do The Gate Falsification Kit does not certify a gate it could not drill. Gates that resist falsification — too entangled to plant against, too opaque to inspect — are classified DECLARED-GAP and reported as such, even when the client is confident they work. Confidence is what I had in my parity gate. The kit also does not confuse coverage with proof: a BEHAVIORAL receipt attests that the gate caught the violation I planted, not every violation conceivable. ## Who it is for Teams whose CI has been green for months — which is precisely the condition under which this audit finds things. Engineering leads who inherited a pipeline of checks nobody remembers writing, and anyone whose deployment decisions rest on ticks that have never once been observed to fail. ## The ship gate No instrument is sold until it does what this page says it does. Where a page is written in the future tense, that tense is a statement about timing rather than a hedge about capability: the instrument is not finished, so it is not listed as available, not priced as available, and not sold. It waits. Nothing described in this catalogue is a placeholder that will quietly disappear. An instrument that turns out to be wrong gets a [kill-ledger entry](https://hadalinstruments.com/kill-ledger/), not a deletion — which is the only version of that promise anyone can check. ## Commercial terms Published in full, pre-launch, so they can be read and checked rather than requested. Every figure is an anticipated indication I have set and not yet ratified, and every derived figure is the arithmetic of the one above it — shown, not asserted. Nothing here is purchasable: there is no checkout on this site. ### Why Gate Falsification Kit is priced the way it is - **What the figure buys** — Every gate in the pipeline under audit treated as a claim to be falsified rather than a fixture to be trusted: a real violation of the class each gate guards, planted on purpose and self-reverted whether or not it is caught, with the outcome observed rather than inferred. What you keep is the per-gate receipt ledger — which gates caught their planted violation, which were verified only by inspection of their failure path, and which could not be drilled at all and are recorded as an open gap rather than rounded up to a pass — plus the drill harness, so falsification becomes a discipline your team re-runs rather than a verdict you have to take on trust. - **Why it is priced this way** — Per engagement, because the work is bounded by the pipeline rather than by the business behind it: a CI estate has a countable number of gates, and drilling them is finite work that ends with a ledger. It is not a subscription, because the ledger is a statement about a pipeline as it was configured on the day it was drilled, and that evidence expires as the pipeline changes — which is why the harness ships with the engagement, so re-drilling after the refactor is something your team runs rather than something you rent. The floor exists because the cheapest honest version of this is still a person planting real defects one gate at a time and watching what actually happens. - **What the alternative costs** — Trusting the green. That is free, universally practised, and the reason this instrument exists: green is the shared output of a healthy pipeline and a sleeping one, and no amount of looking at it distinguishes the two. The DIY version is real and I publish it — the method is in the research, and a team that runs it themselves has my blessing and needs nothing from me. What the engagement buys is that it actually gets done, by someone whose job is to find the gate that cannot fail rather than to ship the feature behind it. Every figure on this page is an anticipated indication awaiting ratification, and nothing here is purchasable. The reasoning above is published for the same reason the arithmetic below is: a price you can interrogate is worth more than a price you have to accept. ### The two-SKU split One route. This instrument has no marketplace equivalent, and the cell says so rather than sitting empty — an empty cell reads as an omission, and this is a fact about how the instrument is sold. Route | What it is | Anticipated | Marketplace SKU | None, and there will not be one. An engagement is a person’s time against your systems, scoped in writing before it begins. That is not a licence a platform can list. | NO MARKETPLACE ROUTE | Scoped engagement | Scoped in writing before work starts: what will be traced or drilled, what evidence will be produced, and what counts as a finding. Findings from client engagements stay private to the client. | from £12,000 per engagement | The price rule The at-or-below-marketplace cap binds the instruments that ship through a platform. This one does not, so the cap has nothing to bind. What holds in its place is simpler and checkable: the figure above is the only figure. There is no separate, higher list price it is discounted from, nothing on this site has ever been sold at any price, and so there is no “was” anywhere to strike through. Also directed for this instrument - from £12,000 per engagement ### Scope, across a group An engagement is scoped by the surface examined, not by how many people read the result, so neither a seat band nor a term applies to it. Where a group has several entities, desks or networks to cover, that is agreed as one programme across them — scoped in writing before work starts, in the same way a single engagement is — rather than repeated engagement by engagement at the single-engagement floor. A retained or multi-engagement programme is an anticipated route, not a published rate card. ### Commercial routes An engagement scales on scope — the surface examined, agreed in writing before work starts — not on seats or a term. [Licensing — seat bands, group licences and multi-year terms in full](https://hadalinstruments.com/licensing/) ### Support - Tier **Engagement** at this instrument’s base contract — direct, scoped in the statement of work, first response targeted at as the statement of work sets it . Support tier follows the annual contract value, not the price of a single unit — more seats, a suite licence or a group agreement raise the contract value and can raise the tier with it. [Support — the tiers, the ticket-only channel model, and what a target does and does not promise](https://hadalinstruments.com/support/) ### Trial mechanics An engagement has no trial period — scope, method and deliverable are agreed in writing before work starts; nothing is bookable yet. [Trial mechanics in full, by delivery class](https://hadalinstruments.com/licensing/#trial). ### Read before you commit The documentation is published ahead of the product on purpose — intended behaviour is only a commitment if it exists first. Start with [installation and first run](https://hadalinstruments.com/docs/install/), then [the limits](https://hadalinstruments.com/docs/limits/): the conditions under which this instrument refuses to produce a number are the part worth reading before you pay. The full centre is at [/docs/](https://hadalinstruments.com/docs/), and the [support model](https://hadalinstruments.com/support/) states what a ticket does and does not cover. ## Questions and answers Answered from what this instrument publishes about itself. Nothing below is attributed to a customer, because there are none yet. ### Why is a green gate not evidence? Because passing is what a working gate does, and it is also what a broken one does. I found a parity gate in my own CI that had been green over nothing for months. ### What do the three classifications mean? BEHAVIORAL: the gate was drilled and observably caught a planted violation. STRUCTURAL: its failure path was verified by inspection but not exercised end to end. DECLARED-GAP: the gate could not be drilled or verified, recorded as an open gap and never rounded up to a pass. ### Do the drills leave anything behind in my codebase? No. The drills are self-reverting: the planted violation is removed automatically whether or not the gate catches it. ### Can I book this engagement today? No. Nothing on this site is bookable or on sale — there is no checkout and no card capture. The figure on this page is an anticipated indication I have set so it can be read and compared, not a quote, and final pricing awaits my ratification. The launch list is the only thing you can join today. ## Change log NOT YET PUBLISHED Gate Falsification Kit has not shipped, so there is nothing to record. When it does, every version lands here — dated, append-only, written by a person, and including the changes that removed a capability rather than added one. ## Where this sits Gate Falsification Kit is one of the instruments in the [Integrity Services suite](https://hadalinstruments.com/suites/services/). How that suite measures — the per-instrument battery, and the receipts each measurement will carry — is set out in the [Integrity Services methodology](https://hadalinstruments.com/methodology/services/), part of the site-wide [measurement methodology](https://hadalinstruments.com/methodology/). ### Also in the Integrity Services suite Gate Falsification Kit shares the Integrity Services suite with one other instrument. - P20 [Dashboard Lineage Audit](https://hadalinstruments.com/instruments/dashboard-lineage-audit/) Where does that number on your screen actually come from? ### Research behind this instrument Gate Falsification Kit draws on two research notes on this site. - [The floor that never fired](https://hadalinstruments.com/research/the-floor-that-never-fired/) Asked as: "how do you know a check that never fails is working" - [How do you tell if a CI gate can actually fail?](https://hadalinstruments.com/research/how-do-you-tell-if-a-ci-gate-can-actually-fail/) Asked as: "how do you tell if a ci gate can actually fail" --- ## Raw artifact — NOT PUBLISHED FOR THIS PAGE No downloadable artifact ships with this page. Eight published measurements do, each content-hashed so a reader can verify the figures independently. Where a measurement is published here without one, that is a gap rather than a policy, and it is stated rather than left to be noticed. [Measurements that ship their data](https://hadalinstruments.com/research/) [Join the launch list](https://hadalinstruments.com/pricing/#waitlist)[How this suite measures](https://hadalinstruments.com/methodology/services/)