← Back to Docs

Getting Started

Core Principles

These are not suggestions. They are non-negotiable design principles that every architectural decision must satisfy. Each one reverses an assumption of the old paradigm — and each one has consequences that ripple through the entire system.

01

A person is not a user. It is an information system.

Old Assumption

A person is a consumer of applications built by others. They authenticate, access, and leave. Their data stays behind.

New Principle

Every person has a selfspace — a persistent information system with their own identity, data, and subscriptions. They are not a guest. They are a peer.

Why It Matters

This reversal is the foundation of everything. If you are a user, you are subordinate to the system. If you are an actor, the system serves you.

02

Software is not a discrete product.

Old Assumption

Software is designed, built, tested, packaged, shipped, and installed. It comes in versions. It rots between releases.

New Principle

Software is a living configuration of reactive streams. No builds. No releases. No version numbers. It evolves continuously.

Why It Matters

The snapshot fallacy is the original sin of software engineering. Stop taking snapshots. Software that is never built can never rot.

03

Content is never duplicated.

Old Assumption

Content is copied everywhere — downloaded, attached, backed up, synced. Every copy creates divergence, version conflicts, and stale data.

New Principle

Content is referenced through subscriptions. There is one canonical version. Everyone who subscribes sees the same thing.

Why It Matters

The copy created the conditions for fragmentation. The reference eliminates those conditions. Provenance becomes structural, not bolted on.

04

Everything is an actor.

Old Assumption

Humans, AI agents, organizations, and devices have different architectures. Integration requires translating between incompatible models.

New Principle

Humans, AI agents, organizations, and devices all use the same architecture. Same identity. Same subscriptions. Same protocol.

Why It Matters

Uniformity is the source of integration power. When every participant speaks the same language, connection is not a project — it's a subscription.

05

Identity is cryptographic.

Old Assumption

Identity is an account — a record in a platform's database, tied to an email and password. The platform owns it.

New Principle

Identity is a keypair. You control it. No provider can revoke it. Authentication is continuous and silent.

Why It Matters

Without cryptographic identity, you cannot own your data, your subscriptions, or your place in the system. Identity is not something you have. It is something you are.

06

The computing grid is abstract.

Old Assumption

Computing power is a product you buy in a metal box. Your device is the center of your computing life.

New Principle

Computing power is a service you access through the grid. Your device is a surface. Your computing lives on the substrate.

Why It Matters

The metal box is an accident of history. Computing should be like electricity — always available where you need it, from any surface.