gbrain: sync converted org-mode brain files

ideas/triad-systemic-effects.org

@@ -5,7 +5,7 @@
 #+title: Triad — Systemic Effects Over Time
 #+filetags: :passepartout:strategy:effects:geopolitics:society:
 
-The [[file:triad-overview.org][triad (Logos + Stoa + Agora)]] is not a product in an existing category. Verified infrastructure is a new category, and every existing category — cloud, AI, OS, social, payments, compliance, governance — eventually migrates into it because the alternative becomes indefensible.
+The [[file:triad-overview.org][triad (Logos + [[file:stoa.org][Stoa]] + [[file:agora.org][Agora]])]] is not a product in an existing category. Verified infrastructure is a new category, and every existing category — cloud, AI, OS, social, payments, compliance, governance — eventually migrates into it because the alternative becomes indefensible.
 
 Using the [[file:orders-of-magnitude-time.org][orders-of-magnitude framework]], the effects cascade across time scales. Each scale is qualitatively different, not just more of the same.
 
@@ -19,7 +19,7 @@ The effect compounds: proof repositories accumulate lemma libraries across field
 
 ** Economic: the compliance industry's margins erode
 
-The first enterprise that replaces a SOC2 audit with a gate rule saves $500K and two weeks. The Big Four consulting revenue in GRC (governance, risk, compliance) starts eroding — first at the margins (automated control testing), then structurally (the entire audit function).
+The first enterprise that replaces a [[file:compliance/soc2.org][SOC2]] audit with a gate rule saves $500K and two weeks. The Big Four consulting revenue in GRC (governance, risk, compliance) starts eroding — first at the margins (automated control testing), then structurally (the entire audit function).
 
 [[file:domain-gate-packages.org][Gate rule packages]] sell to the same CISO who buys audit prep today. The difference: audit prep is a cost center; gate rules are an investment that compounds.
 
@@ -33,7 +33,7 @@ A regulation that says "access logs must be tamper-proof" is a negotiation. A ga
 
 ** Technological: AI safety becomes engineering, not policy
 
-The verified API gateway (captured in [[file:revenue-hub.org]]) proves that AI safety is a /software engineering problem/, not a policy problem. Companies don't need AI regulation — they need Passepartout gate rules between the LLM and production.
+The verified API gateway ([[file:revenue-hub.org][revenue hub]]) proves that AI safety is a /software engineering problem/, not a policy problem. Companies don't need AI regulation — they need Passepartout gate rules between the LLM and production.
 
 This shifts the entire AI safety discourse. The question stops being "what should we ban?" and becomes "what gates should we verify?" Prompt injection, jailbreaks, data leakage, hallucination in critical paths — all become gate rule specifications, not white papers.
 
@@ -41,7 +41,7 @@ This shifts the entire AI safety discourse. The question stops being "what shoul
 
 /I verified it/ replaces /I trust the auditor/. DIDs make platform-owned identity look like a historical anomaly. The [[file:pds-as-a-service.org][PDS model]] makes surveillance advertising technically impossible without the user's active consent gate.
 
-The social contract around data shifts: companies don't own user data because the architecture literally prevents them from accessing it without a permission gate. The GDPR model (notice + consent) was a regulation trying to fix bad architecture. The PDS model is architecture that makes bad behaviour impossible.
+The social contract around data shifts: companies don't own user data because the architecture literally prevents them from accessing it without a permission gate. The [[file:compliance/gdpr.org][GDPR]] model (notice + consent) was a regulation trying to fix bad architecture. The PDS model is architecture that makes bad behaviour impossible.
 
 ** Cultural: verification earns cachet
 
@@ -53,11 +53,11 @@ The /move fast and break things/ ethos ages overnight. In the C-suite, saying /w
 
 ** Economic: the verification monopoly
 
-If every transaction on Agora, every plugin on Stoa, every gate rule on Logos passes through Passepartout's verification, then the early player collects a tax on the entire verified economy. This is the [[file:verification-monopoly.org]].
+If every transaction on Agora, every plugin on Stoa, every gate rule on Logos passes through Passepartout's verification, then the early player collects a tax on the entire verified economy. This is the [[file:verification-monopoly.org][verification monopoly]].
 
-The $960B TAM (from [[file:triad-index.org]]) is not aspirational — it is the cost of admission to the verified stack. Every dollar spent on cloud, AI, OS, social media, payments, and compliance eventually flows through the verification layer. The early player does not capture 100% of that, but the spread on even 5-10% is venture-scale money.
+The $960B TAM ([[file:triad-index.org][triad index]]) is not aspirational — it is the cost of admission to the verified stack. Every dollar spent on cloud, AI, OS, social media, payments, and compliance eventually flows through the verification layer. The early player does not capture 100% of that, but the spread on even 5-10% is venture-scale money.
 
-The switching cost to unverified infrastructure becomes infinite. No enterprise can justify / why would we go back to unverified code / once verification is in place. This is the [[file:infrastructure-lock-in.org]].
+The switching cost to unverified infrastructure becomes infinite. No enterprise can justify / why would we go back to unverified code / once verification is in place. This is the [[file:infrastructure-lock-in.org][infrastructure lock-in]].
 
 ** Geopolitical: compute becomes a strategic asset
 
@@ -98,7 +98,7 @@ The frontier shifts. The question is no longer /can we verify this/ but /what ne
 
 ** Economic: the old economy becomes a historical layer
 
-Proprietary software licensing, cloud lock-in, compliance consulting, annual audit firms — these are as alien to someone born into the verified era as mainframes and COBOL are to a cloud-native developer. The new economy runs on verified infrastructure where the marginal cost of verification is zero and the switching cost to unverified infrastructure is infinite.
+Proprietary software [[file:licensing.org][licensing]], cloud lock-in, compliance consulting, annual audit firms — these are as alien to someone born into the verified era as mainframes and COBOL are to a cloud-native developer. The new economy runs on verified infrastructure where the marginal cost of verification is zero and the switching cost to unverified infrastructure is infinite.
 
 The insurance industry, which prices based on risk, shifts to pricing based on proof coverage. Companies with full verification pay lower premiums. Companies without it cannot get insured. This is the completion of the feedback loop: verification is not just better engineering — it is a requirement for participation in the formal economy.