Private Domain Tag System Architecting and Governance

Building a Governable Foundation for Private Domain Tags

Many teams fall into the trap of 'ad-hoc tagging' when building private domain tags: ambiguous definitions mean three teams have three different meanings for 'highly active'; tag explosion results in hundreds of tags with low utilization; siloed data sources where the same field in WeCom, Mini Programs, and order systems don't align; and lack of ownership leading to tag decay over time. This isn't a problem solved by simply 'creating a few tag cards'—it requires an enterprise-grade, structured governance framework.

This skill provides a methodology for building a private domain tag system from scratch, designed for direct implementation. It is not a code tool or API caller, but a 'system design and governance consulting' process executed by an agent. Its core deliverable is a set of 'four-piece set' blueprints, aiming to instill manageability into tag assets from their inception.

Core Capabilities & Deliverables

The skill's core lies in structurally producing the following four key documents, which together form a complete lifecycle management plan for tag assets:

1. Tag Hierarchical Framework: Defines the classification (factual/behavioral/predictive) and hierarchy of tags to avoid flat, disorganized structures.
2. Tag Dictionary & Metadata: A detailed definition including 18 standard fields (e.g., owner, quality_score_formula, online_offline_thresholds)—the 'registry' for all tags.
3. Governance SOP: Clearly defines mechanisms for owner assignment, rules for definition arbitration, and online/offline procedures based on quality scores, standardizing governance actions.
4. Implementation Roadmap: Outlines the six-stage process from inventory, design, tagging, validation, to launch and iteration.

Workflow & Applicable Boundaries

Upon invocation, provide your business model (e.g., e-commerce repurchases), private domain platform (e.g., WeCom), and available data sources (e.g., orders,埋点). The skill will architect the system based on this input. Even with insufficient information, it will generate an initial blueprint labeled [Assumption - Needs Verification] for you to populate with real data.

Key Considerations:
* This is a pure methodology delivery: It does not directly operate on databases or user IDs. The output is editable documentation (Markdown and an optional Excel template).
* Focus on system governance: If you only need to tag a specific user segment for profiling, you should use its companion skill, Private Domain User Profiling & Tag System.
* Requires manual review and implementation: The suggested parameters in the blueprint (e.g., quality score thresholds, initial tag definitions) must be adjusted and implemented in conjunction with your actual business data, tools, and organizational structure. It solves the framework for 'how to build' and 'how to manage', but realization requires integration with specific systems.