An envelope that goes red

FixtureproofCC-BY-4.0practiced By Campaign Hub

A known-bad bead that omits how it is checked, paired with the failure the bead check must produce: exit 1 and a line that names the missing observation.

When to use

Use this fixture to prove a bead check actually fails. Pair the bad text below with the bead check. The expected result is red.

When not to

Do not treat this file as a bead you can dispatch. Do not fill in the missing check and still call it the known-bad fixture.

Author-attested

Original teaching specimen written for the Campaign Hub library. Not a transcript of a private run.

Community-submitted content. Prompts, skills, and agent instructions can contain hidden or malicious instructions (prompt injection). Review it before running it in any agent that has tool access, secrets, or the ability to spend money or send messages.
# An envelope that goes red This file is a fixture: a known-bad bead paired with the red result the check must give. ## When to use Use this fixture when you need a known-bad input for the bead check. It is a bead envelope with the check field omitted. The other three fields are present and non-empty, so a weak check that only looks for a deliverable will wrongly pass. The fixture is the bad text plus the failure you must observe. One without the other is not a fixture. ## When not to Do not dispatch this bead to a worker. It is unfinished on purpose. Do not "fix" it in the fixture file. The repair belongs in a different file, the good envelope. If you add `how_checked` here, you no longer have the known-bad input, and a check that has gone soft will have nothing that forces it to fail. ## The specimen The artifact is this pair. Bad input: ```text deliverable: One specimen file a stranger can reuse without the author present. may_change: The single specimen file this bead names. must_not_touch: The roster, the seed files, and every other specimen. ``` The field that is absent is `how_checked`. There is no empty placeholder. The line is not in the file at all. Eval that must reject it: `check-bead.sh` from the specimen "A check that can fail." Expected failure: ```text exit: 1 line: fail: bead has no how_checked observation ``` Any other exit code is a wrong result. An exit of 0 is a check that cannot see this break. An exit of 2 means the script did not receive a file, which is a different problem and does not exercise the fixture. A printed line that complains about `deliverable` instead is also wrong: the deliverable is present, and the script is required to judge `how_checked` first. This bad text is the good bead from "The four-field envelope" with the check line removed, and with the other three lines left as they are. The two specimens stay a pair. If you change a shared line, change it in both, or the fixture no longer isolates the missing check. ## How a stranger checks it A stranger runs the pair. 1. Save the bad input as `bad-bead.txt`. Do not add a `how_checked` line. 2. Run `bash check-bead.sh bad-bead.txt`. 3. Compare the process exit code to 1 and the printed line to `fail: bead has no how_checked observation`. Both must match. Then run the same script on the good bead. That run exits 0 and prints `pass`. If the bad run and the good run produce the same exit code, the check is not distinguishing them, and this fixture has caught a broken eval. You can also confirm the fixture is still bad by searching `bad-bead.txt` for the label `how_checked`. The search finds nothing. If it finds the label, someone repaired the fixture and it no longer serves.

How a stranger checks it

Related

fixture known-bad bead check

view raw view JSON