Skip to content
Back to Atlas

Tags & Relationships

Tag system, all 9 relationship types, tag themes, project clusters, and cross-object connections.

core objects

Tags

Tags are lightweight labels that can be attached to ideas, assets, decisions, and projects. They serve as a cross-cutting categorization layer, unlike projects (which are hierarchical), tags can connect objects across different projects and types.

Each tag has a name (unique per workspace), an optional category, and an optional color. Tags appear as filterable facets in the Vault, Decisions page, and Relationships page.

Examples of useful tags:

  • Topic tags: "pricing", "onboarding", "retention"

  • Temporal tags: "Q2-2026", "launch-week"

  • Source tags: "customer-feedback", "competitor-intel"

  • Status tags: "needs-research", "blocked"

Tag Fields




FieldTypeRequiredConstraint
----------------------------------
NameTextYesUnique per workspace
CategoryTextNoGrouping label (e.g. "PROJECT", "TOPIC")
ColorHex colorNoVisual color indicator

Tag Themes

The Relationships page automatically identifies tag themes, tags that appear on multiple items across different object types.

A tag becomes a theme when it has ≥ 2 total items (ideas + assets + decisions) attached. This suggests the tag represents a recurring pattern in your thinking.

Tags that span 2+ different projects are highlighted as potential cross-project connections, signals that two separate initiatives share common themes.

Relationships

Relationships are explicit, typed connections between any two objects in Foundry. You can link ideas to assets, assets to decisions, projects to projects, or any combination.

Each relationship has:

  • A source (the object you're linking from)

  • A target (the object you're linking to)

  • A type that describes the nature of the connection

  • An optional note for context

Relationship Types. Complete Reference










TypeDirectionDescriptionExample Use Case
-----------------------------------------------
SupportsSource supports targetFoundational dependency"This insight supports that strategic decision"
Derived FromSource came from targetOrigin tracking"This asset was derived from that idea"
Reusable ForSource can be reused for targetIP leverage"This prompt is reusable for that project"
AffectsSource affects targetImpact tracking"This decision affects that project's timeline"
Linked ToGeneral connectionLoose association"These two ideas are related"
Evolved IntoSource became targetEvolution tracking"This MVP concept evolved into that full product"
ContradictsTension between objectsConflict awareness"This new data contradicts that earlier assumption"
Inspired BySource was inspired by targetInspiration tracking"This feature idea was inspired by that competitor note"
ReplacesSource replaces targetSupersession"This new framework replaces the old one"

All types except LINKED_TO are directional (source → target). You can create relationships from the Relationships page or from individual object detail pages.

Tag Merging

If you have duplicate or similar tags (e.g. "pricing" and "Pricing" or "onboarding" and "user-onboarding"), you can merge them.

How merging works:
1. Go to Settings → Tags
2. Select the tag you want to remove (source)
3. Choose the tag you want to keep (target)
4. All associations from the source are moved to the target
5. The source tag is deleted

Merging is irreversible. The source tag cannot be recovered after merging.

FAQ

How many tags should I use?
Keep it manageable, 10-20 tags is typical. Too many tags dilute their usefulness. If you have 50+ tags, consider merging similar ones.

Can I tag a project?
Yes. Projects support tags through the TagOnProject junction table. Project tags appear on the Relationships page.

Are relationships bidirectional?
Only LINKED_TO is inherently bidirectional. Other types are directional. "A supports B" doesn't mean "B supports A." You can create reverse relationships if needed.

Can I bulk-tag ideas?
Not currently. Tags are applied individually when creating or editing an idea.