Skip to content

feat: LLM check type support in contract JSON schema#2613

Draft
LaurenDebruyn wants to merge 2 commits intomainfrom
feat/llm-checks-and-remediation
Draft

feat: LLM check type support in contract JSON schema#2613
LaurenDebruyn wants to merge 2 commits intomainfrom
feat/llm-checks-and-remediation

Conversation

@LaurenDebruyn
Copy link
Copy Markdown

@LaurenDebruyn LaurenDebruyn commented Mar 7, 2026

Summary

  • Adds JSON schema definition for the new llm check type in data contracts (prompt, threshold, references)
  • Adds references property to the llm check schema for reference dataset lookups during LLM validation

Note: Remediation contract parsing was added and then removed — remediation is handled entirely by the remediation-cli (Gravity), not soda-core.

Companion PR: sodadata/soda-extensions#298 — feat/llm-checks-and-remediation (soda-llm package with tools, reference lookup, check implementation)

Test plan

  • JSON schema is valid JSON
  • CI green on matching branch with soda-extensions

🤖 Generated with Claude Code

@LaurenDebruyn LaurenDebruyn self-assigned this Mar 7, 2026
@LaurenDebruyn LaurenDebruyn changed the title feat: LLM check type support and contract remediation parsing feat: LLM check type support in contract JSON schema Mar 10, 2026
LaurenDebruyn and others added 2 commits April 15, 2026 11:26
Without this, fuzzy_duplicate checks with no explicit `name:` in the
contract fall through to using the raw type name "fuzzy_duplicate" as
the check_name written to the DW, instead of the human-readable
"No fuzzy duplicate values".

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
@LaurenDebruyn LaurenDebruyn force-pushed the feat/llm-checks-and-remediation branch from 3a8e2b5 to e424ecb Compare April 16, 2026 18:37
@sonarqubecloud
Copy link
Copy Markdown

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant