# Recorded Claude web proposal and local verification

This is a record of a synthetic local experiment, not an installed-package model integration. The founder obtained a proposal through free Claude web on a phone and forwarded the full response. Provider identity is user-reported; the interface and model were not independently captured.

The local controller froze the operation sequence, pricing/cache requirements and check identities before the proposal. It applied the unchanged module, rejected a no-cache control, checked the candidate and checked the same code in a fresh analysis. The ordinary tests, sequence and both requirements passed; the input checks and fixture remained unchanged.

The recorded module uses `JSON.stringify([tenant, sku])` for the cache key in this example's string domain. Candidate SHA-256: `2dfde5b4bfee6ebdb9cba15407e9bd6d0430f78772bc79ed753318f4a67844b3`.

The opt-in controller used for this experiment is outside the accepted tarball and is not yet distributed through an independent public source repository. The downloadable example helper uses the supplied synthetic demo repair, rather than calling Claude or applying this forwarded proposal. Follow [the quickstart](QUICKSTART.md) to reproduce that packaged demonstration; use [the API contract](API.md) for trusted caller-authored inputs.

[Inspect the exact proposal, recorded results and portable provenance](../../claude-web-workflow.html).