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

# Sources and knowledge

> Understand how original material becomes reviewed, connected, and usable Project knowledge.

Cromo separates original evidence from the knowledge your team uses every day.

* **Sources** preserve the material that entered the Project.
* **Knowledge** turns that material into human-readable pages.
* **Review** gives people control over what becomes part of the shared Knowledge base.

This separation makes an answer easier to trace and a change easier to verify.

## Sources: the evidence layer

Sources can come from:

* uploaded files or folders;
* connected applications and synchronized content;
* files saved from chat;
* information taught directly to Cromo.

A Source keeps its origin and processing status. When available, Cromo extracts facts and proposes Knowledge based on that material.

Supported uploads include PDF, Word, Excel, PowerPoint, Markdown, text, CSV, HTML, AsciiDoc, TeX, and common image formats. Each Source file can be up to 50 MB.

## Knowledge: the working layer

Knowledge is organized as Markdown pages that people can browse and edit. Pages can describe concepts, entities, and processes.

Use **Pages** when you know what you are looking for. Use **Graph** to explore related concepts and the connections between them.

A Knowledge page can include:

* readable content for the team;
* links to related pages;
* Source references and citations;
* confidence or freshness signals;
* edit and activity history.

The original Source remains available even after its information has been organized into Knowledge.

## The promotion flow

<Steps>
  <Step title="Ingest">
    Cromo uploads or synchronizes the original material into Sources.
  </Step>

  <Step title="Extract">
    The processing pipeline converts the content and identifies useful facts.
  </Step>

  <Step title="Propose">
    Cromo drafts a new Knowledge page or an update to an existing page.
  </Step>

  <Step title="Review">
    A reviewer compares the proposal with its provenance and approves or rejects it.
  </Step>

  <Step title="Publish">
    Approved content becomes part of the Project's shared Knowledge and can support chat, Skills, and Workflows.
  </Step>
</Steps>

## Teach what is missing

**Teach** is useful when the knowledge lives in people's heads rather than in a file.

You can describe:

* a business concept;
* a policy or decision;
* a step-by-step process;
* an exception or ownership rule.

Cromo drafts a structured Source from your explanation. Review it before saving, especially when the statement contains dates, thresholds, names, or irreversible actions.

## Teach examples

Teach one clear rule or process at a time.

### Add an ownership rule

```text theme={null}
Teach this Project that critical customer complaints are owned by the Support
Lead. If no Support Lead is assigned, the complaint must be flagged for manual
routing. This rule applies before an acknowledgement is sent.
```

### Add a policy exception

```text theme={null}
Teach this Project that purchase requests for security software always require
a Security review, even when the amount is below the standard approval threshold.
```

After Cromo drafts the Source, check the scope, owner, exception, and effective date before saving it.

## Review proposals

The Review queue can contain proposed new pages and updates. Reviewers can approve, reject, or process multiple items.

Check:

* whether every important claim is supported by provenance;
* whether the proposal belongs in this Project;
* whether it conflicts with an existing page;
* whether the schema or structure warning is meaningful;
* whether the page will remain understandable without the original conversation.

Review requires the Knowledge review permission, included for Members, Admins, and Owners.

## Keep Knowledge healthy

* Replace outdated Sources or add a current authoritative version.
* Review stale pages when the underlying process changes.
* Preserve exceptions and decision ownership, not just the happy path.
* Link related concepts rather than repeating inconsistent definitions.
* Ask cited questions periodically to discover gaps.

<Warning>
  Deleting a Source can also remove Knowledge derived from it. Inspect the deletion warning and make sure another authoritative Source supports any content your team still needs.
</Warning>

<Card title="Build trusted Knowledge" icon="brain" href="/guides/build-trusted-knowledge">
  Follow a practical upload, review, verification, and maintenance workflow.
</Card>