the bench takes commissions: describe what you need.

a calibration run on your material, priority on an adapter your pipeline is missing, or something this page has not thought of. no price list lives here, on purpose: a quote is built from what you actually asked for, and everything is on paper before any money moves.

what teams commission

a private calibration runyour detector · your corpora

the same work the public receipts come from, run on the material you actually score and the detector you actually use: error rates at your operating points, thresholds stated empirically and conformally, the subgroup splits an aggregate would hide, and the refusal lines where your data cannot support the ask. the receipt pack arrives in the committed-receipt format with the reproduce commands riding along, and it is yours to publish, file, or keep private.

priority workadapters · features

name the detector you need an adapter for, or the capability your pipeline is missing, and a commission moves it to the front of the queue. one thing never changes: adapters and anything else that lands in the core ship public, under the same license as the rest. priority is for sale; exclusivity is not.

something else entirelydescribe it

measurement problems rarely arrive shaped like a menu, so the third lane is the honest one: describe what you need. if the bench can do it well with the resources it has, a quote comes back built on exactly that. if it cannot, you hear that instead of a yes.

how an engagement runs

it starts with a plain description of the problem: the detector, the material, and what decision the numbers will feed. the first thing that comes back is a feasibility answer, not a pitch; work the bench could not do well is declined plainly, with the reason.

then the paper. before any money moves, every engagement gets a written scope, a timeline, a cost breakdown, and a definition of done. if one of those four is missing, nothing has started yet. the quote is built on the ask, which is why this page carries no prices: a corpus of three hundred support tickets and a corpus of forty thousand essays are different jobs, and one flat number would misprice both.

the route in is the contact page, which names the engagements mailbox and what a first mail should include. engagements run a small number at a time, async by default.

what a commission never buys

a number on this site. the public receipts are ongoing experiments on public data; they cannot be commissioned, and they cannot be edited. that is what makes them worth citing.
a verdict. commissioned receipts describe your detector on your corpus. they never pronounce a document or a person human or AI, the same boundary the terms page holds everywhere else.
exclusivity over the core. commissioned adapters and improvements ship public under the AGPL. a commission buys their place in the queue, never their withdrawal from it.
a paid tier. anything that surfaces an error, an interval, or a caveat stays free, on principle; a commission buys work, never a feature unlock.
a different answer. refusals ship in private receipt packs exactly as they do in public ones: where your data cannot support the guarantee you wanted, the receipt says so. refusing is never priced.

adjacent: contact · the package · about