Know what evidence needs attention

Internal product research scaffold for “Know what evidence needs attention”. 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

  • Which conditions trigger an attention state: missing, stale, failed, changed, or awaiting review?
  • Can a team assign an owner and see the next available action?
  • Are notifications sent, or is attention shown only inside the product?
  • Can a user dismiss or defer an item, and how does it return if the condition persists?
  • How does the interface distinguish a real issue from data the product does not collect?

Product and code information needed

  • Attention-state rules, status transitions, owner fields, and action definitions.
  • Notification channels, schedules, preferences, and suppression rules, if implemented.
  • UI states and copy for each condition, including the distinction between unknown and failed.
  • Tests for assignment, dismissal, recurrence, and resolution.