What we allow, what we don't, and what happens when something crosses the line.

You can post freely on products you've verified ownership of — through GitHub repo admin, DNS TXT, or package provenance. There are no anti-promo restrictions, no 60-day cooldowns, no karma gates. Verification is the gate.

In exchange: every post you make is a structured ask with required fields. Vague promotional posts get blocked at compose time. The composer pushes back on hype words. The mechanic is structural, not editorial.

1. Review-to-Post. To publish a new ask, you must have completed at least one substantive review since your last post. Substantive means the recipient marked it Helpful or Completed. Drive-by "great work!" reviews are logged but don't credit your next post.
2. Daily-Review → Auto-Distribution. Each day you complete a substantive review, your own currently-active asks get a visibility boost. Contribution buys distribution. Quietly, without virtue signaling.

First-ask exception: your very first ask after verification doesn't require a prior review. Every subsequent ask does.

Same-pair limit.Each pair of makers can credit at most one review per 30 days. If maker A has already used maker B as a credit source in the past month, A's next Helpful from B still stands as honest feedback but won't unlock A's next post. Help someone new — broaden the graph. This prevents two accounts from reciprocally credit-laundering each other.

Daily credit cap.Each recipient can issue at most 2 credit-eligible Helpful or Completed verdicts in any rolling 24-hour window. Beyond that, the verdict still stands as honest feedback — the recipient's assessment isn't erased — but it can't unlock the reviewer's next post. This prevents one popular maker from rubber-stamping a friend ring in an hour.

Review immutability.Reviews cannot be deleted or edited within 30 days of submission. After 30 days, deletion is permitted (e.g. for an accidental PII paste) — but the Helpful/Completed verdict the review earned stays on record. This prevents the attack of "submit review, consume the credit, delete the review to re-use the slot." If you submitted something you genuinely need scrubbed before the window closes, email hello@icantmarket.comand we'll handle it manually.

The classifier blocks these at the product-submission gate, before your page goes live:

• crypto Consumer cryptocurrency, token launches, ICOs
• nft NFT collections, marketplaces, mints
• defi DEXes, yield protocols, liquidity-mining apps
• web3-social Lens / Farcaster wrappers
• dao-tooling Governance + treasury management for token DAOs
• scam-adjacent Get-rich-quick, MLM, paid-traffic schemes, dropshipping playbooks
• malware Anything advertising bypass / scrape / spam at scale
• adult Adult content, gambling, weapons

Developer libraries that integrate with blockchains for non-token purposes are fine. The line is consumer-facing crypto/tokens — not the underlying tech.

• Fake testimonials, fabricated metrics, made-up customer logos
• Hype words detected by the composer (revolutionary, game-changing, 10x, transform, unleash, skyrocket, unlock, disrupt, synergy, leverage, etc.) — flagged at compose time with an override checkbox if you really mean them
• Posts that don't fill the structured ask fields honestly
• Copy-pasting the same review across multiple asks
• Reviewing your own ask, or asking a friend to vote-trade

We don't shadowban. We don't silently flag-kill. If we take action, you get told what and why.

• Strike 1. Email with the specific rule + the specific post. No standing change. You can edit, delete, or appeal.
• Strike 2. 7-day account suspension. Verified products stay visible; new posts blocked.
• Strike 3. Permanent account ban. Verified products archived. Public log entry.

If you claim ownership of a product whose name matches a famous library or service — react, next, lodash, typescript, stripe, supabase, etc. — your verification holds in human review even if the technical check passes. We'd rather make you wait 48 hours than let someone impersonate the upstream.

Every post and comment has a Report button. We aim for a 24-hour first response during the charter phase. The moderation log is public. We will tell you what was reported, what we found, and what we did.