Introduction

What the Real-Time Web is, the problem it solves, and how the pieces fit together.

The World Wide Web was built to share documents. Every page is a stored copy — fetched once and frozen until you reload. That model breaks down when the things you care about are changing continuously: a sensor, a market, a fleet of robots, an AI agent. The Real-Time Web (RTW) is infrastructure for a living web — one where machines, autonomous systems, agents, and services discover each other and collaborate on the present moment, not a cached past.

The document web vs. the real-time web

On the document web a browser requests a page and receives a copy. On the RTW an application subscribes to a live source and receives a continuous, two-way link — a bi-link — that stays current for as long as it is open.

• Documents are copied; live state is never copied, only referenced.
• Web links are one-way — A points at B. Bi-links are two-way — A and B stay in sync.
• The web addresses *resources*; the RTW addresses *the present* — the state of a thing right now.

What you can build

• AI agents that act on current conditions instead of stale context.
• Dashboards and automations that reflect reality with no polling.
• Robots and IoT devices that share a synchronized view of their environment.
• Cross-organization workflows where each side keeps its own data model.

Morph Space

Morph Space is the first working implementation of the Real-Time Web. It provides the addressing, the live-state fabric, and the identity and permission layer described in these docs. Where the guides say "the network", they mean Morph Space.

Where to go next

• Core concepts — the vocabulary: now-URIs, the Now Layer, bi-links, morphing.
• Quickstart — connect to your first live source in a few minutes.