Tags

Tags link a campaign's parts across primitives. Tag the sequence, its lead table, the workflow feeding it, and its learnings wiki page with the same label, and one read returns the whole footprint.

Tags are normalized (lowercase, trimmed, deduplicated, up to 50 per item) and have no registry — a tag exists exactly as long as something carries it. Chip colors derive from the label, so the same tag looks the same everywhere.

Browse

oxygen tags list           # every tag with per-primitive counts, most-used first
oxygen tags get q3-outbound  # everything carrying the tag, deep-linked

The web view lives at /tags; each tag page groups its items by kind. On /sequencer, clicking a tag chip filters the list, and /tags/<tag> deep-links into a pre-filtered sequencer view.

Write

Tags are written on each primitive's own surface:

oxygen sequences create ... --tags q3-outbound,saas-founders
oxygen sequences update <sequence> --tags q3-outbound   # replaces the set; "" clears
oxygen sequences list --tag q3-outbound
oxygen tables tag <table> --tags q3-outbound
oxygen workflows tag <workflow> --tags q3-outbound      # org metadata; no new revision
oxygen knowledge page upsert <slug> --tags q3-outbound ...

Recipes carry tags from their catalog definitions.

One special case: an archived sequence still accepts a tags-only update. Finished campaigns are exactly the learnings corpus tags exist to link — tag them freely.

Semantics worth knowing

• Updating tags replaces the whole set (there is no add/remove delta).
• Archived tables, wiki pages, and recipes drop out of the tag index; archived sequences stay in.
• Tags carry no approvals and spend no credits — they are workspace metadata.