3.9 KiB
3.9 KiB
Strategy
Business strategy, competitive analysis, compliance landscape, and market positioning.
-
Adoption — the unified adoption and growth document. Two separate adoptions (social and institutional), each with own phases, flywheel, and dynamics
-
Impact — overview of social, cultural, political, economic, scientific, and geopolitical consequences
- Phase 0 — 10-10² users. First compliance savings, first communities, nothing breaks.
- Phase 1 — 10²-10⁴ users. Refugees, creators, first unbundling signals.
- Phase 2 — 10⁴-10⁶ users. Insurance wedge, contract marketplace, mutual pools.
- Phase 3 — 10⁶-10⁸ users. Cybersecurity/ad collapse, institution crossover, financial disruption.
- Phase 4 — 10⁸-10⁹ users. Two-tier equilibrium, full financial transformation.
- Game Theory — strategic analysis, Nash equilibria, and failure modes
-
- Revenue — detailed revenue streams by phase, subsystem, and first-mover window
- Moats — competitive barriers and infrastructure lock-in
- Evaluation Harness — collective regression suite as certification monopoly
- Licensing and Patents — AGPL strategy and patent approach
- Development Timeline — Phase Zero vs End State estimates
- Sufficiency Flip — per-domain autonomy from LLM dependency
- Social Protocol Entry Strategy — tactical go-to-market for community onboarding
- Smart Contracts and Contract Marketplace — SCAL, escrow, arbitration
- Compute Marketplace — verified compute exchange
- Personal Data Store — PDS hosting service
- Premium Username Registry — namespace economics
- Verification Appliance — hardware appliance
- Lisp Economics — zero marginal cost argument
- AI Industry Impact — effect on GPU demand and AI market
- Upgrade Lifecycle — distribution and migration
- Outbound Sales Strategy — legal and compliance sales framework
- Verified Skill Marketplace — certified skill marketplace
-
Competitive Analysis — competitor landscape
- AI Agent Landscape — scoping of AI coding agents
- Compliance Index — all regulated frameworks by region and priority
- Domain Gate Packages — gate rule encoding for compliance domains
- Compliance Framework Mapping — mapping gate architecture to each regulation
See the Architecture page for how the subsystems compose, and the Development Timeline for when each component ships.