gaige
ink
v0.0.4 · released

every number here has a mailbox: challenges get priority.

four routes, each with the format that gets it acted on fastest. no forms, no tickets, no chatbot at the door.

the routes

email

corrections, challenges to any published number, press, licensing and commercial terms: ghxrk13@proton.me. one mailbox, read by the people who run the numbers.

bugs

a receipt that did not reproduce, an install that broke, output that looks wrong: github issues. attach the fingerprint block from the run; it answers half the questions before anyone asks them.

questions & ideas

use cases, methodology questions, places gaige turned up in the wild: github discussions. threads that survive triage land on the roadmap with a receipt.

security

vulnerabilities in the package or this site: security.txt names the address and its expiry, and the repository’s SECURITY.md carries the same contract. please keep vulnerability detail out of public issues.

what to include

what to expect

mail is read within days, not minutes; there are no autoresponders and no acknowledgment theater. when a report changes a published number, the fix lands with a dated row on the page it changes, and the thread that caused it gets the receipt back. that loop closing is the point of having routes at all.

who answers

the operators of gaige.dev, pseudonymously by policy: names and résumés stay off this site on purpose, and the about page states why receipts outrank credentials here. the mailbox above is the accountable route for everything this site publishes.

adjacent: about the project · terms · privacy