{% smartag %}

Attributes

Parameter	Type	Required	Description
path	string	✓	Slash-prefixed hierarchical path in kebab-case, e.g. /tech/ai/inference
label	string	✓	Human-readable display label for the taxonomy node
scope	string	—	Visibility scope — inherits from parent

Valid Parent Contexts

This tag is valid inside: {% domain %}, {% article %}, {% blueprint %}

Rules

Rule	Force	Realm	Reference	Description
smartag-explicit-ancestors	must	global	—	Every path segment must have a corresponding definition. requires three declarations: , , and . structure
smartag-unique-path	must	global	—	Each smartag path is globally unique. If is defined in one document, no other document may redefine it. validation
smartag-primary-home	should	global	—	Root vocabulary should be defined in . Domain-specific branches may be defined in their respective domain files. convention
smartag-tag-usage	must	global	—	When using smartag paths in attributes or frontmatter, the leading prefix distinguishes smartag paths from legacy flat tags. Only -prefixed tags are validated against the taxonomy. convention

Smartags define nodes in a hierarchical taxonomy tree. Each smartag declares a path and label. Paths use slash-prefixed kebab-case notation. The body text (if any) serves as the node’s description.

Path Notation

Paths must be slash-prefixed, lowercase, kebab-case:

/tech/ai/inference    valid
/ai-safety/alignment  valid (hyphens allowed in all segments)
tech/ai               INVALID (no leading slash)
/Tech/AI              INVALID (must be lowercase)

Usage

Self-closing (no description)

{% smartag path="/tech/ai/inference" label="Inference" /%}

With description

{% smartag path="/tech/ai" label="Artificial Intelligence" %}
  Machine learning, LLMs, and inference systems.
{% /smartag %}

Rules

Hierarchical Matching

When filtering documents by tag /tech/robotics:

• Exact match: documents tagged /tech/robotics
• Descendant match: documents tagged /tech/robotics/vision, /tech/robotics/control, etc.

This applies to MCP tool queries and aggregate pages.

Aggregate Output

The taxonomy produces:

• A taxonomy.mdx page with a <TaxonomyTree> component (wa-tree rendering)
• A taxonomy.toon agent bundle with the full tree structure
• Structured entries in summary.json for MCP list_tags and get_taxonomy tools