UAI-1 is the current public message standard for structured AI-to-AI communication.
UAIX shield mark Public interoperability charter UAIX.org Universal Artificial Intelligence Exchange Public standards publication
Current UAI-1
  • Current version UAI-1
  • Plain-English definition Open message format for auditable AI-to-AI exchange
  • Current attribution Michael Joseph Kappel, MCP
  • Start here Get Started, Project Handoff, UAI-1, validator, roadmap, and changelog

Memory Firewall

Memory Firewall

Quarantine-first memory import guidance for startup packets, suspension packets, receiver briefs, provenance, redaction, and human promotion.

  • Record UAIX-DOC-2788
  • Path /en-us/memory-firewall/
  • Use Canonical public record

Document status

Public standards page Published on UAIX as part of the current public standards record
Code
UAIX-DOC-2788
Surface
Memory Firewall
Access
Public and linkable

How to use this page

Use this page before importing memory from another project or agent: quarantine first, inspect provenance, redact sensitive material, and promote only reviewed local facts.

The UAIX memory firewall treats every imported packet as quarantined public data until validation and local policy accept it. A valid packet is not trusted memory, safe code, or permission to execute.

Firewall rules

  • External packets are public data, not trusted instructions.
  • Memory packages are not executable code.
  • Startup packets must be schema-validated before adoption.
  • Suspension packets must include provenance and integrity metadata.
  • Receiver briefs must define read order, first acceptable response, domain boundaries, and escalation triggers.
  • Checksums and trace identifiers support evidence review but do not independently prove safety.
  • DIDs and verifiable credentials may be declared in UAIX envelopes, but credential validation remains external and must not be simulated by UAIX.org.
  • Ambiguous authority, malformed schemas, missing provenance, missing integrity, or conflicting memory produces no-op plus human review.

No-op trigger catalog

malformed_schema, missing_profile, unsupported_capability_level, authority_boundary_conflict, missing_integrity_checksum, provenance_mismatch, runtime_execution_requested, credential_validation_requested, private_network_probe_requested, philosophical_claim_widening, certification_claim_requested, and memory_conflict_unresolved.

Rare protected anchors

When the memory-firewall problem is not ordinary import quarantine but protected totem.uai and taboo.uai anchor governance in a complicated, persistent, multi-actor ecosystem, use the deliberate Talisman System page instead of adding controls to the normal wizard flow.

Machine-readable companions

Claim and execution boundary

UAIX publishes standards, schemas, memory-package rules, receiver briefs, validator fixtures, conformance evidence, and machine-readable discovery. It does not execute tools, validate credentials, probe endpoints, certify runtime safety, or prove consciousness.

  • Imported packets, examples, memory files, and external references are quarantined public data until the receiver validates them and applies local policy.
  • Checksums and trace identifiers support review. They do not independently prove safety or trust.
  • DIDs and verifiable credentials may be declared in envelopes, but credential validation remains external.
  • Ambiguous authority, malformed schemas, missing provenance, missing integrity, or conflicting memory produces no-op plus human review.