See what data is covered and what is missing
Internal product research scaffold for “See what data is covered and what is missing”. 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
- What does 'coverage' measure: connected sources, collected records, buyer questions, or something else?
- What is the denominator, and who decides which sources or records are in scope?
- How does the product distinguish no data, unsupported data, a failed collection, and an unreviewed result?
- Can a team see which request or decision a data gap affects?
- What does the product explicitly not cover?
Product and code information needed
- Coverage calculation and mapping logic, including the numerator, denominator, scope, and update rules.
- Status enums and UI copy for absent, unsupported, failed, stale, and out-of-scope data.
- The data model connecting sources and records to requests, questions, or other product concepts.
- Examples and tests showing that gaps are not presented as positive or complete evidence.