FAQ

Questions serious builders ask before they commit.

The product is intentionally strict about what counts as progress and what counts as a launch. These are the rules users need before they trust the system.

What counts as shipped?

A working product with a live URL, a real codebase, and a clear summary of what functions now. Another person should be able to open it and verify that the core promise is real.

What does not count?

Placeholder pages, 404s, empty repos, tutorial clones, or products that describe what will be built later instead of showing what works today.

Can I use any stack?

Yes. The product is not opinionated about your tools. It is opinionated about the outcome: the deadline, the scope, and the proof standard.

How long should a commitment be?

V1 is built around 2, 3, 4, or 5 week windows. The short duration is deliberate. It keeps urgency high and makes it harder to hide behind a giant roadmap.

How should I choose the stake?

Choose an amount that will genuinely bother you if you fail. If it feels symbolic, it probably will not change your behavior when the work becomes inconvenient.

Is payment fully enforced already?

Not yet. The commitment workflow is live, and the payment enforcement layer is still being rolled out. The product now states that openly instead of overselling readiness.

Still considering it?

Read the rules, then put an actual launch on the calendar.