entity-management

To track provenance for versioned knowledge dossiers, organize information about individual entities into per-entity markdown files under docs/entities. This enforces provenance rules, requires citations for every claim, and supports cross-referencing to maintain auditable edits over time.

The best way to build an auditable knowledge base is to create individual entity files that log sourced facts with strict citation requirements. This approach compiles source-backed summaries and tracks changes over time for profiles like people, companies, genes, and drugs.

You cross-reference related entities by applying provenance rules across individual entity files within your docs directory. This builds a coherent memory structure that links connected profiles, enabling consistent knowledge tracking and auditable cross-references.

Yes, you can use markdown files to compile source-backed summaries by creating a new entity file under docs/entities/<category>/<entity-name>.md. This structure immediately begins logging sourced facts and enforces citation-backed claims for profiling.

Yes, provenance rules require citations for every claim added to an entity file. This strict requirement ensures all edits remain auditable, supporting accurate tracking of changes over time and reliable knowledge compilation.

You need versioned dossiers with full provenance when tracking changes over time for individual entities like contracts or genes. This approach ensures auditable edits, citation-backed claims, and coherent cross-referencing between related profiles.