t4-p2-07draft2–4h

In-flow feedback capture

requires: t4-p2-06

Spec

A lightweight in-flow way to collect feedback - a reaction on the digest, or a weekly two-question check-in - rather than a separate survey people forget to fill in.

Why this matters

Feedback mechanisms that require leaving the flow measure conscientiousness, not satisfaction. In-flow capture is the difference between data and a response rate problem.

Verify

No result yet. Run `learn verify t4-p2-07` locally, or push to trigger CI.

contractcontract: t4_p2_07_feedback

unrun

evidenceevidence: screenshot

unrun

Rubric

# t4-p2-07 — In-flow feedback capture

**Task:** A lightweight in-flow way to collect feedback - a reaction on the digest, or a
weekly two-question check-in - rather than a separate survey people forget to fill out.

**Strong:** Feedback capture happens inside the existing flow users already touch (a
reaction on a message they already see, or a check-in delivered where they already work),
with real captured responses from actual usage, not a hypothetical mechanism.

**Passing but weak:** The mechanism is built and technically in-flow, but hasn't actually
captured any real responses yet, or requires a genuinely separate action (a link to click,
a form to open) that undermines the "in-flow" requirement.

**Fails:** Feedback is collected via a separate survey/form disconnected from the product's
actual usage flow - the exact pattern this task explicitly asks you to avoid.