Explain evidence scope and limits
Internal product research scaffold for “Explain evidence scope and limits”. Questions and product/code evidence needed before public copy can be written.
Working research scaffold. This page lists questions for Product and Engineering; it does not confirm that the feature is available. The current foundation marks detailed first-party collection, proof-pack generation, buyer inspection, and AI-assisted response preparation as planned. Verify each answer against the released Mockup product and its code before turning it into a public capability claim.
Questions to answer
- How does the product distinguish direct system data, policy documents, test results, and a person's statement?
- What scope, time, source, and collection state are shown beside each item?
- What do any completeness, freshness, or confidence indicators actually measure?
- How are unsupported, missing, stale, or conflicting records explained to a buyer?
- How does the product prevent evidence from being presented as a certification or guarantee?
Product and code information needed
- Evidence-type taxonomy, source and scope fields, timestamps, and status definitions.
- Any completeness or confidence formula, its inputs, limitations, and approved customer-facing explanation.
- Buyer and operator UI, export formats, and wording around limitations.
- Product/legal owner review and tests that keep scope and status visible.