Version 01, the latest authored version

Version 01 · the body as written

## The Broadcast Architecture of Guava Nexus

Guava Nexus can be understood as a system for preserving thought before distributing it.

At its core are not feeds, messages, or generated outputs, but **versioned records**: discrete states of human context that can be revisited, compared, cited, and traced through time. A Seed is not merely text. It is a record of what someone was willing to preserve at a particular moment, together with the history of how that record changed.

This creates a problem of transmission.

Once context has been preserved, how does it leave the repository without losing its identity?

A human reading a page and an AI retrieving structured data are fundamentally different consumers. They may receive the same intellectual record, but they do not consume it through the same medium. Guava therefore needs a layer beneath those interfaces that establishes what, exactly, is being transmitted.

That is the role imagined for **VCP*--version context protocol.

```text
                GUAVA NEXUS
                     │
             Versioned records
                     │
                    VCP
         context identity + integrity
                     │
          ┌──────────┴──────────┐
          ↓                     ↓
       SeedCast                 MCP
   human broadcast        machine broadcast
          ↓                     ↓
       humans                  AIs
```

VCP is not primarily concerned with whether the receiver is human or machine. Its concern is more fundamental: **the identity and integrity of context itself**.

Which Seed is this?

Which Version?

Who recorded it?

What body belonged to that Version?

What relationship did it declare to another record?

What evidence accompanied it?

What has changed since?

What can be verified, and what remains merely asserted?

Only after these questions are answerable does broadcasting become meaningful.

### One record, different receivers

For humans, Guava can broadcast through forms adapted to human cognition.

A Seed page can be read.

A lineage can be visually explored.

A Version history can be inspected.

And SeedCast can eventually transform those records into conversation, narration, dialogue, and sound.

SeedCast therefore becomes a **human broadcast layer**: a way of turning an intellectual graph into something people can listen to, encounter, and interpret.

For machines, the requirements are different.

An AI should not have to visually inspect a webpage, guess where the authoritative text begins, or infer which historical Version the user meant. It should be able to request structured records directly.

That is where MCP belongs.

MCP becomes a **machine broadcast layer**: a standardized interface through which AI systems can search, retrieve, and traverse Guava's recorded context.

The AI may then reason over those records, but the reasoning remains downstream.

Guava's responsibility is not to tell the machine what to conclude. Its responsibility is to ensure that the machine receives the right intellectual object.

### VCP is therefore deeper than MCP

MCP answers questions such as:

- How can an AI retrieve a Seed?
- How can it search recorded bodies?
- How can it request a particular Version?
- How can it traverse a recorded relationship?

VCP would answer a different class of questions:

- What makes this context object *this* context object?
- What makes Version 4 distinguishable from Version 3?
- What parts of the record are committed and what parts are metadata?
- How can another system refer back to precisely the same state?
- How can the receiver verify that the context has not silently become something else?

This makes the distinction useful:

**MCP concerns access.  
VCP concerns identity.**

Or more precisely:

**MCP tells machines how to receive context.  
VCP tells everyone what context was actually received.**

That means MCP could someday be replaced by another machine-interface protocol without destroying the intellectual record.

SeedCast could evolve from audio streams into entirely different forms of human consumption.

But the underlying Version should remain the same.

That is why VCP, if Guava develops it, belongs below the broadcast interfaces.

### The signal should survive the medium

This is analogous to older communications systems.

A radio program is not identical to the electromagnetic wave carrying it.

A written idea is not identical to the paper carrying it.

A web document is not identical to HTTP.

And a Guava Seed should not become identical to MCP.

The transport can change while the record persists.

Guava therefore becomes less like a single application and more like a system with a persistent intellectual substrate:

```text
Human context
      ↓
recording
      ↓
Seed
      ↓
Version
      ↓
context identity
      ↓
VCP
      ↓
distribution
 ┌────┴────┐
 ↓         ↓
human     machine
media     interfaces
 ↓         ↓
SeedCast   MCP
 ↓         ↓
people     AI
```

This separation could become strategically important.

If intellectual artifacts are going to move among humans, models, agents, applications, and future systems that do not yet exist, their identity cannot depend entirely on the interface currently transporting them.

The record must survive its receiver.

### From publishing to broadcasting context

Traditional publishing distributes finished works.

Social networks distribute messages.

AI systems generate responses.

Guava could occupy a different layer: **it preserves evolving context and makes that context broadcastable without collapsing its history.**

A human might listen to a SeedCast conversation derived from a person's intellectual graph.

An AI might retrieve the same underlying Seed through MCP.

A researcher might cite an exact Version through its public URL.

A future application might consume the record through an API that does not yet exist.

Different interfaces.

Different receivers.

Same recorded context.

And this may ultimately be the architectural principle underneath Guava Nexus:

> **Record thought once, preserve its identity through time, and allow it to travel through whatever medium its receiver understands.**

In that model, VCP protects the signal, SeedCast broadcasts it to humans, and MCP broadcasts it to machines.

keccak256 of this body is what the commitment on chain records · the title, the version label, the author's note and the source are outside it