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

Normalize all passepartout-economics to inline wiki links

Browse Source 
Replaced every bottom-of-section 'See also:' block with inline
Org-mode file: links at the first natural mention in body text.
All 29 files across the economics directory now use wiki-style
inline cross-references rather than standalone reference blocks.
This commit is contained in:
Hermes
2026-05-23 05:58:18 +00:00
parent 5a2fce162a
commit 3063f8fdf7
28 changed files with 56 additions and 123 deletions
Download Patch File Download Diff File Expand all files Collapse all files

6
ideas/passepartout-economics/infrastructure-lock-in.org
View File

@@ -11,8 +11,6 @@ A hospital that runs Passepartout with HIPAA gate rules ($50K/yr) for five years
- 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 domain packages are added.
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 moat. The evaluation harness (regression suite) is a close second — it grows with every deployment and cannot be ingested from public data.
See also: [[file:evaluation-harness.org][Evaluation harness]], [[file:verification-monopoly.org][Verification monopoly]], [[file:moats.org][Moats]], [[file:upgrade-lifecycle.org][Upgrade lifecycle]], [[file:domain-gate-packages.org][Domain gate packages]]
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.