MG-IDENTITY-002 + SFC-IDENTITY-001 · Data integrity · Repaired
Invisible Unicode IDs in reviewed CSV exports
A value can contain characters and still fail to provide a visible product identity.
Two of our CSV tools accepted different invisible-only SKU values into explicitly approved exports. The findings concerned invalid identity data in downloaded files. They did not demonstrate script execution, an inventory update or financial loss. [1]
This is an explanation of existing repaired findings from Browser Busters, Ten Thirty Two’s AI-assisted review project. Both had low, conditional application data-integrity impact; neither was a new browser-engine vulnerability.
Two tools, different validation gaps
In Margin Guard, a SKU made only of U+200B ZERO WIDTH SPACE appeared without a visible part name. Matching fictional cost and selling-price files allowed that row to be audited, classified below target and exported after manual approval. [1]
Supplier File Converter already rejected that character and formula prefixes. A value made only of U+3164 HANGUL FILLER nevertheless passed its validation. After the visitor mapped columns, validated and reviewed the rows, the unchanged value reached the import CSV. These were separate observed paths, not a claim that the tools shared identical validation. [1]
| Application | Required interaction | Observed output |
|---|---|---|
| Margin Guard | Matching source files, audit and explicit approval | Invisible-only SKU in the changes CSV |
| Supplier File Converter | File selection, column mapping, validation and review | Invisible-only SKU in the import CSV |
Validate identity without silently rewriting it
The repair requires meaningful visible identity content alongside the checks for unsafe formatting controls. Margin Guard also rejects the tested directional formatting before pricing advice or approved export. Invalid rows remain available as source evidence for correction; the application does not silently delete characters or invent replacement identifiers. [1]
The Hangul filler case exposed the limit of the Converter’s existing blacklist. Adding only that one missed character would not establish a general identity rule. The repair instead checks the content requirement and preserves legitimate text, rather than treating all non-ASCII identifiers as invalid.
That preservation had a positive control: six valid identifiers, including leading-zero, Arabic, CJK and joiner-containing values, retained their exact text through the paired conversion and Margin workflows, including changes and rollback exports. These controls check that blocking a bad input does not require altering the good ones. [1]
New regressions failed on the original source. After repair, 28 Margin core checks, 12 Converter core checks and three targeted browser cases passed. The repairs were recorded in Margin Guard Release 3 and Supplier File Converter Release 2. [1]
Inspect the entire reviewed-export path
A visible table is only one part of this workflow. For a similar authorized local test, follow synthetic rows through validation, approval and the downloaded file. A useful check compares exact source and output values, not only their appearance on screen.
- Include invalid identity cases and legitimate multilingual or leading-zero controls in the test plan.
- Check that invalid rows remain inspectable but cannot enter the approved output.
- Confirm that accepted identifiers stay unchanged through downstream and rollback exports.
For a parts reviewer, an apparently blank identifier is a reason to resolve the source record before import. This case does not establish that every blank-looking cell is the same defect or that another supplier’s file contains these characters.
Evidence and limits
The original export paths were reproduced with fictional local files in fresh Edge contexts. No real inventory import or third-party spreadsheet execution was attempted. The observations do not establish how every Unicode character renders in every font, or guarantee all identifiers across browsers and devices. [1]
[1] Original application evidence. Browser Busters evidence file, findings MG-IDENTITY-002, SFC-IDENTITY-001 and identityRegressionSummary. The findings hub keeps these observations separate from historical vendor advisories.