Brief Evaluation Harness: Grading AI Outputs with Code

An empty placeholder file becomes a working evaluation harness that grades every AI-generated brief against real company data, catching a database-outage bug on its first run.

1:55 video2 min readWatch on YouTube

Reading AI-generated briefs by hand only catches errors the reader happens to notice, and only in the one brief they're looking at. Muskan from Humanitarians AI ran into this directly: the file meant to check her briefs was an empty placeholder, so the only way to catch a wrong statement was to read it line by line, which is exactly how she found a factual error earlier in the week. This week she filled that placeholder in, and code now grades every brief before anyone reads it.

Comparing briefs against real data, not vibes

The idea behind the harness is simple to state and hard to skip once you've seen it work: every brief gets compared against the actual data collected for that company, not against a reader's general sense of whether it sounds plausible. Six checks run against that data. They confirm required sections are present, flag generic filler, and require empty sections to say "unknown" rather than bluff with confident-sounding text. Dates and dollar amounts have to trace back to a real signal in the source data, and the sharpest check verifies that the financial score in the brief exactly matches a rule-based calculator, so the AI can't quietly substitute its own number.

Hard failures versus warnings

Not every mismatch means the same thing, so the harness separates checks into two tiers. Hard failures mark a real defect, meaning the brief is simply wrong and needs to be fixed. Warnings are meant for a human glance rather than an automatic rejection, because some mismatches are legitimate: the AI might correctly total a number that doesn't appear word-for-word in any single headline in the source data. That's arithmetic, not a lie, so it gets flagged for review instead of failed outright.

What the first run caught

The harness proved its worth immediately. On its very first run, it flagged a case where the competitor database was unreachable, and the brief still wrote confident, detailed text about competitors that had no basis in real data. A human reader might easily read past that kind of confident prose without questioning it. The harness didn't, because it wasn't evaluating tone or fluency, it was checking every claim against the source.

Key takeaways

  • An evaluation harness compares AI-generated output against real source data automatically, rather than relying on a human skim.
  • Six checks cover section presence, filler detection, "unknown" labeling for missing data, factual tracing, and financial score verification.
  • Hard failures mean the brief is wrong; warnings flag things worth a human glance, like arithmetic that doesn't map to a single headline.
  • The harness caught a real bug on its first run: confident text about competitors generated when the underlying database was unreachable.
  • A single automated check that runs on every output beats a human carefully reading one output once.

Try it yourself

Take one thing your own AI writes and put a check on it in code: a number, a date, or a score that must trace to real data, and fail the output when it can't. This is the kind of hands-on work coming out of the Humanitarians AI Fellows program.

Chapters

  1. 0:00The Problem: Reading AI Briefs by Hand
  2. 0:35The Six Automated Checks: Section Presence to Financial Math
  3. 1:10Hard Failures (Real Lies) vs. Warnings (Arithmetic Checks)
  4. 1:40First Run Success: Catching the Confident Competitor Bug
Full transcript(auto-generated, with timestamps)

The Problem: Reading AI Briefs by Hand

[0:00]Hey, I'm Muskin. The file that was supposed to check my briefs was an empty placeholder. This week I filled it. Now code grades every brief before anyone reads it, and it caught a real bug on the first run. The idea is simple. Every brief gets compared against the actual data we collected for that company. Not vibes, not a human skim, code. Before this, the only way to catch a wrong statement was to read it by hand. That's exactly how I found a factual error earlier today. Six checks run against that data. Required sections present. No

The Six Automated Checks: Section Presence to Financial Math

[0:36]Generic filler. Empty sections must say unknown instead of bluffing. Dates and dollar amounts have to trace to a real signal. And the sharp one, the financial score must exactly match our rule-based calculator, so the AI can't quietly swap in its own number. The checks come at two levels. Hard failures are real defects. The brief is wrong. Warnings are for a human glance, because sometimes the AI correctly adds up a total that doesn't appear word for word in any single headline. That's arithmetic, not a lie, so it's flagged,

Hard Failures (Real Lies) vs. Warnings (Arithmetic Checks)

[1:10]Not failed. And it worked immediately. On the very first run it flagged this. When the competitor database is unreachable, the brief still writes confident text about competitors out of nothing. A human might read right past that. The harness didn't. The lesson, same as always, don't trust the output, check it against the source in code. A test that runs on every brief beats a human reading one brief once. Your turn. Take one thing your AI writes and put a check on it in code. Pick one claim that

First Run Success: Catching the Confident Competitor Bug

[1:42]Must trace to real data, a number, a date, a score, and fail the output when it can't. One automated check beats a hundred careful reads. Caught by code. More next week. Humanitarian's AI.

More from Mycroft Financial AI

Humanitarians AI Lyrical Literacy Project