DEDUPED Hot AI repos, turned into use cases Get 5 a day

How to verify the exact CSV bytes behind a paired statistics run with Forest

Retrieve the retained input file and provenance record for a paired statistics analysis in FOREST.

  • Research
  • Advanced
  • 1 hour
  • From the README
  • Any agent

Who it is forA reviewer or lab member who must confirm which exact data file produced a reported paired statistic.

The problemA source CSV may be changed later, so the file on disk no longer proves which bytes were analyzed.

The outcomeThe retained input file, its SHA-256 and size from the run metrics, and a confirmed link between the analysis and the input.

What you need first

  • Python 3.11 or newer
  • Node.js 22 or newer for the Web workspace
  • Git installed on the worker machine
  • A model provider configured in Settings or through the API
  • An explicit spending budget and execution limits set before unattended runs
  • tectonic or pdflatex if you want PDF compilation

Steps

  1. Submit paired statistics input to POST /api/projects/{id}/statistics/paired.
  2. Read the run and its input_provenance object with GET /api/runs/{run_id}.
  3. Download the retained bytes with GET /api/projects/{id}/download?path=runs/{run_id}/paired-input.csv.
  4. Compare the SHA-256 of the downloaded file with the value in input_provenance.

Prompt for your agent

Using the FOREST API on <base URL>, fetch run <run ID> for project <project ID>, download its retained paired-input.csv, and compute the SHA-256 of the downloaded bytes. Report whether it matches the input_provenance hash in the run record. Verify that the downloaded path is runs/<run ID>/paired-input.csv.

Caveat. The provenance records the bytes the worker consumed, not the bytes at enqueue time, and it is not a general file-version history.

Share: X LinkedIn Hacker News Email Copy link

Disclaimer

Deduped lists open-source repositories that belong to other people. We do not own, maintain, audit, or vouch for any of them, and a repo appearing here is not an endorsement or a safety check. The use cases, steps, and prompts are written by AI and may be incomplete, outdated, or just wrong. Where a use case is marked "Seen in the wild", we link to public posts where someone described something similar, but we have not verified those posts and the use case itself is still our AI's own write-up. Use all of this at your own risk. Only run code, commands, or agents on systems and accounts you are authorized to use, and read the code and every command before you run it, especially anything that touches credentials, files, or the network. Nothing here is professional, security, legal, or financial advice. All trademarks and project names belong to their respective owners, and their use here does not imply affiliation. Content is provided as is, without warranties of any kind. Found a mistake, a safety problem, or something you want removed? Email [email protected] and we will look at it promptly. Full disclaimer page