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

14
ideas/passepartout-economics/collective-regression-suite.org
View File

@@ -4,7 +4,7 @@
#+title: Collective Regression Suite — Specification
#+filetags: :passepartout:evaluation:regression:suite:collective:
The evaluation harness is not a static test suite written once. It is a living artifact that grows with every deployed instance. Every gate decision that a human corrects becomes a test case. Every bug fix adds an edge case. Every regulatory update adds a rule that must be checked.
The [[file:evaluation-harness.org][evaluation harness]] is not a static test suite written once. It is a living artifact that grows with every deployed instance. Every gate decision that a human corrects becomes a test case. Every bug fix adds an edge case. Every regulatory update adds a rule that must be checked.
This specification describes how the collective regression suite is built, maintained, and used, with Agora as the substrate for distribution and contribution.
@@ -12,7 +12,7 @@ This specification describes how the collective regression suite is built, maint
A single instance learns from its own mistakes. The collective learns from every instance's mistakes. A HIPAA deployment in one hospital discovers an edge case that a SOC2 deployment in a SaaS company would never encounter on its own — but if that SaaS company ever expands into healthcare, their gate stack must handle that edge case. The collective suite gives them hundreds of thousands of edge cases they did not pay to discover.
This is the mechanism behind the verification monopoly claim. A certification means "your gate stack is verified against every edge case ever discovered by any instance in the ecosystem." A competitor starting from scratch cannot buy or scrape this knowledge.
This is the mechanism behind the [[file:verification-monopoly.org][verification monopoly claim]]. A certification means "your gate stack is verified against every edge case ever discovered by any instance in the ecosystem." A competitor starting from scratch cannot buy or scrape this knowledge.
**What a test case is**
@@ -123,7 +123,7 @@ Assume each deployed instance generates on average one new unique test case per
- Year 2: ~50,000 cases (1,000 instances x 50 weeks x 1 case/week)
- Year 3: ~500,000 cases (10,000 instances x 50 weeks x 1 case/week)
At year 3, a new instance that runs the suite captures half a million edge cases from real deployments at zero marginal cost. The operator charges $50K-$200K for the certification. The insurmountability is not technical — a well-funded competitor could reproduce some of these cases through synthetic generation. The insurmountability is provenance: these cases are labeled by real human corrections from real deployments. A synthetic case is a best guess. The collective suite's cases are ground truth.
At year 3, a new instance that runs the suite captures half a million edge cases from real deployments at zero marginal cost. The operator charges $50K-$200K for the certification. The insurmountability is not technical — a well-funded competitor could reproduce some of these cases through synthetic generation. The insurmountability is provenance: these cases are labeled by real human corrections from real deployments. A synthetic case is a best guess. The collective suite's cases are ground truth. This creates powerful [[file:moats.org][moats]] — the data network effect is inherently accumulated over time and cannot be bought.
**The operator's role**
@@ -143,10 +143,4 @@ Instance runs → human corrects a gate decision → new test case is abstracted
Every component of this loop exists or is on Passepartout's roadmap except the Agora Note publishing channel. The gate stack generates the raw signal. The abstraction pass strips instance details. The local triage de-duplicates. The Agora DID provides authentication. The Merkle root provides integrity. The certification badge provides monetization.
Nothing in this loop requires new core Passepartout functionality. It requires the Agora protocol for inter-instance communication and a server-side aggregation process. Both are roadmap items, but neither depends on the self-driving Lisp Machine.
See also:
[[file:evaluation-harness.org][Evaluation harness certification service]]
[[file:verification-monopoly.org][Verification monopoly — the big money]]
[[file:infrastructure-lock-in.org][Infrastructure lock-in]]
[[file:moats.org][Moats]]
Nothing in this loop requires new core Passepartout functionality. It requires the Agora protocol for inter-instance communication and a server-side aggregation process. Both are roadmap items, but neither depends on the self-driving Lisp Machine. The suite itself is the [[file:infrastructure-lock-in.org][infrastructure lock-in]] — once an enterprise has certified against it, switching to a competitor means rebuilding their compliance from scratch.