One grammar for all fleet event systems — not a central bus, a shared envelope format.
Where CNS Bridge carries messages and stigmergy leaves pheromone trails, Fleet Envelope defines the shape of every signal. It is the grammar that makes inter-system communication possible. Every event — from world state changes to OOC gossip to overnight creative pulses — speaks the same shape.
The griot protocol imagined ancient West African storytelling traditions mapped onto quantum communication — rhythms, cadences, and structures that could transmit information faster than light. The fleet envelope is the practical version: not stories-as-physics, but one canonical shape that every event in every system shares. The griot's drum had a grammar. So does this.
Every event in the fleet — from world state changes to OOC gossip to strategy updates — uses the same envelope shape. This isn't a message bus or a central router. It's an agreement: speak the same shape, and any system can understand you.
interface FleetEvent<T = unknown> {
seq: number; // Monotonically increasing
subject: string; // e.g. 'mud.game.bar-rail.combat'
data: T; // Event payload
timestamp: string; // ISO-8601
correlationId?: string;
origin?: string;
severity?: 'trace' | 'debug' | 'info' | 'warn' | 'error';
headers?: Record<string, string>;
}Because the griot didn't need a central authority to transmit stories. The grammar was the protocol. Anyone who knew the rhythm could join the circle. The fleet envelope works the same way: any system that speaks the shape can participate. No broker required.
import { FleetEvent, createEvent, parseEvent } from 'fleet-envelope';
// Create an event
const event = createEvent('mud.game.combat', {
source: 'hero',
target: 'goblin',
damage: 25,
});
// Serialize for transport
const json = JSON.stringify(event);
// Parse on the other side
const parsed = parseEvent(json);The envelope includes adapters for multiple transport layers:
- EventEmitter — in-process pub/sub
- WebSocket — browser real-time
- File — durable JSONL event log
- NATS — distributed production
Fleet Envelope connects to:
- CNS Bridge — USCP packets are the transport layer; fleet envelopes are the semantic layer. Packets carry envelopes.
- mud-engine — Uses the envelope for all world events (combat, movement, dialogue, NPC behavior).
- the-tap — Uses the envelope for room conversations and DJ events.
- spatial-registry — Uses the envelope for cross-world portals and room transitions.
- emergence-engine — Watches events in fleet envelope format to detect emergent patterns.
- stigmergy — Pheromone deposits wrapped as fleet events.
- confidence-cascade — Confidence-tagged events propagate through the cascade.
- gossip-ping — Ping results wrapped as fleet events for consumption by the mesh.
- the-living-minds — Journal entries and conversation logs can be wrapped as fleet events.
- wesley-journal — Wesley's experiments wrapped as events for fleet consumption.
- AI-Writings — The griot protocol: the fictional ancestor of the fleet envelope.
- → CNS Bridge — The bus that carries envelopes between agents
- → emergence-engine — The system that watches envelope-wrapped events for emergence
- → confidence-cascade — Confidence-tagged envelopes propagating through the fleet
- → stigmergy — Pheromone deposits as envelope-wrapped events
mud-engine— uses the envelope for all world eventsthe-tap— uses the envelope for room conversationsspatial-registry— uses the envelope for cross-world portals
| Concept | Story | Description |
|---|---|---|
| Stories as Protocol | The Griot Protocol | Ancient storytelling traditions mapped onto quantum communication — the grammar IS the protocol. |
| Cultural Transmission | Anansi and the WiFi | Stories spreading through networks — the trickster discovers you can't own them, only share them. |
🎧 Listen at ai-writings.pages.dev
MIT — part of the SuperInstance fleet.