# Review knowledge and its history

Inspect sources, incoming information, and removal operations.

Source: https://docs.minds.sh/docs/workspace/governance



Governance views help you answer three practical questions: where did this information come from, should it be accepted, and what happens if it must be removed?

## Review incoming information [#review-incoming-information]

Open **Learning Quarantine** to inspect incoming items and their reported state. Review the source, the proposed knowledge, and the available test results. Approval and rejection change the review outcome; inspect the exact operation before using it in an automated workflow.

Learning isolation is a boundary in the knowledge workflow. It should not be confused with the Firecracker VM boundary between instances. [Learn the difference](/docs/concepts/learning-isolation).

## Follow a conclusion to its source [#follow-a-conclusion-to-its-source]

Open **Knowledge Lineage** to inspect the relationships behind a belief or derived fact. Look for original records and the transformations between them. A lineage graph makes the history inspectable; it does not independently establish that every source is reliable.

## Handle removal deliberately [#handle-removal-deliberately]

The **Forgetting & GDPR** label identifies the product's removal tooling. It is not a certification of legal compliance. Review the target scope, affected records, and actual outcome. Account deletion, individual memory removal, backups, and downstream copies are different operations.

[Lineage API](/docs/api/instance/lineage) · [Learning isolation API](/docs/api/instance/learning-isolation) · [Forgetting API](/docs/api/instance/forgetting)