wai upscale and wai tonemap: an exact derivation from the command line, with its record and its check #578

Merged

dcharlot merged 2 commits from wai/upscale-tonemap-door into main 2026-11-02 21:47:29 -05:00

Conversation 0 Commits 2 Files changed 17 +1002 -6

dcharlot commented 2026-11-02 08:43:53 -05:00

Owner

Copy link

WAI can verify an upscale record and a rendition record, but no door in the toolchain could make one. That logic lives in waiTransport's providers, on the wrong side of the line: WAI holds every open ability, and waiTransport operates them. These commands also give media.upscale and media.tonemap a real entry in the catalogue, which the coming tariff prices by name.

The commands

wai upscale run <in.png> --prior <p.wsr> [--derivation sr2|sr4] -o <out.png>
    [--record <out.json> --envelope <in.wai> --key <seed>]
wai upscale verify <record.json> --envelope <in.wai> --prior <p.wsr> [--picture <out.png>]

wai tonemap run <in.wai> --headrooms <h,h,...> --out <dir> [--input-class <class>]
    [--record <out.json> --key <seed>]
wai tonemap verify <record.json> --envelope <in.wai> [--renditions <dir>]

• run makes the output, and with --record signs the record. Without it, no key is needed.
• verify recomputes the record under require-proof and holds the output to it, printing the outcome as JSON and exiting 1 on a refusal.
• exact_upscale::make and exact_tonemap::make are the functions underneath. They return the record's body for the caller to sign, so a service with its own key can use them.

Limits:

• The upscale's input is an 8-bit RGB PNG, which is what the reader in png_still holds.
• The tonemap's input is a still: a WAI2 of a PNG base and its gain map. The existing run_graph and tone-mapping limits apply unchanged.

Why run: the catalogue refuses a command that's the start of another, so wai upscale can't sit beside wai upscale verify.

What ran

• tests/cli_derive.rs, new, runs the binary end to end. What run writes is accepted by each extension's verifier from those files alone, and refused with another prior, another envelope, an altered picture or an altered rendition. Bad arguments are refused too.
• tests/cli_ops.rs, with both features: 10 passed, including the new operations under --dry-run. With quickstart alone: 47 passed for the binary and 10 for cli_ops.
• Catalogue unit tests: 6 passed. catalogue/ops.json is regenerated.
• wai breaking against the merge base: nothing unacknowledged. check-tests-in-ci: passes, with the new test added to the conformance job.

Not done here: waiTransport's providers still have their own copy of this logic. They move to these functions when it next re-pins WAI.

🤖 Generated with Claude Code

WAI can verify an upscale record and a rendition record, but no door in the toolchain could make one. That logic lives in waiTransport's providers, on the wrong side of the line: WAI holds every open ability, and waiTransport operates them. These commands also give `media.upscale` and `media.tonemap` a real entry in the catalogue, which the coming tariff prices by name. ## The commands ```text wai upscale run <in.png> --prior <p.wsr> [--derivation sr2|sr4] -o <out.png> [--record <out.json> --envelope <in.wai> --key <seed>] wai upscale verify <record.json> --envelope <in.wai> --prior <p.wsr> [--picture <out.png>] wai tonemap run <in.wai> --headrooms <h,h,...> --out <dir> [--input-class <class>] [--record <out.json> --key <seed>] wai tonemap verify <record.json> --envelope <in.wai> [--renditions <dir>] ``` - `run` makes the output, and with `--record` signs the record. Without it, no key is needed. - `verify` recomputes the record under `require-proof` and holds the output to it, printing the outcome as JSON and exiting 1 on a refusal. - `exact_upscale::make` and `exact_tonemap::make` are the functions underneath. They return the record's body for the caller to sign, so a service with its own key can use them. **Limits:** - The upscale's input is an 8-bit RGB PNG, which is what the reader in `png_still` holds. - The tonemap's input is a still: a `WAI2` of a PNG base and its gain map. The existing `run_graph` and tone-mapping limits apply unchanged. **Why `run`:** the catalogue refuses a command that's the start of another, so `wai upscale` can't sit beside `wai upscale verify`. ## What ran - `tests/cli_derive.rs`, new, runs the binary end to end. What `run` writes is accepted by each extension's verifier from those files alone, and refused with another prior, another envelope, an altered picture or an altered rendition. Bad arguments are refused too. - `tests/cli_ops.rs`, with both features: 10 passed, including the new operations under `--dry-run`. With `quickstart` alone: 47 passed for the binary and 10 for `cli_ops`. - Catalogue unit tests: 6 passed. `catalogue/ops.json` is regenerated. - `wai breaking` against the merge base: nothing unacknowledged. `check-tests-in-ci`: passes, with the new test added to the conformance job. **Not done here:** waiTransport's providers still have their own copy of this logic. They move to these functions when it next re-pins WAI. 🤖 Generated with [Claude Code](https://claude.com/claude-code)

dcharlot added 1 commit 2026-11-02 08:43:53 -05:00

wai upscale and wai tonemap: an exact derivation from the command line, with its record and its check ... 3ba5bccf78

The catalogue lists what works, and the toolchain could verify an upscale
record and a rendition record without any door that made one. The doing lived
in a hosted service's providers, which is the wrong side of the line: WAI holds
every open ability.

`wai upscale run` and `wai tonemap run` make the picture and, with `--record`,
sign the record. `wai upscale verify` and `wai tonemap verify` recompute that
record under require-proof from what it names, and hold the output to it.
`exact_upscale::make` and `exact_tonemap::make` are the functions under them,
and they return the record's body for a caller to sign, so a service that signs
with its own key can use them too.

The commands are `run` and `verify` because the catalogue refuses a command that
is the start of another: `wai upscale` beside `wai upscale verify` is a form
that can never be told apart from a file named verify.

Co-Authored-By: Claude Opus 5.5 <[email protected]>

dcharlot added 1 commit 2026-11-02 12:12:32 -05:00

wai-studio: the action table holds the catalogue's new operations ... bc65134edf

Co-Authored-By: Claude Opus 5.5 <[email protected]>

dcharlot referenced this pull request 2026-11-02 12:23:12 -05:00

receipt-ledger: tariff version 6 prices an endpoint and a third party's usage, and bills an upscale and a tone mapping by what re-derives them #579

dcharlot merged commit 643f700294 into main 2026-11-02 21:47:29 -05:00

dcharlot referenced this pull request from a commit 2026-11-02 21:47:30 -05:00

Merge pull request 'wai upscale and wai tonemap: an exact derivation from the command line, with its record and its check' (#578) from wai/upscale-tonemap-door into main

dcharlot referenced this pull request 2026-11-02 22:32:36 -05:00

Quantum jobs on a provider outlive what sent them: the record, the command line, the desktop app and the Studio #590

dcharlot referenced this pull request 2026-11-02 22:32:58 -05:00

wai-quantum-qpu and wai-quantum-cli: a job on a provider outlives what sent it #581

dcharlot referenced this pull request 2026-11-02 22:59:00 -05:00

receipt-ledger: tariff version 6 prices an endpoint and a third party's usage, and bills an upscale and a tone mapping by what re-derives them #591

Sign in to join this conversation.

Reviewers

No reviewers

Labels

Clear labels

No items

No labels

Milestone

Clear milestone

No items

No milestone

Projects

Clear projects

No items

No project

Assignees

Clear assignees

No assignees

1 participant

Notifications

Subscribe

Due date

The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set

Reference

Transaction-Science/open-standards!578

No description provided.