Repository navigation
feat(blueprints): add continuous GenAI evaluation and prompt guardrail pipeline with Comet Opik - #437
Merged
MartinRst merged 2 commits intoOct 5, 2026
Conversation
…l pipeline with Comet Opik
MartinRst
approved these changes
Oct 5, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What
Adds an enterprise-grade production workflow blueprint: Continuous GenAI Evaluation and Prompt Regression Guardrails with Comet Opik (
flows/comet-opik-llm-evaluation-guardrail.yaml).This blueprint provides Kestra users with an automated quality gate for Generative AI applications and LLM prompt pipelines, continuously evaluating candidate prompts against benchmark datasets, measuring multi-dimensional metrics (answer relevance, factual hallucination prevention, and RFC 8259 JSON schema compliance), logging full experiment traces to Comet Opik, and enforcing hard quality thresholds with Slack alerting and human-in-the-loop review.
Blueprint Details
flows/comet-opik-llm-evaluation-guardrail.yamlcomet-opik-llm-evaluation-guardrailcompany.teamAI,Data(strictly validated againstvalidate-blueprint-tags.yml)LLM Evaluation & GuardrailsProblem Solved
Prompt engineering, model checkpoint updates, and retrieval-augmented generation (RAG) parameter tuning frequently introduce silent regressions. These regressions manifest as degraded answer relevance, increased hallucination rates, broken structured output formatting (such as invalid JSON), and subtle drift in brand alignment. Traditional unit tests cannot detect these non-deterministic failure modes.
Without continuous evaluation guardrails embedded directly into CI/CD pipelines and deployment lifecycles, flawed prompt changes can slip into production, degrading user trust and violating service level agreements.
Architecture and Workflow
Hacktoberfest 2026 Track 02 Compliance Checklist
setup_evaluation_context(io.kestra.plugin.core.log.Log)run_opik_evaluation(io.kestra.plugin.scripts.python.Commands)notify_slack_passed(io.kestra.plugin.notifications.slack.SlackIncomingWebhook)log_evaluation_passed(io.kestra.plugin.core.log.Log)log_evaluation_failed(io.kestra.plugin.core.log.Log)notify_slack_alert(io.kestra.plugin.notifications.slack.SlackIncomingWebhook)check_evaluation_guardrail(io.kestra.plugin.core.flow.If)require_human_approval(io.kestra.plugin.core.flow.Pause)ci_cd_webhook_trigger(io.kestra.plugin.core.trigger.Webhook)nightly_regression_sweep(io.kestra.plugin.core.trigger.Schedule)plugin-scripts-python(io.kestra.plugin.scripts.python.Commands)plugin-notifications(io.kestra.plugin.notifications.slack.SlackIncomingWebhook)extend.tags:['AI', 'Data'](Valid per.github/workflows/validate-blueprint-tags.yml, <= 3 allowed tags).extend.descriptionwith ASCII diagram, Mermaid chart, inputs table, runbook, extension ideas, and plugin links.Verification
The blueprint was verified locally:
validate-blueprint-tags.ymlscript pass verified with Python YAML parser.answer_relevance,hallucination_score, andis_json_valid, trace emission to Opik, and proper Kestra ion output formatting::{"outputs": ...}::.