Binary File Ingestion Suppression (Hex Buffer Guard)

Overview

When an autonomous agent mistakenly attempts to read a compiled binary (.exe, .wasm, .pyc), SQLite database (.sqlite), media asset (.png, .mp4), or compressed archive (.tar.gz, .zip) into text context, standard tokenizers attempt to decode raw byte streams into UTF-8 characters.

This causes immediate Context Poisoning: thousands of unrenderable replacement tokens (\ufffd, \x00, \x0f) flood the context window, blowing past token limits, degrading model attention weights, and causing model hallucination loops.

The Binary Suppression Protocol enforces pre-flight binary detection via magic bytes and null-byte heuristics, replacing raw file contents with clean structural metadata.

Raw Binary Ingestion vs. Metadata Guard