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

# Manage Knowledge Sources

> Update, refresh, remove, and organize Knowledge sources while preserving ownership, permissions, and index health.

# Manage Knowledge sources

Knowledge needs maintenance after ingestion. Sources can become stale, move between projects, lose upstream access, or require re-indexing after a configuration change.

## Review source metadata

A useful source record should identify:

* source type
* owner/context
* added time
* processing/index status
* last refresh or revision when available
* chunk/document counts
* size/storage metadata
* failure state when present

## Refresh a source

Refresh when the underlying material changed and Starfire supports source synchronization or re-ingestion.

For static uploads, refreshing can mean replacing the source with an updated version and rebuilding its index.

For repositories or connected sources, refresh can mean indexing a newer revision.

## Re-index

Re-indexing is appropriate when extraction succeeded but the retrieval index must be rebuilt—for example after embedding/index configuration changes or when an index becomes stale.

## Remove a source

Before removing a source, determine whether projects, agents, or workflows depend on it. Removing it from Knowledge can change future answers without changing historical conversations that already used the material.

## Ownership and permissions

Changing a source's project or organization context can change who can retrieve it. Treat ownership changes as permission changes, not filing-system cleanup.

## Duplicate sources

Avoid keeping multiple nearly identical copies unless there is a real versioning reason. Duplicate chunks can distort retrieval ranking and make citations less clear.

<Tip>
  Use source names that identify the actual reference and version, such as `Starfire Billing Architecture — Sep 2026`, rather than `document-final-v2`.
</Tip>
