Quoted commas and embedded newlines
A note contains a comma, escaped quote and newline. Changing its content should fail the selected protection even though the CSV is well formed.
Expected: Protect note — failed.
Moyan AI Work Check
Ten public CSV checks
These synthetic before-and-after files test deterministic constraints, not AI product quality. Products are not yet tested. Each case has original downloads, declared rules, expected behavior and a working local checker. A pass cannot establish factual or business correctness.
Method: read the scenario, download both files if useful, load the test and run its predeclared rules. Compare the observed outcome with the expected outcome. Inspect exact changes and review flags. All records are synthetic, and no model generated the edited outputs.
Unicode is preserved exactly
Accents and non-Latin scripts are data. This unchanged example passes exact protection; no transliteration or Unicode normalization is performed.
Expected: Protect name — passed.
Leading zeros are part of an ID
An edited identifier loses its leading zeros. Matching uses strings, so 001 and 1 represent different keys.
Expected: Preserve IDs — failed.
Remove one exact duplicate
Two identical records share a key. The declared change is minus one row, with one surviving record per original key. Protection is not checked when original keys repeat.
Expected: Deduplicate by key — passed.
Near duplicates remain distinct
Ada and ada have different keys. A case-insensitive merge removes a legitimate distinct ID in this test. Deduplication does not authorize fuzzy merging.
Expected: Deduplicate by key — failed.
Blank is different from zero
A missing amount becomes zero. The protected column fails and a declared total remains not checked because the original blank has no declared numeric meaning.
Expected: Total amount — not checked.
Locale numbers need interpretation
Comma decimals and thousands separators are intentionally ambiguous. The checker refuses to guess a numeric locale or certify the sum.
Expected: Total amount — not checked.
Protected values and offsetting totals
Two amounts change in opposite directions. Their sum still passes, while exact protection fails. This demonstrates why a matching total cannot establish correctness.
Expected: Protect amount — failed.
A record is omitted
The edited file omits one customer. The unchanged-row expectation and ID preservation fail. Missing cells appear as null in the report, distinct from empty strings.
Expected: Row count — failed.
Dates and formula-like text stay unexecuted
An unchanged ambiguous date and formula-like text need review even when ID and row rules pass. Download fixtures as text; spreadsheet programs may execute formula-like cells.
Expected: Dates and ambiguous values — not checked.