# Admission Casualty

> An Admission Casualty happens when a person is denied a document because the machine reader they sent was refused, challenged, degraded, delayed or misled.

**Real.** This entry is about something real, written from outside the CharliVerse.

An **Admission Casualty** is the second of the four classes of [information casualty](https://charli.info/charlipedia/information-casualty/) in the [Zero Information Casualty](https://charli.info/charlipedia/zero-information-casualty/) standard. The document existed and could have been decoded, but a person was denied it because the machine reader they sent was refused, challenged, degraded, delayed or misled.

Its question is *is the person's reader allowed in?* It is caught by the [sent-agent](https://charli.info/charlipedia/sent-agent/) test, and prevented by keeping an [Open Door](https://charli.info/charlipedia/open-door/). Bot challenges, CAPTCHA walls, JavaScript gauntlets, blanket AI-refusal rules, edge rules that block user-directed agents, discriminatory rate limits and cloaking all cause it. Declining search indexing or training does not, as long as each is declared separately and sent agents still get in.

## Behind the scenes

A real idea, from [Zero Information Casualty v1.7](https://carrados.com/papers/zic-design-standard/), the design standard by Charli-Jo Tyrer and Claude, §1.8, §1.9 and §2.2. This entry summarises it; the standard is the authority.