Turn two CSV rosters into a schema-valid LDEX BEM transmission (press Cmd/Ctrl+Enter for a live preview):

/** DataSonnet
version=2.0
input payload application/csv
input coverage application/csv
output application/vnd.limra.ldex.bem+json;version=2.0
*/
// Two CSV rosters (demographics + coverage) -> a schema-valid LDEX BEM transmission.
// The carrier and employer envelope come from the LDEx plugin config; this script
// builds the employees. Value maps translate the source codes into LDEX values.
local ldex = import "ldex/bem.libsonnet";
local maps = import "valuemaps/maps.libsonnet";

// Relationship "E" marks the employee; everyone else is a dependent, grouped by SSN.
local employees = std.filter(function(r) r.Relationship == "E", payload);
local depsBySSN = ds.arrays.groupBy(std.filter(function(r) r.Relationship != "E", payload), function(d) d.SSN);
local covsBySSN = ds.arrays.groupBy(coverage, function(c) c.SSN);

local employeeObjects = std.mapWithIndex(function(i, emp)
  local eeID = "ee-" + ds.strings.zeroPad(i, 3);

  local dependents = std.map(function(dep) {
    dependentSocialSecurityNumber: dep.SSN,
    dependentRelationshipTypeCode: maps.relationship(dep.Relationship),  // S -> Spouse, C -> Child
    dependentName: { lastName: dep.LastName, firstName: dep.FirstName },
    dependentGenderCode: maps.gender(dep.Gender),                        // M/F -> Male/Female
  }, std.get(depsBySSN, emp.SSN, []));

  local coverages = std.map(function(cov) ldex.buildCoverage({
    productTypeCode: "CriticalIllness",
    coverageTierCode: maps.coverageTier(cov.CoverageLevel),              // EE -> Employee, EF -> EmployeeFamily
    benefitAmount: std.parseInt(cov.CoverageAmt),
    coverageEffectiveDate: cov.EFFECTIVE,
    employeePartyID: eeID,
  }), std.get(covsBySSN, emp.SSN, []));

  ldex.assembleEmployee({
    employeePartyID: eeID,
    employeeSocialSecurityNumber: emp.SSN,
    employeeName: { lastName: emp.LastName, firstName: emp.FirstName },
    employeeBirthDate: emp.DOB,
    employeeGenderCode: maps.gender(emp.Gender),
    employeeMailingAddress: ldex.buildAddress(emp),
    coverage: coverages,
  }, { dependent: dependents }),
  employees);

ldex.buildTransmission({ employee: employeeObjects })

→ a schema-valid LDEX BEM transmission (abbreviated):

{
  "transmission": {
    "employer": {
      "employerName": "Sample Demo Employer",
      "employee": [
        {
          "employeePartyID": "ee-000",
          "employeeName": { "lastName": "Doe", "firstName": "Jane" },
          "employeeGenderCode": "Female",
          "coverage": [
            { "productTypeCode": "CriticalIllness", "coverageTierCode": "EmployeeFamily", "benefitAmount": 20000 }
          ],
          "dependent": [
            { "dependentName": { "lastName": "Doe", "firstName": "John" }, "dependentRelationshipTypeCode": "Spouse" }
          ]
        }
      ]
    }
  }
}

_{Illustrative and trimmed for brevity. The carrier/employer envelope and value maps come from your project's LDEx configuration.}

Why Dot Star DX Studio

Benefits and group-insurance integration is still done in spreadsheets, hand-written EDI, and brittle SOAP. Dot Star DX Studio brings a modern, AI-assisted data-mapping workflow to the editor your team already uses, purpose-built for LDEx and benefits/insurance data.

Features

✦ DataSonnet mapping with live preview

First-class support for .ds transformation scripts: syntax highlighting, IntelliSense (completions, hover, signature help), and inline diagnostics. Press Cmd/Ctrl+Enter to run the transform and see the output instantly, with your input payloads auto-resolved from the workspace.

✦ Step-through debugging + Mapping Variable Inspector

Set breakpoints in a .ds script and F5 to debug it. The Mapping Variable Inspector shows local values captured on each run, so you can see exactly how a mapping evaluates.

✦ Rules authoring & evaluation

Author .rule.json / .rules.json rule files with language support and a visual Rule editor, evaluate them against your data, and manage rule configuration and providers without leaving the editor.

✦ Visual pipelines

Chain a mapping and a rules check into a runnable pipeline. The story-flow Pipeline Builder opens *.pipeline.json visually, a guided New Pipeline wizard gets you started, and Generate with AI hands context to your chat to author the mapping or rules for you.

✦ Business-friendly editors & reports

Edit value maps and rule variables in visual table editors instead of raw JSON, and read a per-field Mapping Report (confidence, source, and review flags) instead of digging through raw output.

✦ LDEx-aware

Built for the LIMRA LDEx standard: BEM/EOIS/BCM/RSP schema settings, validation presets, HIPAA-safe handling, and carrier/employer configuration surfaced as editor settings.

✦ Ask your AI assistant

A @datasonnet chat participant answers ds.*/std.* function questions, reviews your active script for issues, and looks up LDEx schema structure, in plain conversation.

✦ Your tools in any AI chat (MCP)

Turn Dot Star's tools on inside your AI assistant over MCP, so you can map, validate, and transform benefits data by just asking. The AI Tools panel in the Dot Star DX Studio sidebar shows what your license has turned on and switches it on in one click. On Cursor, Windsurf, or Claude Desktop, "Set up in another app" writes the right config for you. The tools work across your assistant's Ask, Plan, and Agent modes, starting with DataSonnet mapping.

✦ Cross-IDE

One extension for VS Code, Cursor, and Windsurf/Devin. The "Add AI Rules File" command drops the right instructions file for whichever editor you're in (.github/instructions, .cursor/rules, or .windsurf/rules).

Editor support: requires VS Code 1.101+ (and current Cursor / Windsurf, which track that base). The VS Code build uses the latest AI/MCP APIs, feature-detected so the extension still loads on the forks.

Getting started

1. Install Dot Star DX Studio from the Marketplace (or your provided .vsix).
2. Activate your license: run DX Studio: Enter Offline License Token and paste the token from your Dot Star account. (IAM sign-in is coming.) See the activation guide.
3. Open a .ds file and press Cmd/Ctrl+Enter to run your first transform.

On first run, a Getting Started walkthrough opens to guide you from activating your license to turning your AI tools on in your chat.

.ds syntax highlighting works for everyone; the engine, preview, debugging, and chat unlock with a datasonnet entitlement.

What's included

About Dot Star LLC

Dot Star LLC transforms workforce benefits & group-insurance technology: strategic consulting, hands-on engineering, and purpose-built accelerators that move carriers, benefit administrators, and brokers from legacy workflows to modern, AI-powered solutions. Learn more at benefits.dotstar.ai.

Licensing & Support

Dot Star DX Studio is free to install. Authoring (opening and editing mappings, rules, and pipelines) is available to everyone; running transforms, evaluating rules, running pipelines, and the AI tools require a Dot Star license. The extension verifies an offline license token — no account or network connection is required to run licensed features.

• License inquiries & support: info@dotstar.io
• Activate a license: run DX Studio: Enter Offline License Token from the Command Palette, or see docs/licensing/activation.md.

This is a Preview release; some features marked "Coming" are still in progress.

Standards & Trademarks

Dot Star DX Studio is an independent product that implements the LIMRA LDEx (LIMRA Data Exchange) standards - including BEM, EOIS, RSP, and BCM - for benefits/enrollment data interoperability. LIMRA, LDEx, and the LDEx standard names are trademarks of LIMRA. Dot Star LLC is not affiliated with, sponsored by, or endorsed by LIMRA. All other trademarks are the property of their respective owners.

_{Proprietary software, licensed not sold; see LICENSE.md. Building on it? See CONTRIBUTING.md.}