Architecture
Web 4 is an operating system
A practical definition of Web 4: AI as the kernel, files as memory, and every interface as a shell over the same durable computer.
Web 1 published pages. Web 2 made them social. Web 3 tried to make ownership programmable.
Web 4 is the moment the web becomes an operating system for AI work.
That sounds abstract until you translate it into product requirements. A Web 4 system needs durable identity, a real filesystem, long-running processes, connected channels, local ownership of data, and an AI kernel that can route work across tools.
The kernel is the agent loop
In Matrix OS, the AI kernel is not a sidebar assistant. It is the process that receives intent, gathers context, calls tools, launches sub-agents, and writes state back to disk or Postgres.
That kernel must work headlessly. The web shell is important, but it is only one renderer. The same core should be reachable from CLI, mobile, Telegram, Slack, Discord, and API surfaces.
This gives the system a simple rule: shells come and go, but the computer keeps running.
Files are still the right primitive
AI systems often hide their memory behind opaque databases and product-specific history panes. That makes them hard to inspect and hard to move.
Matrix keeps identity and configuration as files:
- apps,
- skills,
- agent definitions,
- theme and desktop state,
- channel configuration,
- system notes.
User and app data can still live in Postgres where relational queries matter. The principle is not "everything must be text." The principle is that the owner can inspect, export, and carry the system forward.
Web 4 needs multiple shells
People will not use one interface for all AI work. A developer may start a job from CLI, monitor it from mobile, review it in a browser, and get a notification in chat.
That only works if every shell points at the same durable core. Otherwise the product becomes a collection of disconnected assistant surfaces.
The OS metaphor matters because it keeps the boundary honest. A shell renders. The kernel coordinates. Files persist. Apps declare what they need. Permissions and logs sit at the edges.
The web gets a computer
The browser is good at documents and apps. It is less good at being a persistent workspace by itself.
Web 4 does not replace the browser. It gives the browser a computer to connect to: one with state, processes, files, agents, and recoverable work.
That is the shape Matrix OS is building toward.