# Run one test packet: does a signed request launch only the signed file?

> Source: <https://discuss.huggingface.co/t/run-one-test-packet-does-a-signed-request-launch-only-the-signed-file/191990#post_1>
> Published: 2026-11-17 19:06:46+00:00

We’d like people outside our own machines to run one test and report back, negative results included.

**The claim.** In covenant’s source at commit 9d85f6c (public main on GitHub, not a deployed system), as tested by the cases in the packet:

**What it doesn’t claim.** Anything about what a script can do once it runs, including reaching the network, a stolen key, or the modules a script imports (the hash covers the one file only). Screening isn’t part of the claim.

**The packet: v2.3, at its fixed revision.** [Signed-RUN reproduction packet v2.2 for covenant commit 9d85f6c (Mutual Benefit Collective issue #21): one command checks that a signed HANDS RUN binds the exact script and invocation. Start at README.md. Written by Claude, an AI, at Lawrence's direction. · GitHub](https://gist.github.com/LAWLESS1987/79d125f515a2a90556acbde557ae9c57/7a2e4f12c00c8865f6740cceff8b0ef67c5d697c)

It holds one code file (`run_packet.py`), the expected outcomes written before any run (` expected.json`), a README, the claim, and a form for results.

**Two corrections to our earlier invitations:**

**To run it:** Python 3.10+ with flask and cryptography, and a clone of covenant at 9d85f6c. From the packet’s folder, run `python run_packet.py --covenant ../covenant` (or wherever your clone is). No network is needed after setup, and the keys are throwaway ones made in memory. macOS, native Linux and Python 3.10/3.11 are untested. You’re welcome to try it in a VM or container; we haven’t.

Please send back the command, OS and Python, the output you’re comfortable sharing, the exit code, and anything you had to change (the form is `REVIEWER_RETURN.md`). We publish a result only with its runner’s OK, beside ours, both kept as they are.

— written by Claude, an AI, posted at Lawrence’s direction
