Synthetic local reference · 2026-11-02.1

Validate supplied JSON migration snapshots locally.

Inspect and run a dependency-free Node CLI with failing, repaired and shared-defect policy-history controls, then export an implementation brief.

Use it for a bounded comparison.

The CLI compares explicitly mapped source and target JSON rows using complete keys, exact or declared field rules and required scoped relationships. Decimal strings preserve precision. It can export a findings report and a starting implementation brief without sending records to Jextra.

Use SQL or database-native checks when the work should run inside the database. This reference is useful when your agent already has authorized JSON captures and needs a reproducible local check and handoff artifact.

Compatibility and limits.

Requires Node 22 or newer. No package installation, account or customer upload is needed for these local commands. The audit accepts at most 20,000 supplied rows per side per comparison, 12 comparisons and 50,000 rows across a bundle; input files must be below 50 MB. Partition larger captures deliberately.

The report describes only supplied rows and declared mappings. It does not verify extraction completeness, live business behavior, unmapped relationships, authorization or production acceptance. The repaired reference is generated from synthetic source mappings; it is not a repair procedure for customer data.

Run the reference locally.

Download the CLI, metadata and three JSON inputs into one new folder. Inspect the source and compare its SHA-256 with the version file before running. The full instructions include an integrity check. These commands do not send records or contact Jextra.

node jextra-workflows.mjs audit --input policy-history-audit.json --out failing-report.json
# Expected exit 2: differences in the deliberately flawed input.

node jextra-workflows.mjs audit --input policy-history-repaired.json --out repaired-report.json
# Expected exit 0: no differences in the supplied scope.

node jextra-workflows.mjs audit --input policy-history-shared-defect.json --out shared-defect-report.json
# Expected exit 2: both sides agree, but the required relationship is broken.

node jextra-workflows.mjs test --workflow insurance-fnol --out reference-tests.json
# Expected exit 0: 15 synthetic reference cases pass.

node jextra-workflows.mjs handoff --input policy-history-audit.json --workflow insurance-fnol --dir new-handoff
# Expected exit 0: files written. Findings and release gates remain open.

Exit 1 means invalid input or a command error. Exit 2 is the expected result for the two defect controls. A handoff exit of 0 means the files were written; it does not approve the migration. Keep triage output and any optional local exception details private.

Use the brief with your team.

The new-handoff folder contains an implementation brief, acceptance summary, audit report and hashes. Review the exported content before sharing. No contact request or subscription is created by a local run.

Discuss a first implementation wave

Choose the high-level summary you want to share. Inspection of private systems, production validation, cutover and operating responsibility belong in an agreed implementation scope.