whiteducksoftware / whiteducksoftware/flock
🧮 [FEATURE] [1.0] Evaluation Harness
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 120
- Forks
- 14
- Avg merge
- 19h 32m
- Merged PRs (30d)
- 8
Description
Is your feature request related to a problem?
We do not have a standardized way to evaluate agent outputs against ground-truth datasets. Teams resort to manual spot checks or custom scripts, which makes it impossible to track quality regressions or compare models objectively. This blocks our 1.0 goal of shipping enterprise-grade evaluation tooling.
Describe the solution you want to see
- Build an evaluation harness that can ingest CSVs or Hugging Face datasets containing inputs and expected outputs, execute Flock workflows, and compute a configurable set of metrics (BLEU, ROUGE, accuracy, hallucination flags, cost, latency, etc.).
- Provide a declarative configuration file (YAML/JSON) to describe datasets, orchestrator setup, and metric suites so evaluations are reproducible.
- Output results as structured artifacts (saved to DuckDB/Azure storage) and human-friendly reports (Markdown/HTML) that can be shared with stakeholders.
- Integrate the harness with CI and the dashboard so product teams can run ad-hoc evaluations and track trends over time.
Describe alternatives you have considered
Current practice is to run workflows manually and eyeball the outputs or write ad-hoc Python scripts tied to specific experiments. Those approaches don’t scale, have no reporting, and can’t be reused across customers.
Additional context
Leverage the same storage abstraction we plan for persistence so offline runs and hosted evaluations share code. Pair this work with the benchmarking initiative to reuse dataset loaders and metric implementations where possible.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reviewing the planned persistence storage abstraction and the benchmarking initiative, since the issue calls for shared dataset loaders and metric implementations. Map how Flock workflows are currently executed and how the dashboard and CI integrate before defining the harness boundaries. Done means reproducible CSV or Hugging Face evaluations with configurable metrics, structured DuckDB or Azure artifacts, Markdown or HTML reports, and CI/dashboard integration.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- ai, data, testing-qa
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100