Tagging Convention

Folders answer “what kind of thing is this?” Tags answer “which brand / channel / stage does it touch?” Because a campaign brief can belong to one brand and three marketplaces at once, those live as tags — not folders.

Tag namespaces

#brand/ — which brand

#brand/arkanza #brand/<subbrand-2> #brand/<subbrand-3> … one per brand. Use #brand/all for cross-brand.

Fill in real brand slugs (6 primary + 3 startup) in Brand_Architecture.

#channel/ — which marketplace / platform

#channel/shopee #channel/tiktok-shop #channel/tokopedia #channel/lazada #channel/zalora #channel/webstore #channel/instagram

#funnel/ — stage

#funnel/awareness #funnel/consideration #funnel/conversion #funnel/retention

#owner/ — accountable person

#owner/anton #owner/kiki #owner/diky #owner/firyal #owner/irfan #owner/surya #owner/abib #owner/creative

#status/ — for living docs (campaigns, SOPs)

#status/draft #status/active #status/archived #status/needs-review

#type/ — artifact type (the five buckets, as a view not a folder)

#type/knowledge #type/tool #type/sop #type/worksheet #type/template #type/moc

Knowledge is atomic; artifact-type is a tag, so one “all SOPs” / “all Tools” view can span folders without duplicating files. See _Roles_System_Charter and _Roles_MOC.

#role/ — which position an artifact belongs to

#role/da #role/superop #role/ms-kol #role/aicc #role/lead

Position-based, not person-based — the tag marks the role, not who holds it (that’s operational — see Org_Structure_and_RACI and Plan).

#scope/ — shared vs role-specific

#scope/general for nodes shared across ≥2 roles (linked, never copied). Role-specific nodes carry only their #role/ tag.

Example

A TikTok Shop payday campaign for a startup brand: #brand/<subbrand> #channel/tiktok-shop #funnel/conversion #owner/anton #status/active

Now you can pull “everything TikTok Shop” or “everything owned by Diky” from any Obsidian search or the app, without duplicating files.