The tag model

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.

For 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.

The 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.

Templates have their own kind, logical template ID, active marker and revision tags. All of these assets share one corpus; the tags distinguish their roles.

Malformed 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.

Tags do not create a transaction across assets. They make state observable and cheaply repairable without a second registry that must agree with them.