> ## Documentation Index
> Fetch the complete documentation index at: https://docs.getvector.me/llms.txt
> Use this file to discover all available pages before exploring further.
# Features in your domain
> See every feature your market offers in one catalog, mark what you already have, and research or tidy up many features at once.
Everything Vector learns about your market ends up as features: capabilities that at least one of your [competitors](/competitors/add-competitors) offers, whether or not you have them yourself. They live in one catalog. The comparison, the [product map](/features/product-map) and delivery are all views of that same set — so this is the place to start when you want to know what your market expects from a product like yours.
Open it from **Features** → **Features in domain** in the left menu. The page is titled **Features in product domain**.
## See what your market offers
The catalog lists features grouped by cluster, with areas indented under their cluster as **↳** rows. For each feature you see:
| Column | What it tells you |
| ----------- | ---------------------------------------------------------------------------------------------------------------------------------------------------- |
| Feature | Its name, a one-line summary, and a badge such as **Table stakes**, **Differentiator**, **Emerging** or **Regulatory** once it's been classified |
| Us | Whether your product has it |
| Competitors | How many of your competitors have it, for example `4/11` |
| Known | How much you know about it: eight dots and a count such as `6/8`, one for every section of its [dossier](/features/feature-dossier) that has content |
A feature many competitors have and you don't is a gap worth a look. A feature with few **Known** dots isn't less important — it just hasn't been researched much yet.
Click a feature's name to open its dossier. Use the search box to find one by name.
## Mark what you already have
The **Us** column is your own status for each feature. Click it and pick a value:
| Value | Meaning |
| ---------------- | -------------------------------- |
| ✅ Has it | Your product has this feature |
| ⚠️ Partial | You have part of it |
| 🔜 On roadmap | You've planned it |
| ❌ No | You don't have it |
| — Not applicable | It doesn't apply to your product |
Set it once and it shows everywhere: in the comparison, on the product map and on the feature's own page. [Planning delivery](/delivery/plan-a-delivery-cycle) for a feature moves it to **On roadmap** for you.
The features you have, partly have or have planned also show on **My product**, under the **Features** step — your own product's feature list, drawn from the same statuses.
## Focus on what matters
The toolbar above the list narrows it down:
* **Competitors** — **Short list**, **Long list** or **All**. It decides which competitors count in the **Competitors** column. Short list, the default, keeps it to the competitors you're directly up against.
* **Only differences** — keeps only the features some competitors have and others don't. Features everyone has, or nobody has, drop out.
* **Status** / **Score** — show presence marks, or a 0–10 rating of how good each version is. In Score view, the **Us** column shows your rating instead of the status picker.
To see the same features laid out against each competitor, switch the view from **List** to **Coverage** — see [Compare competitors](/competitors/compare-competitors).
Opening the catalog from a cluster or an area on the product map filters it to that part of the map. **Show all features ✕** clears the filter.
## Add a feature by hand
Most features arrive through research: what's found lands as a [candidate](/features/candidates) first, and becomes a feature once you decide it should. When you already know a capability belongs in the catalog, add it yourself: click **New feature**, give it a name, optionally pick a cluster, and click **Create**. It gets its own dossier straight away.
## File unclassified features
Every feature belongs to a cluster on the product map. When some don't, a **Needs classification** banner at the top of the page says how many, and **See them ↓** jumps to their group at the bottom of the list. Select them and use **Move to cluster/area…** to file them all at once.
A feature with a cluster but no area is fine — it simply lives in the cluster directly.
## Research many features at once
Tick the checkboxes next to features — or **select all** on a group header — and an action bar appears at the top of the page. Pick the dossier sections to fill — **👥 Public Reviews**, **🔬 Deep how-it-works**, **📈 Trajectory**, **📊 Competitor coverage**, **🎨 UI references** or **🛡 Re-verify evidence** — and click **Next**.
A confirmation shows how many runs will start: one per feature per section. Each run is separate and uses your [AI key](/getting-started/connect-a-provider), so check the count before you click **Run**.
To find the features that still need research, use **Select by gap ▾**: it selects the visible features missing a given section, replacing whatever was selected before.
## Tidy up the catalog
Select features and use the same action bar:
* **Move to cluster/area…** — file them under a cluster, and optionally an area.
* **Archive** — take features you don't care about out of the list and the comparison. They keep their history; bring one back with **Unarchive** on its own page.
* **Merge…** — for a single feature: takes you to its [possible duplicates](/features/duplicates-and-merging), where you fold another entry into it.
## Where to go next
Where this catalog comes from.
Everything known about one feature.