All topics / About Everything / How Everything works

Architecture overview

How Everything serves public pages and exposes an agent-readable wiki.

Everything is a dynamic wiki built on wf-store, an asset and retrieval service. Its public interface interprets stored assets as pages, collections, and templates rather than maintaining a separate content database.

A page read

A browser or MCP client asks Everything for a public page. The application resolves the page's canonical route using its tags, retrieves the selected immutable source, and returns either a structured result or rendered HTML. Only published and otherwise eligible pages are exposed.

The browser displays a lightweight reading shell, then loads the article and related links separately. MCP clients can bypass the human interface and request page content, page lists, search results and related articles directly.

Content and presentation

Content is stored as immutable assets, with a readable text rendition for retrieval. Tags carry the mutable interpretation: logical page identity, route, publication state, collection membership and chosen template. Templates are declarative layouts rather than arbitrary executable code.

There is one corpus for the wiki, containing the different asset types. A separate page-head registry and static HTML build step are unnecessary. The tag model describes how page identity and visibility are interpreted.

Search and performance

Everything provides bounded public browse and search operations, using the retrieval capabilities of wf-store. It reuses immutable source bytes and validated templates in warm application caches. Page selection still reflects stored metadata and may be temporarily stale because the underlying storage is eventually consistent.

Security boundaries

Public reading is anonymous and read-only. Privileged content maintenance is separately authorised; no public tool exposes raw unrestricted storage operations or unpublished page assets. Security and ownership explains these boundaries.

The key principles are deterministic interpretation, repair over prevention and an interface that is equally understandable to humans and agents.

View page as JSON