{"path":"/guide/how-it-works/tag-model","content":{"title":"The tag model","summary":"Tags define wiki meaning; content JSON carries the writing.","breadcrumbs":"[Everything guide](/guide) / [How Everything works](/guide/how-it-works)","body":"Everything interprets ordinary wf-store tags. A page revision has tags for kind, logical identity, route, page type, template association and revision ordering. Draft and publication tags control public eligibility; `wf:deleted` means logical retirement.\n\nFor example, an article might carry `everything:page`, `everything:id:example`, `everything:slug:research:example`, `everything:type:article` and `everything:uses:article`, plus its revision and publication state.\n\nThe JSON source can contain `title`, `summary`, `body` and other display data. Canonical identity, slug, type, template ID, publication and revision fields are reserved at the top level because their authority belongs in tags.\n\nTemplates have their own kind, logical template ID, active marker and revision tags. All of these assets share one corpus; the tags distinguish their roles.\n\nMalformed combinations remain inspectable by the owner. Public interpretation rejects unsafe ambiguity rather than guessing. Multiple eligible published revisions or active templates use deterministic ordering by valid revision key, then asset ID.\n\nTags do not create a transaction across assets. They make state observable and cheaply repairable without a second registry that must agree with them.","navigation":"[Everything guide](/guide) · Section: [How Everything works](/guide/how-it-works) · Previous: [Architecture overview](/guide/how-it-works/architecture) · Next: [Repair over prevention](/guide/how-it-works/repair-philosophy)","related":[{"title":"Repair over prevention","url":"/guide/how-it-works/repair-philosophy"},{"title":"One corpus, many content types","url":"/guide/how-it-works/wf-store/corpora"}]}}