docs(confidence-engine): preserve evidence provenance

This commit is contained in:
2026-08-29 18:24:32 +01:00
parent 88d9768276
commit 50a66749ae
2 changed files with 53 additions and 0 deletions
+15
View File
@@ -515,6 +515,21 @@ Three tiers, applied top to bottom:
- Omit items too verbose to scan; do not synthesise rewritten claims.
- Never invent facts absent from the graph.
### Provenance and attribution
Preserve authorship and provenance in every user-facing presentation.
When displaying a user's previous input, keep it visibly distinct from system-generated interpretation. If the original user wording is available, present it as the user's response rather than rewriting it into system prose. Derived Findings, summaries, uncertainties, assumptions, or follow-up questions must not be styled or worded in a way that implies the user said them.
The distinction should be:
```text
User response → user-authored (verbatim)
What we learned → Engine-derived
```
Exact labels are subject to UX refinement; the durable rule is separating provenance, not prescribing specific copy.
## Investigation Narrative
The reasoning graph is the machine representation of the investigation.