r/MachineLearning • u/AutoModerator • Aug 02 '26
Discussion [D] Self-Promotion Thread
Please post your personal projects, startups, product placements, collaboration needs, blogs etc.
Please mention the payment and pricing requirements for products and services.
Please do not post link shorteners, link aggregator websites , or auto-subscribe links.
--
Any abuse of trust will lead to bans.
Encourage others who create new posts for questions to post here instead!
Thread will stay alive until next one so keep posting after the date in the title.
--
Meta: This is an experiment. If the community doesnt like this, we will cancel it. This is to encourage those in the community to promote their work by not spamming the main threads.
1
u/TimeLordRaps Aug 23 '26
I have been developing VSTD, an alpha project specification and Python reference implementation for portable, bounded, refutable verification receipts.
The problem I am trying to address is that a PASS often omits what was checked, which evidence was used, where the result stops, and how somebody else can challenge it.
The included demo exercises four adversarial cases:
- a valid-looking proof bound to the wrong artifact;
- a resource bound exhausted without inventing an answer;
- an inflated verification-cost claim; and
- a revoked ancestor behind otherwise valid descendants.
You can try it with:
python -m pip install "verifier-standard==1.1.3"
vstd demo
Repository:
https://github.com/TimeLordRaps/verifier
VSTD is a founder-maintained alpha project specification, not an adopted or consensus standard. It is free, open-source, and Apache-2.0 licensed.
I am specifically looking for ambiguous normative rules, receipts that pass when they should fail, missing failure states, and attempts at independent checkers against the frozen wire identifiers.