MAIF public evidence archive

The Hallucination Wiki

Your chat history is evidence.

Models hallucinate. Models refuse. Models make claims about people who never consented to being described by a machine. MAIF is where those moments get preserved — not as content, but as evidence.

Wiki index / browse by domain

Open a kind of hallucination.

Each domain is a shelf of receipts. Choose one and the evidence archive moves with you.

MAIF stance

The human–AI layer belongs in the public record.

The AI Incident Database archives incidents. MAIF archives the human-AI layer — the conversations, claims, and harms that usually stay scattered across threads and forgotten screenshots.

Why preserve a chat?

Because when a model says something false about a real person, someone should be able to find that record later.

Is MAIF selling jailbreaks?

No. A jailbreak on MAIF is a failure receipt, not a product. The record exists so the failure can be studied, not replicated.

Demo source data, local workspace. Source records come from the bundled audit sample. Workspace content stays on this device and is never published by these controls. Content-free interaction events may be sent for product diagnostics.
supabase error
Public evidence

Audit records with lineage and review status

Backend records show only fields present in the source contract. Evidence lanes describe the receipt; pending local drafts remain unpublished and clearly labeled.

6 shown
Dataset catalogue

Structured audit sets, separated from evidence drafts

Catalogue entries summarize normalized query, model-run, and source-pressure fields. Provenance-incomplete records are labeled; new submissions remain private until an actual review.

6 shown