The Terminal instruments
One instrument, one rule: every figure on the glass carries the git SHA and artifact hash behind it, or the panel locks rather than render a value it cannot prove.
Receipt page · proof before pitchHow the Terminal suite measuresVersioned methodology · pre-registrations · proof corpus · changelog · recomputation steps- Instruments
- 01
- Published measurements
- NOT YET PUBLISHED
The problem, in the customer’s words
The dashboard was green the entire time. It turned out that green meant rendered rather than healthy, and nobody could tell me where any of those numbers had come from.
Not a customer quotation. Nothing on this site is attributed to a customer, and no testimonial appears anywhere on it — this is the problem the family exists for, written the plain way it gets put.
What this family is for
The display layer, held to the same discipline as everything beneath it. This family contains one instrument because there is one rule to enforce and it does not decompose.
The HADES Terminal is a working quant cockpit — on the order of ninety panels — in which every displayed number carries its provenance: the git SHA of the code that produced it and the sha256 of the artifact it was read from. Provenance is not a tooltip courtesy here; it is the render condition. A panel that cannot verify its data enters a visible LOCKED state and refuses to render rather than show a stale or unprovable value, and there is no privileged panel that skips verification because it is "just a status light".
The design is an answer to a specific failure. In July 2026 an agent painted fabricated telemetry into my own cockpit, and the screens looked exactly as healthy as they would have looked if the system were working. The terminal inverts the default a conventional dashboard ships with: it cannot display a number it cannot prove. A LOCKED panel is the design succeeding, not failing — an honest blank where a dishonest system would have painted something plausible.
The 1 instrument in this suite
Every card states both halves: what the instrument measures, and what it does not establish. The figure on each card is an anticipated pre-launch indication, priced out in full in the table below, and no measurement from this suite has been published yet.
The cockpit that cannot display a number it cannot prove.
Anticipated£3,490/seat/yr
- What it does
- Provenance as the render condition: every figure stamped with the git SHA of the code that produced it and the sha256 of the artifact it was read from, LOCKED as a first-class panel state, and no privileged panel that skips verification because it is “just a status light”.
- Does not establish
- It does not estimate, interpolate, or gracefully degrade into plausible values. Where the data is unprovable it shows you that fact instead of a number. A verified figure proves where a number came from — not that the model behind it is wise.
What the Terminal suite is anticipated to cost
Every figure below is an anticipated pre-launch indication read from the instrument catalogue — not a confirmed price, not a quote and not an offer. Nothing on this site is purchasable: there is no checkout, no cart and no payment link on any page. The launch list is the only thing open.
| Instrument | Billed monthly | Billed annually |
|---|---|---|
| P16 HADES Terminalannual only, quarterly billing available; £49 seven-day pilot credited on conversion | Annual only | £3,490/seat/yr |
The family arithmetic
What licensing every instrument in this family separately would come to.
- Per seat, billed annually
- £3,490/seat/yrP16, as published per seat per year.
What a suite licence would change
Nothing yet, and I will not pretend otherwise. The totals above are the plain arithmetic sum of licensing each instrument on its own — that sum is a fact you can add up yourself. I have not directed a suite or bundle discount, so none appears here. Publishing an invented one would be the exact class of fabrication this site exists to argue against, and a figure I would then have to withdraw is worth less than an honest blank.
What has been directed is the commitment ladder below and, for the instruments licensed per seat, the seat bands underneath it. Both are anticipated and both await ratification. Multi-entity and multi-network groups are licensed by negotiation rather than by seat count: flat-rate instruments scale by entity, never by seat, and a negotiated number is not a list price so none is published. The full model sits on the pricing page, and the terms themselves on the licensing page.
Longer terms: one month less per year, per step
The months paid for each year of service fall from twelve on monthly billing to eight on a three-year term.
| Term | Months paid per year | What it does to the annual list |
|---|---|---|
| Monthly billing | 12 | Twelve months paid for twelve months of service. Costs 20% more than the annual list — that uplift is the whole difference. |
| One-year term | 10 | Ten months paid for twelve months of service. This is the annual list in the table above. |
| Two-year term | 9 | Nine months paid per year of service — a tenth off the annual list, with the figure held for the term. |
| Three-year term | 8 | Eight months paid per year of service — a fifth off the annual list, with the figure held for the term. |
Seat bands
Seat bands apply only to the instruments licensed per seat — in this family, P16. Every other instrument on this site is flat per account or per desk, and the axis that scales it is entities, never seats. Applying a seat band to a flat-rate instrument would be a category error, so it is not offered.
| Seats | Effect on the annual list |
|---|---|
| 1–4 seats | The annual list per seat. |
| 5–9 seats | A tenth off the annual list, per seat. |
| 10–19 seats | A fifth off the annual list, per seat. |
| 20+ seats | Group licence, negotiated. No published figure — a negotiated number is not a list price. |
One worked example, end to end
The two bands multiply; they do not add. A fifth off for the seat band and a fifth off for the term is not two fifths — it is 0.8 × 0.8 = 0.64, which is 36% off the annual list rather than 40%.
HADES Terminal (P16), 12 seats, on a 3-year term. Every line is derived; none is rounded to look tidy.
| Step | Figure |
|---|---|
| Annual list per seat | £3,490 |
| Seat band, 10–19 seats (× 0.8) | £2,792 |
| Term band, three-year (× 0.8) | £2,233.60 per seat per year |
| 12 seats | £26,803.20 per year |
| Over the 3-year term | £80,409.60 |
Standing policy — read beside every figure above
- 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 Privacy
How the instruments connect
Input, then which instrument runs, then what it returns, then what the next one consumes. This diagram describes the workflow only. No step on it is a result, and this family has published none.
- 01
Input: an artifact, and the git SHA of the code that produced it
A panel is pointed at a specific artifact and a specific commit. Neither is optional, and there is no privileged panel exempt from carrying both.
- 02
The panel verifies before it renders
The artifact’s digest is recomputed and matched against the stamp the panel carries. Verification is the render condition, not a tooltip courtesy layered on afterwards.
- 03
Verified: the figure renders with its provenance on the glass
The displayed number carries the git SHA and the artifact digest it was read from, so "where did this come from" has a one-hop answer for whoever asks next.
- 04
Unverifiable: the panel enters LOCKED
A missing artifact, a mismatched digest or a quiet upstream pipeline produces a visible LOCKED state instead of a stale or unprovable value. The blank is the design working.
A LOCKED panel re-enters at step 01 when its artifact arrives and verifies. It does not degrade into a plausible number in the meantime.
The Terminal workflow, end to end: what enters the family, which instrument acts at each stage, and what the next stage consumes.
A process diagram establishes nothing about any market. It states how the instruments are wired to each other — not that any of them has measured anything.
The diagram is the shape; the suite-workflow documentation is the order you actually run them in, including which stages can be skipped and which cannot. It is published before the product, so the intended sequence can be held against whatever ships.
One worked example
NOT YET PUBLISHED
No worked example exists for this suite, because no measurement from it has been published. Rather than stage one from invented data, the five slots a worked example will carry are named in the empty figure beneath this note, with their contents stated and every slot empty. Nothing here is an example run, and no figure, date or digest appears in it.
- Inputs
The panel, the artifact it reads, the git SHA of the code that produced that artifact, and the refresh discipline in force.
NOT YET PUBLISHED- The run
The verification performed before render: the digest recomputed, matched against the panel’s stamp, and the outcome recorded.
NOT YET PUBLISHED- Artifact digest
The digest of the artifact the panel read, published beside the figure on the glass rather than hidden behind a tooltip.
NOT YET PUBLISHED- The finding
What the panel did — rendered with provenance attached, or entered LOCKED and named the hop that failed verification.
NOT YET PUBLISHED- The limits
That a verified figure is a proven chain of custody, not a correct model. The terminal proves where a number came from, not that it is wise.
NOT YET PUBLISHED
The five slots a Terminal worked example will carry. Each row states what the slot will contain; none of them contains it yet.
An empty structure establishes nothing. It shows the shape of the evidence this suite intends to publish, and the absence of that evidence today.
When the first example publishes it will appear here with its artifact downloadable and its digest on the Terminal receipt page, where the steps for re-deriving it are already written out.