> ## Documentation Index
> Fetch the complete documentation index at: https://docs.zwiron.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Know overview

> Catalog, lineage, glossary terms, policies, tags, and governance programs that make moved data understandable and stewarded.

Know in Zwiron is where moved data becomes inventory and shared meaning. After Jobs land data, **Catalog** holds the assets, **Lineage** shows how they flow, and **Governance** surfaces under Know steward terms, policies, tags, classification jobs, subject areas, enforcements, and programs.

<Note>
  Know is not Trust and not Match. Use [Trust](/trust/overview) for quality detect, gates, and incidents. Use [Match](/match/overview) for entity resolution. Use Know to inventory assets and define the vocabulary and rules that attach to them.
</Note>

The following articles cover Know end to end:

* [Catalog](/platform/catalog) — browse and tag profiled assets
* [Lineage](/know/lineage) — upstream and downstream graph
* [Terms](/know/terms) — business glossary
* [Policies](/know/policies) — access, masking, retention, and business rules
* [Tags](/know/tags) — tag classifications (taxonomy)
* [Classification](/know/classification) — jobs that propose and apply tags
* [Subject areas](/know/subject-areas) — business domains for assets
* [Enforcements](/know/enforcements) — bind policies to scopes
* [Initiatives and goals](/know/programs) — strategy programs and measurable targets

***

## Where Know sits

| Area | Role relative to Know |
| - | - |
| **Connections / Jobs (Move)** | Profiling and sync populate Catalog assets |
| **Catalog** | Searchable inventory; place to **apply** tags |
| **Lineage** | Edges from Jobs and Match write-back when assets are linked |
| **Governance** | Define terms, policies, taxonomy, domains, enforcements, programs |
| **Trust** | Quality and certification signals update Catalog assets |
| **Match** | Optional Catalog asset link enables lineage and Trust follow-up after write-back |

Typical sequence:

1. Connect and **profile** so schemas and tables appear in Catalog.
2. Open **Know → Catalog** (and **Know → Lineage** when you need impact).
3. Define shared meaning under **Know → Terms** and **Know → Policies**.
4. Build the tag taxonomy (**Tag classifications**), then apply tags on Catalog assets.
5. Use **Know → More** for subject areas, enforcements, classification jobs, initiatives, and goals.

***

## Navigation

| Task | In the app |
| - | - |
| Browse assets | **Know → Catalog** |
| Trace flow | **Know → Lineage** |
| Glossary | **Know → Terms** |
| Policies | **Know → Policies** |
| Hub for Tags and other modules | **Know → More → All governance** (page title **Governance**) |
| Subject areas, enforcements, classification, initiatives, goals | **Know → More** → choose the child |

Sidebar under **Know**: **Catalog**, **Lineage**, **Terms**, **Policies**, **More**.

**Tags** is not a top-level sidebar item. Open it from **Know → More → All governance → Tags**, or use the command palette (**Governance → Tags**).

Breadcrumbs on governance pages use the label **Governance** and link to `/governance`.

***

## Related articles

* [Catalog](/platform/catalog)
* [Lineage](/know/lineage)
* [Terms](/know/terms)
* [Policies](/know/policies)
* [Tags](/know/tags)
* [Trust overview](/trust/overview)
* [Match overview](/match/overview)


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.