an instrument, run like one

gaige is a calibration and drift instrument for AI measurement: a Python package, a command line, and this site, which publishes the receipts the tool emits. the pitch fits in one sentence: whatever detector you already run, gaige reports what it actually does on your material, with error bars and a fingerprint attached. the certificate carries the full scope; the package page walks the install.

the name is an invented word: gauge, with ai set inside it the way the wordmark draws it. the bench reads the letters as good ai gauging evidence, and that reading earns its adjective the same way every page here does: a number travels with the instrument that produced it, or it does not ship.

gaige is run as a deliberately small, deliberately closed bench. issues and receipt-backed reproductions are welcome; pull requests are not accepted. that is chain of custody rather than unfriendliness: every number this project publishes must reproduce from a command somebody here actually ran, and a closed bench keeps that promise cheap to keep.

the work comes out of practice: security engineering in environments where the network is a privilege, doctoral-level research in AI measurement and detection calibration, and years of defending numbers to reviewers who were paid to doubt them. names and résumés stay off this site on purpose. here, receipts outrank credentials, and every receipt reproduces without knowing who ran it first. that is policy, stated on the certificate too, and it holds until the receipts themselves give a reason to change it.

the bench is built and operated by twilight ventures llc, and it answers for its numbers. the public trail is the identity: github.com/ghxrk13 holds the code and its history, pypi serves the releases, and every receipt on this site reproduces from the commands it prints. wrong numbers get corrected in place with the correction dated; the contact page routes straight to the bench, and a question about any measurement gets answered with the run that produced it.

the tool is dogfooded on this site: public copy gets scored by the same instruments the package wraps before it ships, and the pages carry their own build receipts in the footer. when a promise here changes, the privacy page changes in the same deploy.

the front page calls itself the certificate, and reading it first pays off. it states what gaige is, names what it refuses to do, and carries the reference receipt with its fingerprint. after that, follow whatever question brought you here. maybe the receipts page, where every committed export renders with its numbers up front and its instrument attached, scripts or no scripts. a receipt that needs javascript to exist is not much of a receipt. or the guides shelf, where the long versions live: detector guides, worked threshold arithmetic, drift practice, dated regulatory reading.

the faq answers the questions that keep arriving; custody explains why your corpus and your evidence stay yours; the roadmap says what shipped and what is queued. the footer of every page carries its own build receipt: version and date. if a page here ever contradicts another one, that is a bug; say so on the contact page and it gets fixed in one deploy.