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

gbrain: sync converted org-mode brain files

Browse Source
This commit is contained in:
Hermes
2026-05-24 03:00:35 +00:00
parent b3d91f2e55
commit 94f1871177
67 changed files with 4307 additions and 152 deletions
Download Patch File Download Diff File Expand all files Collapse all files

4
ideas/collective-regression-suite.org
View File

@@ -6,11 +6,11 @@
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.
This specification describes how the collective regression suite is built, maintained, and used, with [[file:agora.org][Agora]] as the substrate for distribution and contribution.
**Why collective**
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.
A single instance learns from its own mistakes. The collective learns from every instance's mistakes. A [[file:compliance/hipaa.org][HIPAA]] deployment in one hospital discovers an edge case that a [[file:compliance/soc2.org][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 [[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.