{"path":"/guide/how-it-works","content":{"title":"How Everything works","summary":"A small interpreter over wf-store, with explicit ownership and repairable content state.","breadcrumbs":"[All topics](/guide) / [About Everything](/topics/about-everything)","body":"Everything is an application layer over ordinary wf-store APIs. It adds wiki interpretation: logical pages, routes, publication, templates, safe public discovery and owner tools. The storage service does not need to become a wiki database.\n\n[Architecture overview](/guide/how-it-works/architecture) follows a request through the edge, application and storage. [The tag model](/guide/how-it-works/tag-model) explains where identity and state live. [Repair over prevention](/guide/how-it-works/repair-philosophy) describes the tradeoff behind ordinary tag corrections.\n\nThe [wf-store section](/guide/how-it-works/wf-store) introduces immutable assets, renditions, readiness and independent retrieval families. [Security and ownership](/guide/how-it-works/security) explains why anonymous reading does not imply anonymous editing or raw-storage access.\n\nThe central constraint is simple: one corpus contains all wiki asset types. There is no parallel content registry, per-type database or static HTML publishing system to keep synchronized.\n\n## In this section\n\n- [Architecture overview](/guide/how-it-works/architecture) — Follow public requests and owner writes through the current system.\n- [The tag model](/guide/how-it-works/tag-model) — Tags define wiki meaning; content JSON carries the writing.\n- [Repair over prevention](/guide/how-it-works/repair-philosophy) — Prefer observable state and ordinary correction over elaborate consistency machinery.\n- [wf-store](/guide/how-it-works/wf-store) — The asset and retrieval service underneath Everything.\n- [Security and ownership](/guide/how-it-works/security) — Anonymous readers get public wiki operations; only the configured owner gets writes.\n\n## The responsive reading path\n\nThe application returns a [navigation shell and skeleton](/guide/reading/navigation-and-loading), loads the article separately, then loads related results near the viewport. Its [warm caches](/guide/how-it-works/caching) reuse immutable page bytes, template selections/definitions and SDK setup. Page selection remains live; template staleness is deliberately tolerated.\n\n- [Caching and freshness](/guide/how-it-works/caching) — Understand one-call warm fetches, source-byte expiry and instance-lifetime templates.","navigation":"[About Everything](/topics/about-everything) · [Architecture overview](/guide/how-it-works/architecture)","related":[{"title":"Architecture overview","url":"/guide/how-it-works/architecture"},{"title":"How pages become websites","url":"/guide/templates/runtime-rendering"}]}}