Space / Roadmap
Building FRQNCY Social
A 24-month plan to take FRQNCY from a centralized MVP to a protocol-native community network — on the destination axis of Farcaster and Nostr, but routed through AT Protocol because that's where the audience already is.
TL;DR
FRQNCY Social is a small, values-driven, crypto-adjacent community network. Today it is a centralized app on Supabase + Astro + Preact. In 24 months it is an AT Protocol-native app with a Farcaster side-channel for crypto surfaces and a Nostr read-bridge. The bet: lean chronological feed, follow-graph primary, transparent re-ranker, project-anchored conversation as the headline differentiator, monetized by freemium + tipping — no ads, ever. Cooperation, not competition — no public leaderboards.
Phase 1 — Centralized, Portable Bones
Months 0 – 6 · Where we are today
Keep the Supabase + Astro + Preact stack exactly as it is. Use this phase to nail product-market fit on a tight community before any protocol work lands in production. Shipping discipline beats architectural purity.
Protocol
- ✓Supabase source of truth
- ✓Auth, posts, follows, DMs, comments
- ○Lexicon spec repo
xyz.frqncy.* - ○Lazy
did:webper user - ○Nightly signed-JSON export
Ranking
- ✓Reverse-chrono feed
- ✓Profile feed filter
- ○Project-anchored rooms
- ○Points-only conviction v1
- ○Full ranking formula behind flag
Economics
- ✓Free core product
- ✗No ads — ever
- ○$5/mo Supporter tier
- ○Stripe Connect tipping
- ○Llama Guard 3 moderation pass
Phase 2 — Dual-Write Federation
Months 6 – 12 · Differentiation lock-in
Stand up a production PDS serving *.frqncy.social, dual-write every post / follow / like to the user's signed repo, consume the Bluesky firehose via Jetstream, and run a custom App View on Cloudflare Workers + D1. The reputation vector (Social, Conviction, Debate) replaces the scalar karma number on profiles.
Protocol
- Production PDS
- Jetstream firehose ingest
- Custom App View
- Cross-post to Bluesky
- Cross-post to Farcaster (Neynar)
- In-house Ozone labeler
Ranking
- Discover surface (interest-graph)
- Contribution signals on profile (posts, replies, helpful tags)
- Project-anchored rooms w/ shared context
- Weekly "projects to revisit" digest
- A/B test ranking weights transparently
Economics
- NFT Founding Member (500 seats)
- Tipping fee 0% → 3%
- Trust-level system (TL0–TL4)
- Community mods per channel
- Crypto-attorney review of v2 markets
Phase 3 — Protocol-Native
Months 12 – 24 · Platform-optional
Flip the source of truth: PDS records are canonical, Supabase demotes to index / cache. Users can bring their own DID, export their repo, move to another PDS host without losing followers. Publish the FRQNCY Lexicons so any ATProto client can consume xyz.frqncy.resonance. Ship a Farcaster Mini App for the 630-project rating surface. The network outlives the app.
Protocol
- PDS becomes canonical
- BYO-DID import
- Public Lexicon registry
- Farcaster Mini App
- Nostr read-bridge
Ranking
- FRQNCY ranker as Bluesky custom feed
- User-facing feed-tuning sliders
- Opt-in AI personal feeds
- Reputation as portable PDS record
Economics
- Staked markets — only if legal-cleared and community-aligned
- Private personal conviction journal (no public ranking)
- Per-channel mod rotation (6 mo)
- Public transparency report
Non-Negotiables
- · No ads, ever. Attention that heals, not attention that extracts.
- · Points-only conviction at launch. No real-money markets until an attorney signs off.
- · Portable by design. Every user can export their whole repo from day one.
- · Transparent ranking. The formula ships in docs and as a tuning UI.
- · Blameless post-mortems. Public write-ups when moderation fails.
How to Shape This Roadmap
This is a living document. The roadmap gets updated when the product learns something — not on a fixed cadence. If you want to influence what ships next, the highest-leverage things you can do are:
Post and react in the Feed
Every post, follow, and like is signal for what the network is for. Seed the ritual.
Explore the Space
Read the research, the principles, and the open questions driving FRQNCY Social.
Contribute on GitHub
The code is open. Issues, PRs, and Lexicon proposals welcome.
Send feedback
One email. What's missing, what's wrong, what you wish we'd build next.