Evidence & Provenance
Keep claims, decisions and actions traceable back to their sources.
Primitive already preserves provenance in memory and business-intelligence boundaries. The broader causal/evidence model aims to make every consequential transition explainable from source through execution to receipt.
Primitive should be able to answer: 'Where did this information come from?', 'Why did we decide this?', and 'What actually changed because of it?'
Provenance answers origin; evidence answers support; receipts answer what execution actually occurred. Keeping those distinct prevents a generated statement from becoming equivalent to a source and prevents an intended action from being confused with a completed effect.
Existing evidence boundaries
Managed memory preserves provenance during merge, and business-intelligence/opportunity analysis engines include explicit evidence/provenance boundaries.
Causal receipts
Harness records and Control transition receipts provide complementary mechanisms for reconstructing execution and authority transitions.
Epistemic labels
Primitive theory documents explicitly separate observed patterns, Primitive facts, working theory, hypotheses, metaphors and proposals. Docs carries that discipline into user-facing explanations through delivery status and source pointers.
Where this description comes from
These pointers are the authority behind the status and technical description. If implementation and documentation disagree, the canonical implementation or Control contract wins and this page should be corrected.