CLAUDE WATERMARK REMOVER · DESTINATION TEST
Why does the same cleaned binary export produce two numeric values?
The bytes for AB read as 16706 by default and 16961 with little-endian enabled.
What the test establishes
Two reads use the same byte storage and offset. Only the byte order option changes. This isolates a destination interpretation error from any character removal. A receiving binary format needs an explicit byte order contract; a readable preview cannot establish that contract. Preserve the original bytes when investigating a mismatch and record the exact reader arguments. Neither number is a watermark score or an identification result. They are numeric interpretations of the two ASCII bytes produced after the callback. The test uses a fresh two-byte array so backing-store offsets cannot account for the difference.
Reproduce the observation
Save tested-app.js and reproduce.cjs together, then run node reproduce.cjs. Compare its output with the recorded observation. The harness executes the actual homepage callback in a minimal DOM and records its resulting field values and method calls. Destination operations run in Node.js; the homepage DOM is a controlled substitute. Runtime: v24.22.1. No submitted text or genuine Claude output is used.
{
"bytes": [
65,
66
],
"default": 16706,
"littleEndian": 16961
}Capability boundary
One unsigned two-byte read is measured. Signed values, larger records and real network protocols are excluded.
This Claude watermark remover edits a small selected character set. These callback observations do not establish authorship, detector scores, statistical-watermark removal or end-to-end browser behavior. For real work, keep the original and compare the exact result at its destination.
Primary material and next step
The tested first-party source snapshot and complete harness are the primary material for this page. For broader scope, read invisible Unicode versus AI watermarks, or return to the cleaner.