What is a Collection?

A Collection is a saved scope that uses Labels as filter rules.

Learn more about Labels here: Labels overview

Instead of selecting files manually for each task, you define rules once and reuse them across chats and workflows.

Think of a Collection as a fence around the part of your project data you want Chief to use.

Why use Collections?

• Stay focused - reduce noise by working on only relevant files.

• Move faster - reuse saved scopes instead of rebuilding context.

• Collaborate clearly - teammates can use the same scoped dataset.

• Support repeat workflows - reporting, reviews, and planning become consistent.

How Collections work

Collections use two operator layers:

• Group operator: combines labels inside one filter group.
  

  

• Global operator: combines multiple filter groups.
  

  

Group operators

• include all of - a file must match all labels in that group

• include any of - a file can match any label in that group

• exclude if all - a file is excluded only if all labels in that group match

• exclude if any of - a file is excluded if any label in that group matches

Global operator between groups

• Include all of - a file must satisfy every group

• Include any of - a file can satisfy any one group

Chief evaluates the filter logic against labeled files in the current project and returns the matching file set for that Collection.

Examples of Collections:

Below is a simple Collection, Just Planets with just one label applied. Using @mentions you can scope this Collection to your chats, although in this case, you could just as easily at-mention the label in your chat and the effect would be the same.

click images to enlarge

This Collection, Planet or Star Data is more sophisticated. It is defined to match all content that contains either the Planet Data label or the Star Data label.

In this case, Using @mentions, if you were to at-mention the Planet or Star Data Collection in your chat, you would be chatting with all the matching files below.

This Collection, Planet and Star Data is set to only match content that contains both labels. In this case, only one asset has both Planet Data and Star Data applied. (If any future assets were labeled with both labels, they would automatically show up in this Collection).

This Collection, Planet or Star data (but not images) contains multiple filters. You can set multiple filters by clicking the filter icon again after you create your first filter. This Collection is set to exclude any assets labeled as images — even if they have one of the other labels applied.

Other things to keep in mind:

• Scope control: Mention a Collections by name to limit prompts to be run on just the data in that Collecction.

• Knowledge Pane: Switch between Assets and Concepts within a Collection for different perspectives on your data

• Projects: Collections defined in one project won’t exist in other projects. Collections, Labels and Assets are all defined per-project.

• Coming soon: Automations that rerun prompts when the data in Collections changes, keeping insights continuously up to date.

Collections and the bigger picture

Collections connect with other Chief features:

• They fence your data based on usage of one or more Labels, which help you organize your Assets

• You can see either a list of the assets in a Collection, or a graph of all the the Concepts in that Collection, letting you see extracted insights only from the scope that matters.

• They integrate into Prompts and Actions, giving you precise control over the data Chief draws from.

By combining these elements, Collections become more than organizational tools — they shape the way you interact with your knowledge.