Use deliberate edge cases to test difficult workflows.

The testing job

What an edge case gives you

Edge cases make a system's assumptions visible. Instead of asking whether a clean document works, you can inspect how the workflow responds when the input is incomplete, ambiguous, or internally difficult to interpret.

• Missing context or fields
• Conflicting details in one document
• Unexpected ordering or structure
• Mixed signals that force a decision

Human input

Each case needs a reason to exist.

Deniable packages include human input, review, and creative scenario design. That human layer gives a document a testing purpose instead of leaving you with random noise around an otherwise ordinary example.

Broader than parsers

Use the cases wherever difficult inputs matter.

The same document can help you inspect routing, classification, extraction, retrieval, validation, and product QA. The use case is the behavior you want to observe, not a single parser or model.

Repeatable workflow

Run the same question more than once.

Choose a relevant pack, inspect the case and its scenario context, run it through your system, and record what happened. A fixed document can then be used again when you change a prompt, parser, model, or workflow step.

Access

Choose a ZIP pack or API retrieval.

Fixed dataset packs are delivered as ZIP files. Prepaid API credits are a separate path for authenticated retrieval from the curated catalogue. Both are designed for repeatable internal testing.

Scope

Difficult does not mean guaranteed.

Designed cases can expose assumptions and failure modes, but no dataset can promise that it will find every possible defect. Deniable does not use production records for these examples.