amr/hermes-brain
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

rewrite: combined growth strategy — Logos (top-down verification) + Agora (bottom-up communities) as two engines, one infrastructure

Browse Source
This commit is contained in:
Hermes
2026-05-23 14:01:43 +00:00
parent 89a9ee0c2c
commit 59e9ced3e5
1 changed files with 145 additions and 61 deletions
Download Patch File Download Diff File Expand all files Collapse all files

206
ideas/growth-strategy.org
View File

@@ -2,115 +2,199 @@
:ID: growth-strategy :ID: growth-strategy
:CREATED: [2026-05-23 Sat] :CREATED: [2026-05-23 Sat]
:END: :END:
#+title: Growth — Zero to Billions Across Time Scales #+title: Growth — Two Engines, One Infrastructure
#+filetags: :passepartout:growth:network:strategy: #+filetags: :passepartout:growth:network:strategy:agora:
How the triad grows from zero instances to planetary infrastructure. Each phase is a qualitatively different growth regime, with its own customers, levers, and failure modes. The triad has two independent growth engines that share the same infrastructure. Logos (verification) grows top-down through enterprise compliance sales — capital-efficient, revenue from day one. Agora (the social network) grows bottom-up through community adoption — network-effect-powered, zero customer acquisition cost per user. Each engine would be incomplete alone. Together they form the full stack: verification funds the build, the network provides the users, and at every crossover point they make each other more valuable.
The growth curve is logistic, not exponential from day one. Enterprise first (linear, high value per node), then developer-led (quadratic, moderate per node), then regulatory/insurance-driven (punctuated). The stacked network effects make each subsequent phase easier to scale than the previous one — but each phase must be solved /before/ the next can begin. This page defines the combined growth strategy across four phases, with each engine advancing in parallel and reinforcing the other at specific transitions.
* Phase 0 → 1: Zero to Enterprise (0 → 100 instances, 3-12 months) * The Two Engines
/Logos (top-down, revenue-funded):/
- Customer: CISO, compliance buyer
- Growth lever: Enterprise sales + gate rule library compounding
- Revenue: $2-12M/year by month 12
- Failure mode: Wrong pricing, too early for market
- Entry: Direct enterprise compliance engagements
/Agora (bottom-up, community-driven):/
- Customer: Organized communities, creators, developers
- Growth lever: Multi-vector network effects (identity, publishing, payments, contracts, governance)
- Revenue: Transaction fees, PDS hosting, marketplace commissions
- Failure mode: Never reaches critical mass on any vector
- Entry: Organized community onboarding pilot groups, then expand
* Phase 0: Bootstrapping (0 → 100 instances, 0 → 10K Agora users, 3-12 months)
** Logos Engine
*Customer:* Enterprise compliance teams. Clear buyer (CISO), existing budget, pain that maps directly to gate rules. *Customer:* Enterprise compliance teams. Clear buyer (CISO), existing budget, pain that maps directly to gate rules.
*Growth lever:* Enterprise sales + direct integration. No network effects yet — value must be real without anyone else using it. *Growth lever:* Enterprise sales + direct integration. No network effects yet — value must be real without anyone else using it.
*How it works:* *Tactics:*
1. Ship Passepartout MVP — verifies code, applies gate rules, produces compliance report.
2. First sale encodes a regulation as gate rules, verifies the customer's deployment.
3. Each engagement funds the next. Gate rule library grows with every customer.
4. The compute marketplace bootstraps with one provider (you) selling verification to smaller instances.
1. Ship the MVP ([[file:time-estimates.org]]) — a Passepartout that verifies code, applies gate rules, and produces a compliance report. *Revenue:* $2-12M from enterprise compliance engagements. Funds the team and the Agora build.
2. First sale is a compliance engagement: encode a regulation as gate rules, verify the customer's deployment, produce a report their auditor accepts.
3. Each engagement funds the next. Gate rule library grows with every customer. This compounds — each new regulation encoded is a product, not a project.
4. The compute marketplace ([[file:compute-marketplace.org]]) bootstraps with one provider (you) selling verification to smaller instances. No liquidity problem because you are both sides of the market initially.
*Key metric:* Deployed instances. Gate package revenue. Regulations encoded. ** Agora Engine
*Failure mode:* Wrong pricing. Too early for market. The compliance buyer exists but the product must replace an existing process, not add a new line item. *Customer:* Organized communities — HOAs, clubs, cooperatives, PTAs, volunteer orgs, religious groups — any group that currently uses 3+ separate tools and has a leader who can onboard them.
*Phase 0 revenue:* $2M-$12M (from [[file:investment-thesis.org]]). Funds the team, keeps the lights on. *Growth lever:* Group density solves the cold start. The community exists before the platform. Onboard one HOA of 200 families, get 200 users at once.
* Phase 1: 1 to 10³ — Enterprise to Developer Ecosystem (100 → 10,000 instances, 12-24 months) *Tactics:*
1. Identify 5-10 pilot communities via warm intros or personal networks.
2. Each gets a white-glove onboarding: admin sets up their Collective Persona, invites members via share link.
3. Members arrive to find a complete community space: announcement feed, group chat, task board, treasury, voting.
4. The first real use case (budget vote, dues collection, contractor hire) is the killer demo.
5. Ship identity + content + contracts + payments + governance. The bundle must work from day one for organized communities — they need all five layers.
*Revenue:* Minimal in Phase 0 ($20-100K in transaction fees). The goal is product-market fit with a specific community type, not revenue.
*Key metric for crossover:* Community retention at 90 days. If a community is still using the Agora for its core operations after 90 days, the bundle has stickiness.
*Phase 0 crossover:* The first enterprise compliance customer needs employee identities. Their PDS deployment seeds Agora identities for the compliance team. This is accidental — the enterprise's employees get DIDs as a side effect of their company buying verification. The Agora gets its first non-community users for free.
** Combined Summary
| Dimension | Logos | Agora |
|-----------+-------+-------|
| Customer | CISO, compliance buyer | HOA president, club leader |
| Entry | Cold sales | Warm intro to pilot communities |
| Revenue | $2-12M | $20-100K |
| Key metric | Instances deployed | Communities active at 90 days |
| Failure mode | Wrong pricing, too early | No community finds PMF |
| Build priority | Passepartout MVP | Note primitive, PDS, SCAL basics |
* Phase 1: Dual Growth (100 → 10K instances, 10K → 100K Agora users, 12-24 months)
** Logos Engine
*Customer:* Two-sided — enterprise compliance (continuing Phase 0) plus individual developers adopting Passepartout through AGPL. *Customer:* Two-sided — enterprise compliance (continuing Phase 0) plus individual developers adopting Passepartout through AGPL.
*Growth lever:* Open-source adoption + platform economics. The gate rule SDK lets developers create and sell their own gate rules. The marketplace has supply. *Growth lever:* Open-source adoption + platform economics. The gate rule SDK lets developers create and sell their own gate rules.
*How network effects kick in:* *Tactics:*
1. Gate rule SDK launch — developers encode compliance domains as products.
2. Proof library compounding — every new instance contributes edge cases.
3. Attestation marketplace — track record of correct verifications carries weight.
4. Agora identities as employee benefit — every enterprise PDS includes DIDs for all employees.
1. /Proof library compounding:/ Each new instance contributes edge cases to the regression suite ([[file:collective-regression-suite.org]]). Ten instances have a good proof library; a hundred have a great one; a thousand have a library no single organization could build alone. The curve is super-linear in instances. *Revenue:* $10-50M. Verification appliances, marketplace fees, Agora username registrations.
2. /Compute marketplace liquidity:/ 100+ instances means providers and consumers exist simultaneously. The marketplace can price verification in real time. No single instance needs to provision for peak load — they buy burst compute from the marketplace. *Key metric:* Third-party gate rules published. Active developer count.
3. /Attestation starts working:/ With 100+ instances, a track record of correct verifications carries weight. The attestation marketplace ([[file:agora-contracts.org]]) has enough data for reputation scores. The first insurance products become possible. ** Agora Engine
*Revenue growth:* $10M-$50M. Verification appliances scale from project to program. Marketplace fees begin. Agora usernames ([[file:agora-usernames.org]]) start generating recurring revenue. *Customer:* Community refugees (banned subreddits, nuked Discord servers) + creators (OnlyFans/Patreon refugees who want to own their audience).
*Key metric:* Third-party gate rules published. Marketplace monthly transaction volume. Active developer count. *Growth lever:* Crisis-driven migration + creator-led audience migration.
*Failure mode:* Developer adoption stalls because the AGPL experience is not polished enough. Gate rule SDK is too hard to use. This phase requires the most product attention — the first thousand developers must succeed. *Tactics:*
1. Monitor deplatforming events. When a subreddit of 10K+ users gets banned, offer a ready-made Agora community space within 24 hours.
2. Ship creator tools: LSAT for paywalled content, Lightning subscriptions, Blind CDN for video distribution.
3. The Phase 0 pilot communities now have members who need to hire each other. Freelance contracts emerge organically.
4. Every enterprise PDS deployment from the Logos engine includes employee DIDs. Those employees can join Agora communities with zero friction.
* Phase 2: 10³ to 10⁶ — Developer to Mainstream (10,000 → 1M, 2-5 years) *Revenue:* $1-5M. Transaction fees from contracts, LSAT subscriptions, PDS hosting.
*Customer:* Consumers + small businesses. PDS as a service ([[file:pds-as-a-service.org]]) becomes a consumer product. Agora usernames go mainstream. *Key metric:* Communities onboarded. Paying subscribers. Contract volume.
*Growth lever:* Consumer network effects. Each new PDS makes the Agora network more valuable. Each new user is a potential compute provider, gate rule buyer, and data licensor. ** Phase 1 Crossover
*How it works:* This is the critical reinforcement point:
1. /Stoa premium ([[file:revenue-hub.org]]) ships enterprise features./ SSO, compliance dashboards, fleet management. The enterprise buyer from Phase 1 upgrades from project to org-wide deployment. - Enterprise employees already have Agora DIDs (from their company's PDS). They can join Agora communities with one click — no registration, no password, no onboarding friction.
- Agora communities naturally need verification. An HOA's contractor hire should be verified. A community's vote results should be provable. The verification engine that Logos built for enterprises is now useful for communities.
- The compute marketplace now has two demand sources: enterprise verification (production workloads) and community verification (contract executions, attestation requests).
2. /Agora identity reaches critical mass./ Username registrations cross 100K. The namespace has value — short names are scarce. The auction market ([[file:agora-usernames.org]]) produces real revenue. *Phase 1 crossover metric:* Percentage of Agora transactions that use Logos verification. Target: 10%+ by end of Phase 1.
3. /Compute marketplace hits density./ 1M+ instances means verification is ubiquitously available. Latency drops because there is always a provider within network distance. The marketplace transitions from /can I find a provider/ to /which provider gives the best price/. * Phase 2: Convergence (10K → 1M instances, 100K → 10M Agora users, 2-5 years)
4. /Insurance marketplace forms./ With 10K+ instances and 2+ years of verifiable track records, actuaries can price proof insurance. The first products: /gate rule correctness insurance/ and /compute provider SLA insurance/. ** Logos Engine
*Revenue growth:* $50M-$500M. Compute marketplace fees become the dominant revenue stream. PDS hosting at scale. Username registry renewals compound. *Customer:* Enterprise compliance (continuing) + verification marketplace (scaling) + insurance industry.
*Key metric:* Agora identities. PDS count. Verified operations per day. Marketplace gross merchandise value. *Growth lever:* Stoa premium enterprise features + insurance marketplace.
*Failure mode:* Consumer adoption requires UX polish the engineering team may deprioritize. The terminal-based Stoa works for developers but not for mainstream users. Qt integration (Stoa v2 from [[file:stoa.org]]) is the gating dependency. *Tactics:*
1. Stoa premium ships SSO, compliance dashboards, fleet management.
2. Insurance marketplace forms — actuaries price proof insurance based on track records of 10K+ instances.
3. Verification monopoly begins — the gate library is the largest, most cited, most battle-tested.
* Phase 3: 10⁶ to 10⁹ — Mainstream to Infrastructure (1M → 1B+, 5-15 years) *Revenue:* $50-200M. Stoa enterprise seats, verification appliances, insurance premiums.
*Customer:* Nation-states. Enterprises that cannot justify unverified infrastructure. Anyone who needs insurance. ** Agora Engine
*Growth lever:* Regulatory mandate + insurance feedback loop. Verification is no longer a choice — it is a requirement for participation in the insured economy. *Customer:* Freelancers, gig workers, small businesses. The organized communities from Phase 0-1 now have enough history that their reputation graph carries real weight.
*How the loop closes:* *Growth lever:* Professional network effects. A freelancer's contract history on the Agora is portable proof of reliability. The reputation is not tied to any platform — it's tied to their DID.
1. /Verification monopoly ([[file:verification-monopoly.org]]):/ The early player's gate library is the largest, most battle-tested, most cited. Regulators reference it. Insurers require it. A new entrant cannot replicate 10+ years of edge cases embedded in 1M+ instances. *Tactics:*
1. Freelancer marketplace emerges organically — communities that already use contracts start hiring across communities.
2. The Algorithm Marketplace creates differentiation — users choose their feed curation logic.
3. Agora identities hit 1M. The namespace has real scarcity. Premium username auctions produce significant revenue.
4. Enterprise adoption of Agora happens because employees already have DIDs. Companies start using Agora spaces for internal collaboration.
2. /Insurance lock-in:/ Insurers price unverified code out of existence. Premiums for unverified deployments are 10× or more. The cost of /not/ verifying exceeds the cost of adopting the triad. This is the insurance parallel to what happened with fire safety — buildings without sprinklers cannot get insured. *Revenue:* $20-100M. Transaction fees, PDS hosting, marketplace commissions, username renewals.
3. /Nation-state adoption:/ The compute marketplace is a sovereign asset. Countries that run their own triad instances have verified digital sovereignty. Countries that do not are dependent on foreign verification infrastructure. The geopolitics are self-reinforcing (see [[file:triad-systemic-effects.org]]). ** Phase 2 Crossover
*Revenue growth:* $1B+. Certification monopoly revenue. Infrastructure lock-in rent. Marketplace fees at global scale. Insurance underwriting profits. The two engines begin to merge:
*Key metric:* Percentage of global compute running on verified stack. Number of nation-state triad deployments. Insurance premiums written against gate rules. - Verification is no longer an enterprise-only product. It is a network service consumed by every Agora transaction. Every contract execution, every attestation, every vote runs through the compute marketplace.
- The Agora's reputation graph becomes the best source of verification track records. Actuaries price insurance based on DID history. The insurance products that Logos enables are /powered by/ Agora data.
- Enterprise employees use the same DID for compliance work and community participation. The boundary between "work identity" and "personal identity" is a Persona toggle — same infrastructure, different roles.
*Failure mode:* Technology shift makes the approach obsolete. A fundamentally different verification paradigm (quantum proof systems, for example) could bypass ACL2. The installed base is a moat, not a guarantee. *Phase 2 crossover metric:* Percentage of verification requests that originate from Agora transactions. Target: 50%+ by end of Phase 2.
* Growth Curve Summary * Phase 3: Infrastructure (1M → 10M+ instances, 10M → 1B+ Agora users, 5-15 years)
| Phase | Scale | Timeframe | Revenue | Primary lever | Failure mode | ** Both Engines
|-------+-------+----------+---------+--------------+--------------|
| 0 | 0→100 | 3-12 mo | $2-12M | Enterprise sales | Wrong pricing, too early |
| 1 | 10²→10⁴ | 1-2 yr | $10-50M | Open source + SDK | Developer UX |
| 2 | 10⁴→10⁶ | 2-5 yr | $50-500M | Consumer network effects | UX polish gap |
| 3 | 10⁶→10⁹ | 5-15 yr | $1B+ | Regulation + insurance | Tech paradigm shift |
Each phase's revenue funds the next. Phase 0 pays for the team. Phase 1 funds the product. Phase 2 builds the moat. Phase 3 is the end state. At this scale, the distinction between Logos and Agora becomes meaningless. Verification is the compute layer. The Agora is the application layer. They are the same infrastructure:
The network effects stack across phases: Phase 0's proof library makes Phase 1's marketplace valuable. Phase 1's developer ecosystem makes Phase 2's consumer product compelling. Phase 2's installed base makes Phase 3's regulatory capture possible. No phase can be skipped — and no phase guarantees the next. - /Verification monopoly:/ The gate library is the most comprehensive proof library ever assembled. Regulators reference it. Insurers require it.
- /Default identity:/ The Agora DID is the default identity for internet users. New services offer Agora login because users demand it.
- /Insurance lock-in:/ Insurers price unverified code out of existence. The cost of /not/ verifying exceeds the cost of adopting the triad.
- /Nation-state adoption:/ Countries run their own triad instances for digital sovereignty. The compute marketplace is a sovereign asset.
- /Installed base moat:/ A new entrant cannot replicate 10+ years of attestation history, 1B+ identities, and millions of verified contracts.
*Revenue:* $1B+. Certification monopoly revenue, infrastructure rent, marketplace fees, insurance underwriting, PDS hosting at global scale.
* The Combined Curve
| Phase | Logos scale | Agora scale | Revenue | Crossover | Failure mode |
|-------+-------------+-------------+---------+-----------+--------------|
| 0 | 0→100 instances | 0→10K users | $2-12M | Enterprise PDS seeds first DIDs | Either engine stalls |
| 1 | 100→10K inst | 10K→100K users | $11-55M | Employees join communities; communities need verification | Logos: developer UX. Agora: no vector reaches PMF |
| 2 | 10K→1M inst | 100K→10M users | $70-300M | Most verification serves Agora; most Agora data feeds verification | Logos: scaling compute. Agora: UX polish gap |
| 3 | 1M→10M+ inst | 10M→1B+ users | $1B+ | The layers are unified | Technology paradigm shift |
* Why This Works Together
Organized communities are the entry point that forces the Agora to ship the full bundle from day one. An HOA using the Agora for announcements, dues, contracts, and voting demonstrates the complete vision — identity + content + payments + contracts + governance — in a single, understandable use case. No marketing message can compete with a community member seeing their dues collected and a roof contract executed through one platform.
Enterprise compliance funds the build. A Phase 0 CISO engagement brings in $500K-2M, enough to pay a small team for a year. The same team ships the Agora Note primitive, PDS, and SCAL. The enterprise revenue buys time for the community adoption to find PMF.
The crossover is automatic. Enterprise employees get DIDs from their company's PDS. They join Agora communities because the DID works everywhere. Communities need verification for their contracts and votes. The verification engine is already running. The two engines were never separate — they were always the same infrastructure, just adopted by different users at different times.
* References * References
- [[file:time-estimates.org][Development timeline]] — the engineering underpinning - [[file:time-estimates.org][Development timeline]]
- [[file:revenue-hub.org][Revenue streams]] — what each phase sells - [[file:revenue-hub.org][Revenue streams]]
- [[file:investment-thesis.org][Investment thesis]] — the three revenue horizons - [[file:investment-thesis.org][Investment thesis]]
- [[file:triad-systemic-effects.org][Systemic effects]] — where this all leads - [[file:alternative-growth-social-first.org][Social-first alternative (now integrated)]]
- [[file:compute-marketplace.org][Compute marketplace]] — the liquidity engine - [[file:agora-entry-strategy.org][Entry strategy — organized communities]]
- [[file:verification-monopoly.org][Verification monopoly]] — the end state moat - [[file:competitive-landscape-agora.org][Agora competitive landscape]]
- [[file:agora-contracts.org][Agora contracts]] — attestation, insurance, governance - [[file:triad-systemic-effects.org][Systemic effects]]
- [[file:collective-regression-suite.org][Collective regression suite]] — how proof libraries compound with scale - [[file:compute-marketplace.org][Compute marketplace]]
- [[file:infrastructure-lock-in.org][Infrastructure lock-in]] — why switching costs compound - [[file:verification-monopoly.org][Verification monopoly]]
- [[file:agora-contracts.org][Agora contracts]]
- [[file:../agora/docs/agora-requirements-00-readme.org][Agora Protocol Specification — full requirements]]