MESA Core · v0.9.3

Evidence & provenance

v0.9.3 source: docs/concepts-and-ingestion.md

This guide has equivalent English and Turkish versions. The source sections behind this page are at the bottom.

What a result carries#

A canonical assertion links subject, predicate, entity/literal object and source evidence to document, revision, chunk, mutation and pipeline identities. Bounded graph proof also preserves supporting assertion IDs, entities, predicates and directions. A path must stay attached to its own supporting sources.

Three hashes have different meanings#

A declared whole-revision content hash, frozen chunk manifest hash and per-chunk content hash identify different things. Direct chunk insertion does not establish the whole-revision hash. Typed legal identity checks structural linkage and bounded aliases; source interpretation remains the producer responsibility.

Pack complete proof within a budget#

ContextBuilder counts formatted model-visible evidence, not the entire HTTP response. Complete graph proof must fit atomically; if canonical BPE cannot load, the conservative UTF-8 byte upper bound may pack less evidence. Empty retrieval means no eligible evidence was returned, not proof a proposition is false.

New chunks can return retrieval_provenance.legal_items as {version, items} for citation, decision_ref, date, amount, duration and outcome. start/end positions refer to the original source chunk even if the hit quotes a shorter fact. These annotations are separate from SPO assertions and do not add fusion score. Disabling legal rules hides stored overlays in returned copies; it does not erase snapshots. Document purge erases their source quotes.