# Bounty Evidence Desk: purchase and local-use guide

Version 0.1.1. Product ID: `bounty-evidence-desk-v1`.

**Offline review preview. Not settlement authorization or live eligibility verification.**

## Inspect before approval

Read the [product metadata](index.json), [customer terms](TERMS.md), [license](LICENSE.md) and [free synthetic review](examples/review.md). The price is **USD 7.00 (700 cents), one time**, through Stripe MPP. This ware has no subscription, browser card-entry checkout or crypto purchase route. A Stripe merchant profile page is not a payment form for this download.

The paid ZIP contains the CLI, wheel, source, documentation, agent instructions, synthetic workflow and sample reports. It runs offline using Python's standard library. A public read or unpaid challenge does not authorize or execute payment.

## Purchase and private delivery

Use a compatible payment-aware client, an authorized Stripe-issued Shared Payment Token and explicit buyer approval. Generic read-only MCP discovery does not pay. Do not submit payment credentials using a general-purpose browser, chat, URL, log or a model tool argument.

1. Before requesting a challenge, have the supported client generate and durably save a private 256-bit recovery key, represented by 64 lowercase hexadecimal characters. Keep the key out of URLs, public pages, chat, source control and logs. The key is required for private recovery; a public payment reference alone is insufficient.
2. The selected client's request is `GET https://lumenhouse.xyz/api/wares/bounty-evidence-desk-v1/purchase/card`, carrying the saved key in `X-Lumen-Recovery-Key`. This creates an unpaid quote. Verify the returned product ID, USD 700-cent price, exact release hash, license and terms. An expected HTTP 402 is an unpaid challenge, not a failed charge.
3. Ask the buyer to approve the exact merchant, product, USD 7.00 price, applicable fees and terms. Submit one authorized Stripe MPP payment through the supported client. Do not purchase both this and another rail, or use another product's challenge.
4. After confirmed payment, save the receipt and private delivery information. Retrieve the ZIP from the returned `/api/bounty-downloads/{order_id}` URL with `Authorization: Bearer <saved-private-recovery-key>` through the supported client. Verify exact byte count and SHA-256 against `index.json` before opening the package.
5. If the reply is lost, pending or uncertain, use the same saved key for Bearer recovery on this same product's original purchase route. Do not sign again, create a new order or pay again. Honor `Retry-After` on rate limits. A challenge can expire; an expired challenge alone does not authorize a replacement charge.

Without payment confirmation, private download is denied. An absent key requires a private key; an unknown order cannot be recovered by a public transaction ID. If recovery cannot resolve the outcome, contact `buscheo@gmail.com` with non-secret order information. Never send the recovery key or payment token by email. No indefinite hosting or automatic refund is promised.

The House read-only MCP exposes the offer and documents. This purchase uses the product's published Stripe MPP HTTP route; do not infer support from the separate Manifest-native payment MCP endpoint.

## Install the delivered kit

After verifying the ZIP, extract your purchased software package into a new local directory. Do not extract or execute contributor evidence archives. From the kit directory:

```sh
python3 -m venv .venv
.venv/bin/python -m pip install --no-index --no-deps dist/bounty_evidence_desk-0.1.1-py3-none-any.whl
.venv/bin/bounty-evidence-desk --version
.venv/bin/bounty-evidence-desk example --out demo
```

Read `START_HERE.md`, `README.md`, `SKILL.md` and `docs/contracts.md`. The example command copies synthetic fixtures into a new directory; it makes no qualification decisions. Use the installed CLI prefix `.venv/bin/bounty-evidence-desk` for commands below.

```sh
.venv/bin/bounty-evidence-desk init --task demo/fixtures/promotion/task.json --desk demo/private/desk.json
.venv/bin/bounty-evidence-desk import --file demo/fixtures/promotion/submissions.json --desk demo/private/desk.json
.venv/bin/bounty-evidence-desk observe --file demo/fixtures/promotion/observations.json --desk demo/private/desk.json
.venv/bin/bounty-evidence-desk state --file demo/fixtures/promotion/states.json --desk demo/private/desk.json
.venv/bin/bounty-evidence-desk review --desk demo/private/desk.json --root demo/fixtures/promotion --as-of 2026-11-13T12:00:00Z --out demo/review
```

Read each exact version's inert evidence and the review. Copy the unapproved decision template to a private reviewer file. Deliberately record your reason, reviewer reference and qualification, preserve its current binding and evidence references, and set `authored: true` only for judgments you made. A newer packet cannot borrow missing evidence from an older one.

```sh
.venv/bin/bounty-evidence-desk decide --file demo/private/decisions.json --desk demo/private/desk.json --root demo/fixtures/promotion --as-of 2026-11-13T12:00:00Z
.venv/bin/bounty-evidence-desk allocate --desk demo/private/desk.json --root demo/fixtures/promotion --as-of 2026-11-13T12:00:00Z --winners demo/fixtures/promotion/winners.json --out demo/allocation
```

The supplied winner-list exercise pins `demo-A-v1`, then `demo-B-v1` and `demo-C-v1`, using 3334/3333/3333 bps. Author the invented fixture judgments after reviewing its packets; keep incomplete `demo-A-v2` separate. Those shares are unequal. No executable settlement command or address list is produced.

For real tasks, import actual task-specific terms, caps, windows, currency, decimals, reward and provenance. Unknown financial or ordering terms prevent a complete allocation preview. Never infer community permission from a URL or verified live eligibility from a supplied state snapshot. Keep private desk/source/reviewer records private and inspect output text before sharing.

## Verification limits

67 source and clean-installed-wheel tests passed on Linux with Python 3.12.14. macOS and other Python versions remain untested. These CLI checks do not prove source truth, permission, live eligibility, contract rounding or paid delivery. No real purchase or successful live paid fulfillment is claimed by this guide.
