gbrain: sync converted org-mode brain files

ideas/effects-growth-flywheel.org

@@ -0,0 +1,94 @@
+:PROPERTIES:
+:ID:       effects-growth-flywheel
+:CREATED:  [2026-05-23 Sat]
+:END:
+#+title: Effects–Growth Flywheel — How Adoption and Consequences Amplify Each Other
+#+filetags: :passepartout:strategy:growth:effects:flywheel:
+
+The effects page ([[file:triad-systemic-effects.org]]) and the growth page ([[file:growth-strategy.org]]) treated two sides of the same process as separate timelines. They are not sequential — effects do not wait for adoption to finish, and adoption does not happen before effects begin. They are interleaved at every scale. Each effect is a growth driver; each growth milestone unlocks new effects.
+
+The key insight: /every systemic effect is a growth engine for the next phase/. There is no phase where effects passively happen while adoption independently proceeds.
+
+* The Flywheel, Not the Pipeline
+
+The old model (sequential, linear):
+
+    Growth Phase 0 → Effects Phase 0 → Growth Phase 1 → Effects Phase 1 → ...
+
+The real model (interleaved, amplifying):
+
+    Enterprise sale → compliance cost drops → more enterprises buy → compliance industry margin erodes → price drops further → small businesses afford gate rules → regulator notices → regulation-as-code → enterprises /must/ buy → ...
+
+At every scale, the effect /is/ the growth mechanism. There is no waiting for effects to "arrive" after adoption reaches a threshold. The first enterprise that saves $500K on an audit has already triggered the compliance erosion effect — at scale 10⁶, that same effect is a structural industry shift, but it is the same mechanism operating at different magnitudes.
+
+* Effect–Growth Map at Each Scale
+
+** Phase 0 (0 → 10² instances, weeks–months)
+
+| Instance count | Effect that starts | Growth driver generated |
+|---------------+-------------------+------------------------|
+| 1–10 | /Scientific reproducibility:/ the first verified paper | Universities buy Passepartout for their compute clusters |
+| 1–10 | /Compliance erosion:/ first enterprise replaces audit with gate rule | Competitors must match the cost savings — enterprise sales accelerate |
+| 10–50 | /Verification API gateway:/ first company runs LLM calls through Passepartout | /Any/ company using LLMs is a customer, not just triad adopters. This effect starts at 10 instances but can scale to millions of API users before growth Phase 1 |
+
+Key observation: the verified API gateway decouples the effect from triad adoption. A company using the gateway never installs Passepartout — they send API calls to a proxy and get back a proof log. The gateway is an /effect/ that drives /economic growth/ (revenue) without requiring /ecosystem growth/ (instances).
+
+** Phase 1 (10² → 10⁴ instances, months–years)
+
+| Instance count | Effect that starts | Growth driver generated |
++---------------+-------------------+------------------------
+| 100–500 | /Regulation as code:/ first regulator encodes a rule as a gate | All regulated entities under that regulator must adopt Passepartout — step function in demand |
+| 500–2K | /AI safety shift:/ gate rule verification becomes expected in enterprise AI procurement | Every company buying AI services requires a proof log — API gateway demand explodes |
+| 2K–10K | /Proof library compounding:/ the collective regression suite has enough edge cases to be qualitatively better than any solo library | Competitive advantage for adopters — those not on the network fall behind on verification coverage |
+
+Key observation: regulation-as-code creates a /step function/ in demand. Before the regulator acts, growth is organic enterprise sales. After, it is mandatory compliance. The timing of the first regulatory encode is the single most leveraged event in the flywheel.
+
+** Phase 2 (10⁴ → 10⁶ instances, years)
+
+| Instance count | Effect that starts | Growth driver generated |
++---------------+-------------------+------------------------
+| 10K–50K | /Computational trust:/ PDS model makes surveillance advertising visibly obsolete | Consumer demand for PDS — "why does my bank still own my data?" |
+| 50K–200K | /Verification cachet:/ /I verify/ becomes a resume signal | Developer adoption accelerates — not from enterprise mandate but from peer pressure and cultural norm |
+| 200K–1M | /Attestation marketplace:/ verifiable reputation has enough data to be reliable | Insurance products become viable — insurers price unverified code higher |
+
+Key observation: the shift from enterprise adoption to consumer adoption is cultural, not technical. The technology works at 10K instances. But consumers don't adopt because the tech works — they adopt because the /alternative is socially unacceptable/. The verification cachet effect /is/ the consumer growth engine.
+
+** Phase 3 (10⁶ → 10⁹ instances, years–generations)
+
+| Instance count | Effect that starts | Growth driver generated |
++---------------+-------------------+------------------------
+| 1M–10M | /Insurance loop closes:/ premiums for unverified code are 10× verified | Economic necessity drives adoption — not engineering preference, not regulation, but /cost of doing business/ |
+| 10M–100M | /Verification monopoly:/ regulator references the early player's gate library | New entrants cannot compete with the installed proof base — the moat compounds with every new instance |
+| 100M–1B | /Compute as geopolitical asset:/ nations run triad instances for digital sovereignty | Nation-state procurement — 100M to 1B happens via government mandate, not organic adoption |
+
+Key observation: the insurance loop is the /completion of the flywheel/. At this point, adoption is no longer driven by the triad's features or benefits — it is driven by the /cost of non-adoption/. The flywheel transitions from pull (people want verification) to push (people cannot afford to be unverified).
+
+* The Critical Path
+
+The flywheel has two critical bottlenecks:
+
+1. /First regulator encodes a rule as a gate./ This is the most leveraged event in Phase 0–1. It converts growth from organic to mandatory in a single domain. Whoever reaches a regulator first — and helps them write that first gate rule — wins that domain permanently.
+
+2. /First insurer prices unverified code higher./ This is the Phase 2→3 transition. It converts growth from pull to push. The insurer does not need 1B instances to act — they need 10K instances with 2+ years of verifiable track records. The compute marketplace ([[file:compute-marketplace.org]]) provides the actuarial data; the attestation marketplace ([[file:agora-contracts.org]]) provides the reputation layer.
+
+* Summary: Effects and Growth Are the Same Curve
+
+| Adoption (instances) | Dominant effect | Growth mechanism |
+|---------------------+----------------+------------------|
+| 0 → 10² | Compliance cost drops | Enterprise sales — the effect /is/ the value proposition |
+| 10² → 10⁴ | Regulation becomes executable | Mandate — one regulator converts pull to push in a domain |
+| 10² → 10⁴ | AI safety shifts to engineering | Verified API gateway sells to /any/ LLM user, decoupled from triad adoption |
+| 10⁴ → 10⁶ | Trust shifts from institutional to computational | Consumer adoption — cultural norm, not technical requirement |
+| 10⁶ → 10⁹ | Cost of non-verification exceeds cost of adoption | Insurance + regulation lock-in — economic necessity, not preference |
+
+Each row's effect /is/ the growth driver for the next row's instance count. The flywheel is the product. The triad is the architecture. The verification monopoly is the steady state.
+
+* References
+
+- [[file:triad-systemic-effects.org][Systemic effects over time]]
+- [[file:growth-strategy.org][Growth phases — zero to billions]]
+- [[file:time-estimates.org][Development timeline]]
+- [[file:revenue-hub.org][Revenue per phase]]
+- [[file:compute-marketplace.org][Compute marketplace]]
+- [[file:agora-contracts.org][Attestation and insurance]]
+- [[file:verification-monopoly.org][Verification monopoly]]