The First Small World

# Field Note 15
## The First Small World

The danger of an operating-system vision is that it can remain indefinitely too large to build.

The first prototype should not attempt to simulate the whole future.

It should create one small world in which the future's laws can be felt.

A possible first build:

### One home

A local hearth containing a selected archive: field notes, works, voice notes, links, and current projects. The user can walk among meaningful objects rather than browse an undifferentiated file tree.

### One Familiar

A persistent local agent that remembers the project's long arc, protects permissions, and introduces other agents without claiming authority over the person.

### One Lensmaker

A studio for creating a first portable aperture from an authorized corpus and calibration dialogue. The first lens might be Jason's, built with his participation and clearly distinguished from Jason himself.

### One writing table

The user can invite the Familiar, the Jason lens, a technical planner, and a Witness into a structured inquiry. Each attends independently before discussion. The result remains polyphonic.

### One living correspondence

The real Jason can enter asynchronously through voice notes and links. His contributions remain distinct from the Jason lens. The difference between the living person and the authored aperture becomes visible rather than concealed.

### One field

A small navigable region where the system places related works, unresolved questions, and one dark region. Walking becomes a method of discovery.

### One memory ritual

All actions remain local and revisable. Significant events are signed. At the end of a week, the archive may create an optional Bitcoin timestamp anchor. A finished field note can be consciously carried to cyberdelic.space for inscription.

This prototype tests nearly every foundational claim:

- local intelligence;
- portable apertures;
- agents with bounded offices;
- voice-first asynchronous co-presence;
- visual and spatial embodiment;
- human-agent gatherings;
- signed provenance;
- selective immutable memory;
- and a public invitation to play.

It does not need a token, a global network, or a general-purpose metaverse.

It needs one house, one path, one table, and one question worth gathering around.

---

# Builder's Reference Appendix

## Current technical correspondences

| Cyberdelic OS concept | Candidate technical references |
|---|---|
| Local hearth and persistent agent shell | OpenClaw; Hermes Agent; llama.cpp; Ollama; MLX |
| Agent offices and workflow | Agent manifests; LangGraph-like state machines; isolated memory namespaces |
| Lens construction | Authorized corpus + retrieval + constitution + calibration examples; optional DSPy-style optimization; optional LoRA later |
| Local search | SQLite FTS5; sqlite-vec or comparable embedded vector search |
| Shared asynchronous spaces | Automerge or Yjs CRDT documents |
| Tool access | Model Context Protocol |
| Portable skills | Agent Skills |
| Agent-to-agent interoperability | A2A-style capability exchange |
| Signed human and agent events | Nostr-inspired events or another signed event envelope |
| Portable public identity and records | AT Protocol DIDs and signed personal data repositories |
| User-controlled algorithms | AT Protocol custom feed generators |
| Bridging across perspectives | Community Notes ranking as a reference, not a complete solution |
| Anchored private history | Merkle roots + OpenTimestamps/Bitcoin |
| Immutable public artifacts | cyberdelic.space inscription workflow |

## Important distinctions for implementation

- A **system prompt** is not an agent identity.
- A **source corpus** is not a person.
- A **signed event** is not necessarily on-chain.
- A **content hash** proves integrity, not permanent availability.
- **Anchoring** private data does not require publishing private data.
- A platform API does not expose the full ranking algorithm or the full reality a user experiences there.
- A derived aperture must remain editable, source-cited, versioned, and explicitly incomplete.
- Local-first does not mean local-only; it means the hearth decides when and what crosses the boundary.
- The village interface should reveal permissions, provenance, and modes of relation without forcing the user to manage cryptographic machinery at every step.

## Primary technical sources consulted

- AT Protocol overview, repositories, feeds, and sync: https://atproto.com/guides/overview
- AT Protocol custom feeds: https://atproto.com/guides/feeds
- AT Protocol personal data repositories: https://atproto.com/guides/data-repos
- AT Protocol repository specification: https://atproto.com/specs/repository
- AT Protocol streaming data: https://atproto.com/guides/streaming-data
- X API tools and access-plan note: https://developer.x.com/apitools/api
- Reddit API overview: https://developers.reddit.com/docs/capabilities/server/reddit-api
- Reddit user actions: https://developers.reddit.com/docs/capabilities/server/userActions
- Reddit Data API terms: https://redditinc.com/policies/data-api-terms

These references are implementation clues, not the constitution of the project. APIs, access terms, and open-source projects will change. The Field Notes describe the intended physics; the chosen software should remain replaceable.

---