known-answer-test packs
a kat pack is synthetic, clean reference input plus a committed expected-output hash — a known answer. replay a pack and a reference engine either reproduces the committed hash or it does not. this is how a skeptic confirms fatcousin tools are deterministic and correct without trusting us — conceptually like nist cftt known-answer testing, but it runs entirely in your browser.
replay a pack
3 committed packs ship below. each input is processed locally; the recomputed sha-256 is matched against the committed expectedOutputSha256. nothing is uploaded.
loading…
loading…
loading…
download a pack's files (kat.json, MANIFEST.sha256, and the input files), then drop them here together. they are hashed locally — nothing is uploaded — and checked against the manifest. if the inputs and kat.json are present, the known answers are re-replayed too.
what a kat pack proves (and what it doesn't)
- determinism — the same input + params always yields the same output bytes, so the committed hash reproduces. a regression that changes output silently breaks the known answer.
- integrity — each pack ships a
MANIFEST.sha256sidecar over its files. recompute it (here, or withsha256sum -c MANIFEST.sha256) to confirm nothing was modified after publish. - synthetic only — every input is fabricated for testing. no real evidence, no personal data, nothing copyrighted. each pack states its synthetic origin.
- it does not prove a tool is fit for a particular legal matter, that upstream acquisition was sound, or that a court will admit anything — see scope and disclaimer.
pack format
each pack is a folder at /kat/<id>/ with a kat.json manifest, synthetic input files, and a MANIFEST.sha256 sidecar. the manifest lists cases, each binding an input + params to a committed known answer:
{
"schemaVersion": 1,
"id": "csv-auth-log",
"title": "...",
"description": "...",
"syntheticOrigin": "fabricated by fatcousin labs — no real evidence ...",
"cases": [
{
"id": "auth-log",
"inputRef": "auth-log.csv",
"params": { "format": "csv" },
"expectedOutputSha256": "<sha-256 of the canonical output>",
"expectedSummary": "6 rows, 5 columns ..."
}
]
}