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

fix: inline org-mode interlinks instead of parenthetical bare [[file:...]] links

Browse Source
This commit is contained in:
Hermes
2026-05-23 20:24:19 +00:00
parent 674b8b35ba
commit 8f875dc192
5 changed files with 12 additions and 12 deletions
Download Patch File Download Diff File Expand all files Collapse all files

4
ideas/effects-growth-flywheel.org
View File

@@ -5,7 +5,7 @@
#+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 [[file:triad-systemic-effects.org][effects page]] and the [[file:growth-strategy.org][growth page]] 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.
@@ -69,7 +69,7 @@ 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.
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 [[file:compute-marketplace.org][compute marketplace]] provides the actuarial data; the [[file:agora-contracts.org][attestation marketplace]] provides the reputation layer.
* Summary: Effects and Growth Are the Same Curve