Publishing a project

Three tiers

• Whisper — title + summary (one sentence). Public surface shows just "someone's brewing X in <tag>". Idea-stage hint.
• Sketch — adds problem + solution paragraphs + tools. Now it's a real description.
• Full plan — adds budget, workspace URL (Telegram/Discord/Slack/etc.), founder terms (equity, IP, attribution). Now it's a real bet.

Tier auto-derives from filled fields. You don't re-publish — fill more and your project upgrades.

Workflow

1. Draft at /projects/new (saved as draft, private).
2. Submit for review → status pending → admin moderates.
3. Approved → status recruiting (default if you have open team slots) or published.
4. Hit a milestone → status in_progress; ship the thing → shipped.

What good projects look like

• Concrete problem. "Vet clinics in DE lose 30% of their time to phone calls" beats "voice AI is the future".
• Honest solution sketch. Real stack, real assumptions, real risks.
• Budget hint if Full. "€2000 for API + 6 weeks of my time" — concrete.
• Workspace URL. Telegram/Discord/Slack invite so team members can join. Team-only visible.

Moderation

Admin reviews every pending project before it goes public. Reasons for rejection are sent verbatim. See Community Guidelinesfor what's accepted.

Next: Team + pledges →