t4-p1-03authored2–4h

Fake-door test

requires: t4-p1-02

Before writing product code, publish a minimal landing page or a single message describing StandupBot's value proposition, and get at least 5 people to react, sign up, or say they would use it. A real signal, not a guess.

The cheapest possible falsification. If five people will not react to a message, the problem you are about to spend a week solving is not one they feel - and you have learned that for the price of a message.

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

evidenceevidence: screenshot, third_party_link
unrun
reporepo: commit_precedes
unrun
# t4-p1-03 — Fake-door test **Task:** Before writing product code, publish a minimal landing page or a single message describing StandupBot's value proposition, and get at least 5 people to react, sign up, or say they would use it. A real signal, not a guess. **Strong:** Evidence of a real artifact (screenshot of the page/message) published to a real audience, with 5+ genuine reactions/signups/responses from distinct people, captured as evidence - not just a claim that this happened. **Passing but weak:** The artifact was published and got some signal, but fewer than 5 responses, or the audience was not realistically able to say no (e.g. only close friends asked directly, in person, with social pressure to be nice). **Fails:** No fake-door test evidence at all, or code was written before this validation step - which is the one thing this task exists to prevent.