Promote entire passepartout-economics/ to ideas/ root
All 31 files from ideas/passepartout-economics/ promoted to ideas/ root. - Subfolder's passepartout-economics.org (42-line index) renamed to triad-index.org to avoid collision with root-level full doc - index.org removed (redundant — triad-index.org replaces it) - Root-level passepartout-economics.org: stripped file:passepartout-economics/ prefix from all cross-references (now simple file:foo.org links) - compliance-framework-mapping.org: same prefix cleanup - All internal file: links within the economics docs already used simple names (no prefix) — they resolve correctly from ideas/ root
This commit is contained in:
16
ideas/infrastructure-lock-in.org
Normal file
16
ideas/infrastructure-lock-in.org
Normal file
@@ -0,0 +1,16 @@
|
||||
:PROPERTIES:
|
||||
:ID: 2f783eb4-638e-5afa-9b59-6224d086a712
|
||||
:END:
|
||||
#+title: Infrastructure Lock-In and Switching Costs
|
||||
#+filetags: :passepartout:economics:moats:lock-in:switching:
|
||||
|
||||
A hospital that runs Passepartout with HIPAA gate rules ($50K/yr) for five years has accumulated:
|
||||
|
||||
- A fact store with a decade of compliance decisions
|
||||
- A proof forest of verified rules
|
||||
- An empirical decision history tied to their specific deployment
|
||||
- Customized gate rules encoding their specific workflows and approvals
|
||||
|
||||
Switching to a competitor means discarding all of it. The accumulated value grows as the fact store deepens. Annual revenue per enterprise grows from $250K in year one to $500K-$1M by year five as more [[file:domain-gate-packages.org][domain packages]] are added.
|
||||
|
||||
This is the strongest residual [[file:moats.org][moat]]. The [[file:evaluation-harness.org][evaluation harness]] (regression suite) is a close second — it grows with every deployment and cannot be ingested from public data. The [[file:verification-monopoly.org][verification monopoly]] and [[file:upgrade-lifecycle.org][upgrade lifecycle]] compound this lock-in: every new regulation encoded as a gate rule deepens the proof forest, making the deployment harder to reproduce elsewhere.
|
||||
Reference in New Issue
Block a user