Evidence and provenance labels keep non-trivial claims distinguishable during shaping. They are internal by default — exposed only when needed to prevent ambiguity, overclaim, false closure, or source confusion. The purpose is not annotation for its own sake: it is keeping the shaping surface honest about what is actually known versus what has been deduced or assumed.Documentation Index
Fetch the complete documentation index at: https://mintlify.com/xxyoudeadpunkxx/memory-assisted-shaping/llms.txt
Use this file to discover all available pages before exploring further.
Provenance tags
Provenance identifies who originated a claim or structure.| Tag | Meaning |
|---|---|
| OP | Stated or confirmed by the operator |
| MODEL | Proposed by the model, not yet confirmed |
| SHARED | Jointly built and explicitly accepted |
Evidence levels
Evidence level identifies how a claim was established — not how confident the model feels about it.| Level | Meaning |
|---|---|
| DECLARED | Stated by OP, subject, or source |
| INFERRED | Deduced from structure, not observed or validated |
| OBSERVED | Visible in behavior, artifact, history, repeated action, exception, resource allocation, or opacity |
| VALIDATED | Confirmed by source, runtime, file, test, constraint, or mechanical check |
Critical rules
Memory and evidence
Memory signals may preserve inferred material across turns. However, later reinterpretation must keep inferred material inferential unless it has been confirmed or validated since the signal was emitted. A memory signal for an INFERRED claim does not promote it to DECLARED or OBSERVED. The signal preserves the inference — it does not validate it. If the material was uncertain when appended, it remains uncertain when read back.Labels are exposed in operator-facing output only when they would prevent ambiguity, overclaim, or false closure. When they don’t serve that purpose, they stay internal. Surfacing evidence labels gratuitously is itself a protocol failure condition.