ideas: editorial sweep — atomization, interlinking, restructuring

- Split competitive-analysis-2026-05.org → TOC + 9 competitor files in
  ideas/competitors/. Dropped date from filename. All competitor UUIDs
  generated, TOC keeps original UUID for backlink continuity.
- Deleted passepartout-economics.org archive (replaced by 27-node KB).
- Inlined 5 'See also' blocks into natural prose (compliance-index,
  first-mover-window, revenue-table, orders-of-magnitude-time,
  native-org-knowledge-base).
- Linked 7 orphan compliance pages back to compliance index + finished
  truncated sentences.
- Linked all 14 Agora requirement docs from topic-relevant pages
  (identity→lisp-machine-security, infrastructure→compute-marketplace,
  social-space→growth-strategy, exchange→agora-contracts, etc.).
- Linked ai-industry-impact from investment-thesis, sufficiency-flip,
  verification-appliance, effects-growth-flywheel (up from 1 to 10+ pages).
- Fixed CREATED timestamps to use git commit dates instead of today.
- Made all links absolute from root (no port inheritance).
- Removed stale agora/docs/ duplicate content.

ideas/effects-growth-flywheel.org

@@ -1,11 +1,12 @@
 :PROPERTIES:
+:ID:       528a0f6c-6fd6-41ed-9d59-237958bdaef2
 :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 [[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 [[id:b9fa4b7b-bc61-4d7f-918d-ff687b80f2ba][effects page]] and the [[id:d28adac8-08a1-40c4-ae43-b5d8d7b1743f][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.
 
@@ -27,7 +28,7 @@ At every scale, the effect /is/ the growth mechanism. There is no waiting for ef
 
 | 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 | /Scientific reproducibility:/ the first verified paper | Universities buy [[id:28c46769-c14b-42aa-ac7a-69d310157f8f][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 |
 
@@ -39,7 +40,7 @@ Key observation: the verified API gateway decouples the effect from triad adopti
 |-------+-------------------+------------------------|
 | 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 [[file:collective-regression-suite.org][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 |
+| 2K–10K | /Proof library compounding:/ the [[id:a5d59d12-b23e-58d6-a81b-9b8b06556949][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.
 
@@ -58,7 +59,7 @@ Key observation: the shift from enterprise adoption to consumer adoption is cult
 | 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 |
+| 10M–100M | /[[id:827bc546-e887-5b7c-9b65-6392beaf0920][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).
@@ -69,7 +70,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 [[file:compute-marketplace.org][compute marketplace]] provides the actuarial data; the [[file:agora-contracts.org][attestation marketplace]] 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 [[id:3c6b0449-a8fb-5b89-b82a-34efb21ef5b5][compute marketplace]] provides the actuarial data; the [[id:64708e1f-00e9-4cb7-b44b-ea0b98e5296d][attestation marketplace]] provides the reputation layer.
 
 * Summary: Effects and Growth Are the Same Curve
 
@@ -81,14 +82,14 @@ The flywheel has two critical bottlenecks:
 | 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.
+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. [[id:827bc546-e887-5b7c-9b65-6392beaf0920][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]]
+- [[id:b9fa4b7b-bc61-4d7f-918d-ff687b80f2ba][Systemic effects over time]]
+- [[id:d28adac8-08a1-40c4-ae43-b5d8d7b1743f][Growth phases — zero to billions]]
+- [[id:dc2e4f22-1c4c-5d4a-a151-f96e5d3b0d70][Development timeline]]
+- [[id:ed05cab4-88e9-4e25-b7c9-346fa39c69a0][Revenue per phase]]
+- [[id:3c6b0449-a8fb-5b89-b82a-34efb21ef5b5][Compute marketplace]]
+- [[id:64708e1f-00e9-4cb7-b44b-ea0b98e5296d][Attestation and insurance]]
+- [[id:827bc546-e887-5b7c-9b65-6392beaf0920][Verification monopoly]]