Context tags

Tags are reusable labels you attach to Context objects: Companies, products, use cases, personas, agents, documents, and their subobjects such as capabilities, product versions, and agent models. Tags describe; they never change who can see an object, how lists sort, or what an experiment runs. Every organization has its own tag library, and Fiveonefour maintains a shared library for shared Context. This page covers the web app; the same operations are available from ax context tags, the HTTP API, and the context_tags MCP tool.

Tag an object

Every taggable object shows a Tags section: on the detail page of a Company, product, use case, persona, agent, or document; inside the dialog that opens a subobject from a list; on the record panel and the editor of a subobject; and next to each model in an agent's catalog (as Eligibility tags).

1. Choose Add tag and start typing. The picker lists your organization's tags that match; arrow keys move, Enter picks, Escape closes.
2. Pick an existing tag, or choose Create “…” to create the tag you typed and attach it in one step. Names are unique per organization ignoring case and surrounding spaces, so creating a name that already exists reuses that tag and tells you so.
3. Remove a tag with the × on its chip.

Changes save immediately and the object's lists, cards, and tag pages refresh. Repeating an add or remove is harmless.

Filter a list by tag

Each taggable list has a Tags filter next to its other filters. Select one or more tags to show objects carrying any of them; the selection is kept in the page URL (?tags=<TAG_ID>,<TAG_ID>), so a filtered view can be shared or bookmarked. Rows and cards show their tags as chips.

Manage the tag library

Context → Tags lists your organization's tags in name order with how many objects carry each one. Search narrows by name.

Open a tag's name to see every object that carries it, across all object types. Filter by Object type; Companies, products, use cases, personas, agents, and documents link to their pages, and subobjects open in place. The Parent column shows the object a subobject belongs to, such as the product of an interface, so you can jump there directly.

Copying shared Context

When you copy a shared object into your organization, its published tags come along. Each shared tag is matched to a tag you already have (first the tag it was copied from, then one with the same name) or created in your library with the shared name and color. Tags you renamed or recolored keep your edits on later copies; tags you left unchanged follow shared renames. Proposals that were denied or withdrawn are never copied.

What tags do not do

• Tags do not cascade: a tag on a product is not a tag on its interfaces or versions, and tags have no parents or groups of their own.
• Tags do not sync in the background: a copied tag follows a shared rename only when you copy again, and only if you have not edited it.
• Tags are edited one object at a time; use the list filter to find objects, then tag each one.
• Tags in a document's frontmatter or YAML stay part of that document; they are not turned into Context tags.

Shared Context

Shared Context objects carry tags from the shared library, which Fiveonefour administers. You cannot attach a shared tag directly. Instead, the Tags section on a shared object shows:

• Published: the tags everyone sees today.
• Pending review: your own proposed additions and removals, if you have a proposal waiting, with a link to the request.

Choose Suggest tag changes (or Revise tag suggestion while a proposal is pending) to pick the tags the object should carry; the difference from the published set is what you propose, with a reason. Fiveonefour reviews the proposal and publishes the accepted changes. You can have one pending tag proposal per shared object; track them under My suggestions.