Guardian Intake Gateway

Govern external content before it becomes model context.

SPECIFICATIONCognitive firewall / zero-trust intake

The Problem

AI systems accept raw external content—documents, emails, tool descriptions, API responses—directly into their reasoning context without verification. This creates a cognitive attack surface where hostile meaning can be injected through prompt injection, false authority, tool poisoning, context poisoning, hidden instructions, and memory contamination.

The Approach

Guardian establishes a model-facing trust boundary. Raw intake flows through a six-zone pipeline: Session Binding → Activation Binding → Quarantine → Traditional Security Analysis → AI-Native Content Analysis → Sanitization → Provenance Capture → Lifecycle Policy → ReceptorEvent → Guard Decision → Controlled Model Representation → Continuity Record → Audit/Retention/Purge. The ReceptorEvent is governed evidence, not truth, permission, or memory. Guardian modules include File, Mail, MCP, Extension, Enterprise, Local Receptors, Receptor API, Lifecycle Console, and Audit Console.

What Exists Today

✓Guardian Intake Gateway architecture specification
✓Local MVP direction defined
✓Receptor module taxonomy specified
✓Audit service prototype demonstrates source, hash, manifest, risk, and policy checks with receipt generation

//What It Does Not Prove

What this project does not prove.

✗Not independently certified
✗No production deployment demonstrated
✗Threat coverage incomplete
✗Benchmark validation incomplete
✗Local prototype only

Evidence

Six-zone intake pipeline architecture (Session Binding → Activation Binding → Quarantine → Traditional Security Analysis → AI-Native Content Analysis → Sanitization → Provenance Capture → Lifecycle Policy → ReceptorEvent → Guard Decision → Controlled Model Representation → Continuity Record → Audit/Retention/Purge)

guardian-intake

SPECIFICATION

Artifact: Guardian Intake Gateway Architecture

Version: v1.0

Environment: Design specification

Date: 2026-08

Result:

Complete architecture specification with 13 pipeline stages, 9 receptor module types, and 3 console interfaces defined.

//Verification Boundary

Specification only. No implementation exists. Local MVP direction defined but not built. Receptor module taxonomy specified but not implemented.

Guardian Audit Service EphUX / Guardian ExoMCP SymID SessionGlyph

Source Artifacts

📄Guardian Intake Gateway Architecture
📄Guardian Product Modules
📄Guardian Audit Service