Nativ JSON locale exercise, 31 October 2026 Files: - en.json: fictional source catalogue with five text values and non-text metadata. - fr-manual-reconstructed.json: output from the released Nativ v1 JSON helper functions, using manually supplied French replacements. This is not AI-generated output or a French-quality benchmark. - fr-broken.json: deliberately corrupted copy (renamed key, changed variable, shortened array, changed metadata type). - validate.py: original standard-library Python exercise checker. No packages or network calls. Run: python3 validate.py en.json fr-manual-reconstructed.json Expected: zero structural findings, exit 0. This does not approve language quality. python3 validate.py en.json fr-broken.json Expected: five structural findings, exit 1. The checked adapter is https://github.com/Nativ-Technologies/nativ-github-action/blob/a07ba35c83ce64dc6174435c69dffa3fabbb01ff/translate_json.py Only collect_strings and set_nested were exercised offline. The SDK was not imported, no client was constructed, and no paid translation or CI action was run. The five replacements were applied to a deep copy of the source. The supplied output and checker are independently inspectable. Scope: this checker expects the same keys, nesting, array length/order and non-text values, and simple {{name}} placeholders with ASCII names and no format modifiers. It ignores object-key order. It rejects duplicate keys, NaN/Infinity and unsupported brace syntax instead of silently approving ICU or advanced interpolation. It also flags an empty target for nonempty source. Number representations are conservative: Python int versus float is a type change. Not covered: language quality, meaning, semantic order of translated array entries, HTML/rich-text correctness, URLs, printf variables, ICU syntax/plural branches or full i18next interpolation. A target-language plural schema may legitimately add keys; do not apply this same-shape check unchanged to such a catalogue. Use the application's actual message parser and runtime tests. Observed v1 adapter boundaries: dot/bracket path delimiters need care with literal keys; root arrays and arrays nested directly inside arrays are not collected by its current traversal. The action writes source basenames inside language-name directories. Check coverage and paths on a small fixture before a large run.