Synthetic local reference · 2026-11-02.1

Preserve policy periods and insurer-scoped relationships.

A synthetic policy-history migration reference covering a missing period, changed holder, exact premium drift and a broken scoped relationship.

Declare the policy identity.

This example keys policy periods by insurer, policy number and version. Named insureds are keyed by insurer and holder ID. Policy-to-holder relationships must resolve within the same insurer. Start and end dates are compared as declared exact values; the fixture does not establish a universal insurance date model.

The failing input omits a historical period, changes a holder and shifts a premium by 0.01. It produces four investigation groups, including the broken target relationship. The repaired supplied-scope control exits 0. A separate shared-defect control demonstrates that matching rows can still contain invalid relationships.

Turn findings into a first-wave boundary.

Export the handoff to obtain an acceptance brief, findings and input/tool hashes. The reference workflow also exercises 15 synthetic cases. Proposed owners and release gates remain unconfirmed until the actual source, consumer and operating owners supply their evidence.

For a real project, define the retained history, capture boundaries, current and historical consumers, relationship semantics, cutover and recovery checks. Choose what to share with Jextra; running this tool does not submit a request or subscribe you to follow-up.

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.