feat: alternative social-first growth scenario

ideas/alternative-growth-social-first.org

@@ -0,0 +1,176 @@
+:PROPERTIES:
+:ID:       alternative-growth-social-first
+:CREATED:  [2026-05-23 Sat]
+:END:
+#+title: Alternative Growth — Social-First Scenario
+#+filetags: :passepartout:growth:strategy:alternative:
+
+The existing growth-strategy assumes institution-first growth: compliance → developer → consumer → regulatory. This page documents an alternative path: grow as a general-purpose social identity network, let institutions catch up later. The triad components (Logos, Stoa, Agora) are the same; the order of operations and the primary growth levers differ fundamentally.
+
+* Why This Path Exists
+
+The institution-first scenario (growth-strategy.org) takes the product's core technical capability — verification — and finds the customer with the clearest pain. That is the safe bet. But verification is not the product's /only/ interface to the world. The triad ships with:
+
+- Agora identities (a namespace, a reputation system, a registry)
+- PDS hosting (personal data stores, compute nodes, agent homes)
+- The compute marketplace (a two-sided network)
+- Verified messaging and data provenance (communication infrastructure)
+
+All of these are social primitives, not compliance primitives. They can be productized without ever mentioning verification, ACL2, or gate rules. The social network grows first; verification becomes a feature that the network offers natively.
+
+Historical precedent: Instagram was a check-in app with filters. The camera and social graph came first; the advertising platform came later. Twitter was SMS broadcast; the real-time news network was emergent. In each case the product that users wanted had a different shape than the product that ultimately captured value.
+
+* Phase 0: Identity as a Premium Good (0 → 10K users, 3-12 months)
+
+Customer: Early adopters who want /ownership/ of their online identity. Not privacy activists — people who have been burned by platform dependency (locked out of Twitter, demonetized on YouTube, deleted from Facebook). The audience is small but passionate: indie creators, crypto-natives who understand self-sovereignty, developers who run their own infrastructure.
+
+Growth lever: Scarcity + status. Agora usernames are a finite namespace. Short names, dictionary words, and brand-relevant handles are valuable. The primary growth mechanism is the same as early Twitter or early Discord: FOMO driven by name squatting, auctions, and visible scarcity.
+
+Tactics:
+
+1. Ship the Agora registry first — a web UI where anyone can claim a username. No verification, no Passepartout, no ACL2. Just "register your name, it's yours, nobody can take it." The name is an NFT-adjacent claim without the blockchain baggage: stored in the Agora's Merkle tree, provably yours.
+
+2. Auction premium names publicly. The first 100 short names (3-4 chars) go to auction. Winning bids are public. This creates a price signal and generates press.
+
+3. Offer a free subdomain tier (username.agora) with a basic profile page. The profile inherits the name's reputation. This is the social graph seed.
+
+4. Bootstrap the PDS as a paid upgrade (username + PDS hosting = $5-15/mo). The PDS stores your identity, your data agreements, your agent configuration. The value proposition is: /your data, your rules, no advertising/.
+
+5. Verification is a surprise feature, not a headline. After registering a name and setting up a PDS, users discover they can /sign/ messages, /prove/ authorship, and /verify/ data provenance. This is the moment the triad's deeper value becomes visible — but users joined for the name and stayed for the control.
+
+Revenue:
+| Stream | Year 1 target | Mature |
+|--------+--------------+--------|
+| Username registrations (free) | 0 | 0 |
+| Premium username auctions | $50K-500K | $2-5M/yr |
+| PDS hosting subscriptions | $50K-200K | $1-3M/yr |
+| Verified identity badges | $20-100K | $1-2M/yr |
+| Total | $120K-800K | $4-10M/yr |
+
+Key metric: Registered usernames. Paid PDS subscriptions.
+
+Failure mode: Namespace doesn't achieve scarcity. Nobody cares about owning their identity because the existing platforms work well enough. The audience for self-sovereign identity exists but is too small to bootstrap network effects. This phase fails if growth is linear because the product is a solution to a problem most people don't know they have.
+
+* Phase 1: Network Effects — The Social Graph (10K → 1M users, 1-3 years)
+
+Customer: The early adopter base expands to include privacy-conscious mainstream users. The trigger is a /platform failure event/: a major platform bans a creator, de-platforms a community, or suffers a data breach. When that happens, the Agora is ready — it offers the same social primitives (messaging, identity, publishing) but with ownership.
+
+Growth lever: Metcalfe's law + switching cost. Each new user makes the network more valuable. But the real lock-in is the /reputation graph/: attestations, signatures, and data provenance are cumulative. A user with 3 years of verified activity on the Agora cannot replicate that on any other platform. The switching cost grows with time.
+
+Tactics:
+
+1. Ship verified messaging. Every message between Agora users is signed and timestamped. No third party can modify or delete it. The product pitch: /Twitter, but your tweets are yours, and nobody can rewrite history/.
+
+2. Publish an attestation API. Third-party services (news outlets, marketplaces, social platforms) can query the Agora to verify a user's reputation. News comments show "verified human, 2yr history, no abuse flags." This creates /outbound value/ — the network becomes useful to people who aren't even on it.
+
+3. Offer PDS-to-PDS federation. Agora instances communicate directly. No central server. This differentiates from every centralized platform and gives a structural privacy advantage that no amount of VC funding can replicate.
+
+4. Introduce data licensing. Users can license their verified data to AI training companies, researchers, advertisers — on their own terms, with their own price. The Agora takes a 10-15% commission. This creates a /revenue share/ that users understand viscerally. Compare: X/Twitter makes billions selling user data and gives nothing back. Agora users get paid.
+
+5. Verification becomes visible. Each user's profile shows a "verification score" based on the length and depth of their attested history. Long-time users get a visible badge. This creates status competition around the /one thing nobody else can offer/: provable history.
+
+Revenue:
+| Stream | Year 3 target | Mature |
+|--------+--------------+--------|
+| PDS hosting subscriptions | $500K-2M | $10-50M/yr |
+| Data licensing commissions | $200K-1M | $20-100M/yr |
+| Premium username renewals | $100K-500K | $5-10M/yr |
+| Verified badge program | $100K-300K | $2-5M/yr |
+| Attestation API (per-query) | $50K-200K | $5-20M/yr |
+| Total | $1-4M | $42-185M/yr |
+
+Key metric: Daily active PDS users. Inter-instance messages per day. Attestation API queries.
+
+Failure mode: Network effects fail to trigger because the user experience is not /better/ than existing platforms — it's /different/. Different is not enough. The product must match or exceed the UX of mainstream social platforms while offering the ownership advantage. If the UX gap is too large, users stay on Twitter/Bluesky/Threads despite the privacy cost.
+
+* Phase 2: The Institution Crossover (1M → 10M users, 2-5 years)
+
+Customer: At 1M+ active identities, the network has critical mass. Institutions (universities, media companies, government agencies, enterprises) can no longer ignore it because /their users are on it/. The crossover happens organically: a university registrar wants to issue verified credentials. A newsroom wants to publish with verified provenance. A regulator wants to use the Agora's attestation infrastructure because it already has users.
+
+Growth lever: Institutional network effects. Every institution that joins brings 10K-100K users with it (employees, students, customers). Each new institutional user increases the value of verification for everyone else. The growth curve becomes logistic with institutional jumps, not smooth organic growth.
+
+Tactics:
+
+1. Ship the Stoa enterprise bundle (SSO, compliance reports, fleet management, audit logging). This was the /entire/ Phase 0-1 of the institution-first scenario. Here it is a Phase 2 feature — built to serve institutions that are already /inside/ the network, not sold to cold prospects.
+
+2. Offer verified credentialing: degrees, certifications, professional licenses, issued on the Agora, verifiable by anyone. The institution pays for the issuance. The graduate gets a portable, provable credential.
+
+3. Offer provenance publishing: news organizations publish articles signed by their Agora identity. Readers verify provenance in one click. Deepfakes and misinformation are detectable because the authentic source is attested. This creates a /consumer pull/ for verification that never existed in the institution-first scenario.
+
+4. Verification appliances are now a /fulfillment order/, not a sales pitch. Institutions already inside the network ask: "Can we run our own instance?" The answer is yes — here is a Stoa appliance. The gate rule SDK is a value-up, not a product.
+
+5. The compute marketplace activates naturally. With 10M+ users and thousands of institutions, compute supply and demand are both present without bootstrapping.
+
+Revenue:
+| Stream | Year 5 target | Mature |
+|--------+--------------+--------|
+| Enterprise Stoa seats | $5-20M | $50-200M/yr |
+| Verified credential issuance | $2-10M | $20-100M/yr |
+| Compute marketplace fees | $1-5M | $50-200M/yr |
+| PDS hosting (scaled) | $2-10M | $20-50M/yr |
+| Data licensing (scaled) | $1-5M | $20-100M/yr |
+| Verification appliances | $2-10M | $50-100M/yr |
+| Total | $13-60M | $210-750M/yr |
+
+Key metric: Institutional join events. Enterprise Stoa subscriptions. Credentials issued.
+
+Failure mode: The institution crossover never comes because the social graph stalls at 1M users — enough for a niche, not enough for critical mass. The network becomes a high-quality-but-small community like early App.net or Mastodon. Verification is real but irrelevant because the rest of the world is on different platforms. The institution-first scenario is still possible from here (direct enterprise sales), but the supposed advantage of "users first" has not materialized.
+
+* Phase 3: Default Infrastructure (10M → 1B+, 5-15 years)
+
+Customer: At this scale, the Agora is the default identity and communication layer for a significant fraction of internet users. New users join because /everyone is there/. Institutions join because /everyone is there/. The regulatory capture that the institution-first scenario required as a /growth lever/ happens here as a /consequence/ — regulators adopt Agora attestation because it is the standard.
+
+Growth lever: Default status. The network is the path of least resistance. A new social platform would need to replicate not just the user base but the entire attestation history, compute marketplace, and institutional infrastructure. The moat is not legal (regulation) but practical (installed base + cumulative value).
+
+Tactics: Similar end state to the institution-first scenario — verification monopoly, certified appliance sales, insurance marketplace, nation-state deployments. The difference is the /path/ and the /character/ of the moat:
+
+- Institution-first moat: regulatory lock-in. You comply because the law requires it.
+- Social-first moat: installed-base lock-in. You join because everyone is there.
+
+The regulatory moat is faster to deploy but brittle (a change in government can undo it). The installed-base moat is slower to build but self-reinforcing.
+
+Revenue: Same end state as growth-strategy.org Phase 3 — $1B+ across certification, infrastructure rent, marketplace fees, and insurance underwriting.
+
+* Comparison: Two Paths Side By Side
+
+| Dimension | Institution-first | Social-first |
+|-----------+------------------+-------------|
+| First customer | CISO, compliance buyer | Indie creator, privacy user |
+| First revenue | $2-12M (year 1) | $120K-800K (year 1) |
+| Time to $10M ARR | 12-24 months | 3-5 years |
+| Time to $50M ARR | 2-4 years | 5-7 years |
+| Time to $1B+ | 5-15 years | 10-20 years |
+| Capital requirement | Low (revenue-funded) | Moderate (must subsidize UX) |
+| Marketing cost | Sales team + compliance mktg | Community + platform events |
+| Key execution skill | Enterprise sales | Consumer product design |
+| Network effect trigger | Developer ecosystem (Phase 1) | Identity scarcity (Phase 0) |
+| Moat type | Regulatory + insurance | Installed base + attestation |
+| Moat durability | Good (legal) | Strong (practical) |
+| Regulatory risk | Dependent (must stay legal) | Independent (regs follow users) |
+| Failure mode | Wrong pricing, too early | Network never reaches critical mass |
+
+* Assessment: Which Is More Likely?
+
+Institution-first is more likely. Here is why:
+
+The triad's core competence is /verification/ — building provably correct systems in ACL2. That maps directly to enterprise compliance pain. A CISO can understand "prove my code is compliant" in one meeting. A consumer cannot understand "prove your identity is yours" without a 10-minute explanation.
+
+The social-first path asks the product to be /also/ a consumer social network. That is a different product, a different team, a different skill set. The verification infrastructure that makes the triad unique is irrelevant to the social-first Phase 0 — users join for the name, not the proof. This means the social-first path's Phase 0 has no durable advantage over any other identity product (ENS, Bluesky AT Protocol, Keybase). The advantage only appears in Phase 2, after years of cumulative attestation. Survival to Phase 2 requires either fast growth (like Instagram) or patient capital (like Wikipedia). Neither is a high-probability bet.
+
+The social-first path's /best/ version is: a platform failure event hands you 1M users overnight. That is uncontrollable and unlikely. The institution-first path's best version is: one compliance engagement funds the next, and the revenue curve is smooth.
+
+However: the two paths are not mutually exclusive. The institution-first path can seed the social network. Every enterprise PDS deployment includes Agora identities for employees. Every gate rule developer is an Agora user. The social graph grows as a /byproduct/ of institutional adoption, not as a separate effort. This hybrid path — verification sales + organic identity network — may be the real strategy: bet on institutions, let the social network emerge.
+
+The social-first path's strongest argument is end-state durability. An installed-base moat (everyone uses it) outlasts a regulatory moat (the law requires it). But getting to the end state requires surviving Phase 0 and Phase 1 on much thinner revenue, and the probability of reaching Phase 2 is lower.
+
+* References
+
+- [[file:growth-strategy.org][Primary growth strategy — institution-first]]
+- [[file:revenue-hub.org][Revenue streams by component]]
+- [[file:agora-contracts.org][Agora contract platform details]]
+- [[file:effects-growth-flywheel.org][Effects and growth as interleaved curves]]
+- [[file:time-estimates.org][Development timeline — Phase Zero and End State]]
+
+#+begin_quote
+The social-first path is attractive because the end state is stronger. But the path to it requires building a consumer product alongside the deep-tech verification infrastructure — essentially running two startups in parallel. The institution-first path is the higher-probability bet because it monetizes the core technical advantage from day one.
+#+end_quote