Architecture reframe: rename triad/Stoa/Logos/Agora → Passepartout

- Renamed ideas/stoa/ → ideas/passepartout/, all stage files prefixed passepartout-
- Renamed triad-index/overview/systemic-effects → passepartout-* under passepartout/
- Renamed ideas/agora/ → ideas/passepartout-social-protocol/, stripped agora- prefixes
- Merged overview and environment pages into architecture; deleted 3 redundant files
- Renamed growth-strategy → enterprise-growth-strategy
- Renamed alternative-growth-social-first → social-growth-strategy
- Removed all Greek names: Stoa, Logos, Agora as product names
- Updated 50+ files of cross-references to new naming
- Kept org-id UUIDs intact throughout

ideas/collective-regression-suite.org

@@ -7,7 +7,7 @@
 
 The [[id:45258a2d-1675-562c-9024-5d1eb2f1ea56][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 [[id:1d074690-a279-59cb-b91d-e9a22ae104ad][Agora]] as the substrate for distribution and contribution.
+This specification describes how the collective regression suite is built, maintained, and used, with [[id:1d074690-a279-59cb-b91d-e9a22ae104ad][the social protocol]] as the substrate for distribution and contribution.
 
 **Why collective**
 
@@ -39,7 +39,7 @@ Key fields:
 - **expected-outcome** — allow or deny.
 - **gate-rule** — which specific rule this case exercises. Helps identify which rule failed when a test breaks.
 - **rationale** — human-readable explanation of why this outcome is correct. Used when a test needs review after a rule change.
-- **origin** — the contributing instance's Agora DID and a Merkle hash proving the case was actually encountered. This is how reputation is tracked.
+- **origin** — the contributing instance's social protocol DID and a Merkle hash proving the case was actually encountered. This is how reputation is tracked.
 
 **How test cases are generated**
 
@@ -53,9 +53,9 @@ Every day, each instance runs a local triage pass:
 
 The local suite is the seed. Once per week (or on explicit trigger), the instance submits new cases to the collective:
 
-1. Sign each new case with the instance's Agora DID.
-2. Bundle into an Agora Note with domain tag and ontology version.
-3. Publish to the collective regression suite topic on Agora.
+1. Sign each new case with the instance's social protocol DID.
+2. Bundle into a social protocol Note with domain tag and ontology version.
+3. Publish to the collective regression suite topic on the social protocol.
 
 **How the collective suite is organized**
 
@@ -88,7 +88,7 @@ Each .regression file is a compressed, sorted list of test cases. The manifest i
 
 **Who can submit**
 
-Any [[id:28c46769-c14b-42aa-ac7a-69d310157f8f][Passepartout]] instance with an Agora DID can submit test cases. But not all submissions are treated equally. The suite maintains a three-tier system:
+Any [[id:28c46769-c14b-42aa-ac7a-69d310157f8f][Passepartout]] instance with a social protocol DID can submit test cases.
 
 Tier 1 — Verified. Human-reviewed by the suite operator. Used in certification scoring. An instance that passes Tier 1 earns the standard certification badge.
 
@@ -102,7 +102,7 @@ Reputation determines when a submitter graduates to auto-acceptance:
 - An instance with a long history of valid submissions (100+ confirmed, zero malicious) graduates to Tier 2 auto-accept.
 - An instance that submits malicious cases (fake edge cases designed to poison the suite) loses reputation. Three malicious submissions and the instance is banned from contributing permanently.
 
-Reputation is public and tied to the Agora DID. A banned instance can create a new DID, but the new DID starts with no history and all its submissions go to Tier 3 pending review. The cost of a Sybil attack is human review time, which scales poorly for the attacker.
+Reputation is public and tied to the social protocol DID. A banned instance can create a new DID, but the new DID starts with no history and all its submissions go to Tier 3 pending review.
 
 **Certification scoring**
 
@@ -110,7 +110,7 @@ When an instance applies for certification:
 
 1. Download the current regression suite manifest. Verify the Merkle root against the operator's signed certificate.
 2. Run each test case through the instance's gate stack. Record pass/fail per case.
-3. Submit results as a signed Agora Note. The note includes the instance's DID, the suite version tested against, and the per-domain pass rates.
+3. Submit results as a signed social protocol Note. The note includes the instance's DID, the suite version tested against, and the per-domain pass rates.
 
 The certification score is the weighted pass rate across all domains that the instance claims compliance with. A HIPAA-certified instance must pass 99.5%+ of the healthcare-hipaa subtree. A generally-capable agent must pass 95%+ of the foundational subtree.
 
@@ -136,12 +136,12 @@ The collective regression suite operator is a distinct role from the Passepartou
 4. Publishes signed manifests at each release.
 5. Issues certification badges.
 
-This role can be performed by the early player as a revenue-generating service, or by a neutral foundation if the ecosystem grows large enough. The revenue model: certification fees ($50K-$200K per enterprise per year). The operator does not gate access to the suite itself — the suite is available to all Agora participants because a larger suite makes the ecosystem more valuable. The operator charges for the badge, not the data.
+This role can be performed by the early player as a revenue-generating service, or by a neutral foundation if the ecosystem grows large enough. The revenue model: certification fees ($50K-$200K per enterprise per year). The operator does not gate access to the suite itself — the suite is available to all social protocol participants because a larger suite makes the ecosystem more valuable.
 
 **Summary of the loop**
 
 Instance runs → human corrects a gate decision → new test case is abstracted and added to the local suite → periodically submitted to the collective suite → de-duplicated and verified → published in the next manifest → every other instance downloads it → future instances must pass it to earn certification → the collective suite grows → the certification becomes harder to fake → the ecosystem becomes more valuable → more instances join → more edge cases discovered.
 
-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.
+Every component of this loop exists or is on Passepartout's roadmap except the social protocol Note publishing channel.
 
-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 [[id:13e6ae54-2d24-5aa0-b1cd-a7e8e749aa70][the self-driving Lisp Machine]]. The suite itself is the [[id:2f783eb4-638e-5afa-9b59-6224d086a712][infrastructure lock-in]] — once an enterprise has certified against it, switching to a competitor means rebuilding their compliance from scratch.
+Nothing in this loop requires new core Passepartout functionality. It requires the social protocol for inter-instance communication and a server-side aggregation process.