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/evaluation-harness.org
View File

@@ -10,10 +10,8 @@ The accumulated regression suite — thousands of edge cases from every deployed
**Target:** AI labs proving their agents' capabilities, enterprise procurement requiring independent verification.
**Price:** $50K-$200K per certification.
The regression suite grows with every deployment, making the certification increasingly valuable over time. The early player's suite is the largest because they started first.
The regression suite grows with every deployment, making the certification increasingly valuable over time. The early player's suite is the largest because they started first. This is the [[file:collective-regression-suite.org][collective regression suite]] mechanism in action.
10 certifications in year one = $500K-$2M.
Long-term endpoint: this becomes the UL certification for AI — a third-party verification nobody can ignore. [[file:verification-monopoly.org][The verification monopoly]].
See also: [[file:collective-regression-suite.org][Collective regression suite]], [[file:verification-appliance.org][Verification appliance]], [[file:infrastructure-lock-in.org][Infrastructure lock-in]], [[file:moats.org][Moats]]
Long-term endpoint: this becomes the UL certification for AI — a third-party verification nobody can ignore. [[file:verification-monopoly.org][The verification monopoly]]. The certification relies on a [[file:verification-appliance.org][verification appliance]] to run the tests in a trusted environment, creating [[file:infrastructure-lock-in.org][infrastructure lock-in]] as certification history accumulates on the platform. These dynamics form powerful [[file:moats.org][moats]].