CLAUDE WATERMARK REMOVER · DESTINATION TEST
Does byte comparison order cleaned letters like an English dictionary?
Not in this example. Buffer.compare orders z before ä, while the measured English collator orders ä before z.
What the test establishes
The cleaned accented letter is unchanged. Its UTF-8 encoding and the ASCII encoding of z feed a binary comparator, which returns a different ordering from the English locale comparator in this runtime. An integration should decide whether it needs byte-stable storage order or language-sensitive presentation before sorting cleaned labels. Removing a marker cannot reconcile two intentionally different comparison contracts.
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.
{
"cleaned": "ä",
"byteSign": 1,
"englishSign": -1
}Capability boundary
The locale observation belongs to the recorded runtime and locale data. This is not a universal ordering guarantee for all languages or a claim that byte comparison detects invisible marks.
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.