Independent by design · no pay-to-rank placements  · How we evaluate tools →
Anclum Submit
J

jessejamesrich/edd

Independent directory — not the official site. Details below come from the project's public repository.

File-based evaluation method for building non-deterministic AI systems

Before you install: no copy-paste command · license MIT

First step: nothing runnable here yet - start from the repository: https://github.com/jessejamesrich/edd

updated 2026-11-18
View on GitHub ↗Direct link · no redirect page
Star count
0 ★ · jessejamesrich/edd · read from the GitHub search API · (checked 2026-11-19 20:00:48)
Source
read directly from its GitHub page · type: open-source project
Harvest history
first seen 2026-11-18 · last seen 2026-11-20 · seen 3× · listed by 1 sources
Score
score 103 · 1 sources · repo
FAQ (answers come from our records)
Who is it for?
We filed it under these tags: Open Source. The tags come from the entry itself, not a taxonomy we imposed.
Who maintains it?
repository jessejamesrich/edd;first catalogued 2026-11-18;last seen 2026-11-20。There is no official certification or quality rating here — we record sources and dates only.
README excerpt (English, untranslated) · Read the full README on GitHub →

# Evaluation-Driven Development (EDD)

Excerpted from the repository README (abridged)

A lightweight methodology for building non-deterministic systems — AI
generation, retrieval, agents, classifiers — where "quality" is a spectrum, not
a boolean. Based on the scientific method: observe, annotate, hypothesize,
experiment, measure.
EDD is context as files. Every investigation lives as a small YAML document
in your repo, versioned alongside the code. The primary reader isn't a
dashboard — it's the next agent (or human) to pick up the work. They read
the story and know exactly where things stand without digging through hundreds
of lines of chat history or scrollback.
> Pairs with ghostbus.
> ghostbus is the live wire — a tmux-backed bus for real-time coordination
> between multiple local coding agents. EDD is the durable record — the
> file-based memory that outlives any single session. Bus for now, files for
> memory. Neither depends on the other; they just compose well.
## In production
edd runs a client data project at OMTM.ai: 99 stories and about 2,000 logged
runs between September and November 2026, covering ingestion from ten source
systems, a read-only access audit, dataset anonymization and a training proof
of concept. Numbers the project reports to the client are backed by executable
checks that recompute them from raw data.
## Why
Traditional tests say pass/fail. That's the right tool for deterministic code:
a function returns the wrong bucket → fix → test → done.
But when you're tuning a generator, a retrieval pipeline, or an agent, the
output is non-deterministic and quality is a gradient. "Did it pass?" is the
wrong question. The right questions are how good, why, and what changed since
last time? A green checkmark can't hold a hypothesis, a run history, or the
reason you tried the thing you tried.
EDD gives that state a home: a mutable story that names the problem, holds
the current theory, and accumulates an append-only list of runs. It's
deliberately low-ceremony — plain YAML, plain directories, greppable, no
service to stand up.
## Concepts
### Story
A mutable working document that names the problem, holds the current theory,
and lists runs. The story is the entry point to ongoing work.
Active stories live in .edd/active/ /story.yaml
Parked stories live in .edd/parked/ /story.yaml
Resolved stories live in .edd/archived/ /story.yaml
A story has:
name — human-readable title
status — one of active, resolved, rejected, superseded, parked
problem — what's wrong, in 1–3 sentences
theory — current hypothesis about why, and what fix to try
refs — loose association to branches, commits, docs
fixture — how to reproduce / test (a command, a file reference, or a
description)
runs — append-only list of results, newest or oldest first but
consistently one or the other
Common optional fields:
priority — p0 immediate, p1 what makes the product wrong or broken,
p2 real and worth doing with nothing visibly broken, p3 lowest.
p3 is not a parking space. Say parked once, with status, or the day
comes when a story is parked by one signal and open by the other
depends_on — story that should resolve before this one starts
blocked_by — the immediate blocker. A blocked story's status stays
active or parked; blocking is a fact about the work, not a phase of it
Listed badge (optional)
Copy this line into the README if you want the listing mark. Optional, and it does not affect being listed.
[![Listed on Anclum](https://anclum.com/badge/listed.svg)](https://anclum.com/en/s/jessejamesrich-edd/)
Source
github · https://github.com/jessejamesrich/edd
Browse by field
Open source
added
today

More entries

All 1,875 →

Filed under

Every tag opens the full list for that filter. Counts are the live catalogue figures.

Browse all fields →

← Back to index