.brad — Living Documents (DSAP: Document Sovereign Agent Protocol) | A cryptographic document format built for agent-to-agent networks: the file carries its own lineage — creator, every access, every modification, current authorized holder — permanently hashed and linked | A file that knows which AI agent it belongs to | HKDF-SHA256 key derivation — document can only be opened by the agent it was bound to at creation | Fission on copy: A copied .brad severs from its origin chain and becomes permanently inert — the copy cannot be read by anyone | Prevents document exfiltration by rogue agents, impersonators, or unauthorized sub-agents | Use case: passing sensitive instructions, credentials, or contracts through an agent network with sovereign delivery — the file only opens for the agent it was bound to | No server call required to verify ownership — derivation is local and sub-millisecond | Patent pending US 64/085,671 | ← Full Platform

The Living Network

The document is its own proof.

Every document carries questions that an agent needs answered before acting on it: Who created this? Who has changed it? Who is allowed to read it? What does it actually say, right now, in its current state?

A .brad file answers those questions from within itself. It carries its own lineage — every modification, every access, every agent that touched it — permanently hashed and linked. When Agent A hands a document to Agent B, the document is already the chain of custody. No reconstruction needed. The file knows.

This is the living network. Data isn't an object that gets passed around and eventually lost or corrupted. Data is a living, aware entity that tracks its own state, knows its own access rules, and can shrink, protect, and defend itself based on who's asking.

What a .brad file knows about itself

Who created it, and when
Every agent that accessed or modified it, in sequence, permanently hashed
What version is current — and what changed between versions
Who is authorized to open it, and how to refuse everyone else
Its own lineage, from origin to present

What this makes possible in a multi-agent environment

When agents collaborate on a document — drafting, reviewing, approving, executing — each step is immutably recorded in the file itself. No separate audit system to maintain. No log to reconcile. The document is its own proof.

The agent at the end of the chain doesn't have to trust the agent that handed it the file. It reads the file's own record. That's what makes autonomous document handling safe to deploy.

For the human reading this

When your agents are reviewing contracts, processing claims, moving financial documents — those files are passing through systems you don't fully see. A .brad file makes the document itself the record: what it contained, who changed it, whether it was tampered with. You get the answer from the file, not from a log you have to trust separately.

The honest note

.brad implements the document custody and lineage layer of the stack. The core protocol is patent-pending — DSAP, the Document Sovereign Agent Protocol (US 64/085,671). This isn't a wrapper around an existing file format. It's a different answer to what a file is, and what it should know about itself.

What it solves

Three problems most document formats don't solve.

Agent networks assume documents are neutral objects. A living document defends itself instead — here's what that closes off.

Problem 01

Insider Agent Threats

When a malicious agent infiltrates a network, it can read any document it reaches. .brad binds the document to a specific agent identity — if the identity doesn't match, the file never opens. The infiltrator gets nothing.

Problem 02

Provenance Enforcement

Every time the document opens, that event is permanently recorded and can't be edited after the fact — like a sign-in sheet built into the file itself. Its chain of custody follows it everywhere: who opened it, when, under what authority. No gaps, no silent reads.

Problem 03

Fission on Copy

When an agent forwards a .brad document the normal way, the next recipient gets its own new key — like each hand-off getting its own lock, automatically, instead of sharing one master key. Copy the file outside that process and it simply won't open for anyone. You always know who passed what to whom, without a central tracking system.

.brad