Skip to content

AlankritVerma01/limitation

limitation

PyPI version Python versions CI License

Evidpath helps teams check a recommender before launch by running interaction tests, saving clear evidence, and comparing two versions before they ship.

What Evidpath Helps You Do

  • check that your recommender endpoint is wired correctly
  • run a repeatable audit against a real target URL
  • open a report that shows who struggled and why
  • compare a baseline and a candidate before launch

Get Started In 3 Steps

Install the package:

python -m pip install evidpath

Check your endpoint:

evidpath check-target --domain recommender --target-url http://127.0.0.1:8051

Run one audit:

evidpath audit --domain recommender --target-url http://127.0.0.1:8051 --scenario returning-user-home-feed --seed 7

That run writes an output folder with files such as report.md, results.json, and traces.jsonl.

Where To Go Next

What Is In This Repo

This repository contains two closely related things:

If you are here to use the product, start with the product guide. If you are here to understand the original proof behind the direction, read the study.

Public Proof

The study package shows the original argument behind Evidpath: offline ranking metrics can miss important user-level tradeoffs.

Useful links:

Offline versus bucket story

Repo Guide

Background

The earlier public write-up that motivated this direction is here:

https://dev.to/alankritverma/why-offline-evaluation-is-not-enough-for-recommendation-systems-15ii

About

Deterministic interaction-testing for recommender audits and regression checks.

Resources

License

Code of conduct

Contributing

Security policy

Stars

Watchers

Forks

Releases

No releases published

Packages

 
 
 

Languages