From 2578bfee611a54ceec43e31a40e7b75bb7665acf Mon Sep 17 00:00:00 2001 From: Hermes Date: Sun, 24 May 2026 18:02:36 +0000 Subject: [PATCH] =?UTF-8?q?Architecture=20reframe:=20rename=20triad/Stoa/L?= =?UTF-8?q?ogos/Agora=20=E2=86=92=20Passepartout?= MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit - 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 --- _index.org | 16 +- ideas/asset-protection-structures.org | 40 ++-- ideas/collective-regression-suite.org | 22 +- ideas/common-logic-iso-24707.org | 8 +- ideas/competitive-analysis.org | 8 +- ideas/competitive-landscape-agora.org | 221 ------------------ ideas/compliance/compliance-index.org | 2 +- ideas/compliance/fedramp.org | 4 +- ideas/compliance/gdpr.org | 2 +- ideas/compliance/hipaa.org | 2 +- ideas/compliance/soc2.org | 2 +- ideas/compute-marketplace.org | 12 +- ideas/domain-gate-packages.org | 2 +- ideas/effects-growth-flywheel.org | 8 +- ...egy.org => enterprise-growth-strategy.org} | 94 ++++---- ideas/infrastructure-lock-in.org | 2 +- ideas/investment-thesis.org | 4 +- ideas/legal-structure-alternatives.org | 10 +- ideas/legal-structure-practical-setup.org | 6 +- ideas/lisp-machine-security.org | 2 +- ...-social-protocol-competitive-landscape.org | 221 ++++++++++++++++++ ...assepartout-social-protocol-contracts.org} | 32 +-- ...artout-social-protocol-entry-strategy.org} | 32 +-- ...assepartout-social-protocol-usernames.org} | 4 +- ...a.org => passepartout-social-protocol.org} | 10 +- .../requirements-00-readme.org} | 6 +- .../requirements-01-overview.org} | 112 ++++----- .../requirements-02-identity.org} | 62 ++--- .../requirements-03-infrastructure.org} | 60 ++--- .../requirements-04-the-primitive.org} | 28 +-- .../requirements-05-social.org} | 34 +-- ...equirements-06-exchange-and-contracts.org} | 30 +-- .../requirements-07-advanced-integration.org} | 14 +- .../requirements-08-library.org} | 16 +- .../requirements-09-implementation.org} | 28 +-- ...requirements-10-governance-and-assets.org} | 14 +- .../requirements-10-user-journey.org} | 6 +- .../requirements-11-assessment.org} | 16 +- ideas/passepartout/_index.org | 30 +++ .../passepartout-architecture.org | 55 +++++ .../passepartout-stage-0-now.org} | 6 +- .../passepartout-stage-1-social-protocol.org} | 28 +-- .../passepartout-stage-2-verification.org} | 20 +- .../passepartout-stage-3-lisp-machine.org} | 30 +-- .../passepartout-stage-4-inference.org} | 10 +- .../passepartout-stage-5-weights.org} | 4 +- .../passepartout-stage-6-training.org} | 8 +- .../passepartout-stage-7-remaining.org} | 20 +- .../passepartout-systemic-effects.org} | 39 ++-- ideas/pds-as-a-service.org | 6 +- ideas/revenue-hub.org | 107 +++++---- ideas/self-driving-lisp-machine.org | 2 +- ...l-first.org => social-growth-strategy.org} | 66 +++--- ideas/stoa-overview.org | 18 -- ideas/stoa/_index.org | 28 --- ideas/stoa/stoa-vision-roadmap.org | 44 ---- ideas/time-estimates.org | 8 +- ideas/triad-index.org | 45 ---- ideas/triad-overview.org | 16 -- ideas/verification-appliance.org | 2 +- ideas/verification-monopoly.org | 2 +- 61 files changed, 859 insertions(+), 927 deletions(-) delete mode 100644 ideas/competitive-landscape-agora.org rename ideas/{growth-strategy.org => enterprise-growth-strategy.org} (57%) create mode 100644 ideas/passepartout-social-protocol-competitive-landscape.org rename ideas/{agora-contracts.org => passepartout-social-protocol-contracts.org} (67%) rename ideas/{agora-entry-strategy.org => passepartout-social-protocol-entry-strategy.org} (81%) rename ideas/{agora-usernames.org => passepartout-social-protocol-usernames.org} (90%) rename ideas/{agora.org => passepartout-social-protocol.org} (74%) rename ideas/{agora/agora-requirements-00-readme.org => passepartout-social-protocol/requirements-00-readme.org} (80%) rename ideas/{agora/agora-requirements-01-overview.org => passepartout-social-protocol/requirements-01-overview.org} (69%) rename ideas/{agora/agora-requirements-02-identity.org => passepartout-social-protocol/requirements-02-identity.org} (86%) rename ideas/{agora/agora-requirements-03-infrastructure.org => passepartout-social-protocol/requirements-03-infrastructure.org} (88%) rename ideas/{agora/agora-requirements-04-the-primitive.org => passepartout-social-protocol/requirements-04-the-primitive.org} (88%) rename ideas/{agora/agora-requirements-05-social.org => passepartout-social-protocol/requirements-05-social.org} (76%) rename ideas/{agora/agora-requirements-06-exchange-and-contracts.org => passepartout-social-protocol/requirements-06-exchange-and-contracts.org} (86%) rename ideas/{agora/agora-requirements-07-advanced-integration.org => passepartout-social-protocol/requirements-07-advanced-integration.org} (97%) rename ideas/{agora/agora-requirements-08-library.org => passepartout-social-protocol/requirements-08-library.org} (88%) rename ideas/{agora/agora-requirements-09-implementation.org => passepartout-social-protocol/requirements-09-implementation.org} (92%) rename ideas/{agora/agora-requirements-10-governance-and-assets.org => passepartout-social-protocol/requirements-10-governance-and-assets.org} (82%) rename ideas/{agora/agora-requirements-10-user-journey.org => passepartout-social-protocol/requirements-10-user-journey.org} (90%) rename ideas/{agora/agora-requirements-11-assessment.org => passepartout-social-protocol/requirements-11-assessment.org} (73%) create mode 100644 ideas/passepartout/_index.org create mode 100644 ideas/passepartout/passepartout-architecture.org rename ideas/{stoa/stoa-stage-0-now.org => passepartout/passepartout-stage-0-now.org} (91%) rename ideas/{stoa/stoa-stage-1-agora.org => passepartout/passepartout-stage-1-social-protocol.org} (76%) rename ideas/{stoa/stoa-stage-2-logos.org => passepartout/passepartout-stage-2-verification.org} (83%) rename ideas/{stoa/stoa-stage-3-stoa.org => passepartout/passepartout-stage-3-lisp-machine.org} (83%) rename ideas/{stoa/stoa-stage-4-inference.org => passepartout/passepartout-stage-4-inference.org} (88%) rename ideas/{stoa/stoa-stage-5-weights.org => passepartout/passepartout-stage-5-weights.org} (97%) rename ideas/{stoa/stoa-stage-6-training.org => passepartout/passepartout-stage-6-training.org} (95%) rename ideas/{stoa/stoa-stage-7-remaining.org => passepartout/passepartout-stage-7-remaining.org} (94%) rename ideas/{triad-systemic-effects.org => passepartout/passepartout-systemic-effects.org} (63%) rename ideas/{alternative-growth-social-first.org => social-growth-strategy.org} (58%) delete mode 100644 ideas/stoa-overview.org delete mode 100644 ideas/stoa/_index.org delete mode 100644 ideas/stoa/stoa-vision-roadmap.org delete mode 100644 ideas/triad-index.org delete mode 100644 ideas/triad-overview.org diff --git a/_index.org b/_index.org index 9f2c6f9..6941fee 100644 --- a/_index.org +++ b/_index.org @@ -2,24 +2,24 @@ :CREATED: [2026-05-24 Sun] :ID: 284f5c7a-1d2b-4e3f-8c6d-9a0b1c2d3e4f :END: -#+title: Brain +#+title: Passepartout — A Verifiable Personal Intelligence #+filetags: :index:navigation: -This is the knowledge base for the [[id:d71df46b-9012-433c-86ce-ec21b78eac5f][triad]] — [[id:42c86e6f-4f27-4993-8238-b7bc7d15fb7b][Stoa (Verified Lisp Machine)]], [[id:1d074690-a279-59cb-b91d-e9a22ae104ad][Agora (Decentralized Protocol)]], and the interconnected concepts around them. +Passepartout is a self-bootstrapping, verified neurosymbolic Lisp machine that speaks the Passepartout Social Protocol. One project, one source tree, one image — from the Python prototype on Gitea to the Lisp verification appliance on custom silicon. -Start with the [[id:4a1f23b0-abc1-4def-9876-543210abcdef][Stoa staged roadmap]] if you are new here: it walks from conventional computing through each stage of verified infrastructure, ending at what remains. +Start with the [[id:4a1f23b0-abc1-4def-9876-543210abcdef][staged roadmap]] which walks from conventional computing through each capability layer of Passepartout, ending at what remains. **Sections:** -- [[id:42c86e6f-4f27-4993-8238-b7bc7d15fb7b][Stoa — Verified Lisp Machine]] — the staged roadmap from conventional computing through verified [[id:84a537b4-4256-50c8-91f5-dd5b4538418f][hardware]], with cost-benefit per stage -- [[id:1d074690-a279-59cb-b91d-e9a22ae104ad][Agora — Decentralized Social Protocol]] — identity, communication, contracts, governance -- [[id:329a30cd-55fb-496d-a60b-91388c211bba][Ideas]] — all concept pages and analysis +- [[id:1c3ec48b-446c-50d2-b53e-126a81f5143f][Architecture — Passepartout overview]] — the three subsystems (verification, environment, protocol) and how they compose +- [[id:1d074690-a279-59cb-b91d-e9a22ae104ad][Passepartout Social Protocol]] — identity, communication, contracts, governance (the protocol Passepartout implements) +- [[id:329a30cd-55fb-496d-a60b-91388c211bba][Ideas]] — all concept pages and analysis across themes **Core concept pages:** - [[id:84a537b4-4256-50c8-91f5-dd5b4538418f][Verification Appliance]] — what a verified Lisp image means, the ACL2 bootstrap -- [[id:13e6ae54-2d24-5aa0-b1cd-a7e8e749aa70][Self-Driving Lisp Machine]] — where [[id:e01b9199-2cba-4ac2-824b-ba1b033cc23e][Passepartout]], Stoa, and Logos converge +- [[id:13e6ae54-2d24-5aa0-b1cd-a7e8e749aa70][Self-Driving Lisp Machine]] — the convergence of all Passepartout subsystems on custom hardware - [[id:1c95ce7d-a2db-506a-9608-df68f9ae211b][Lisp Machine Security]] — Merkle memory, gate stack, structural proofs - [[id:c34940cc-090e-57c4-8020-e78b1d32b96c][Domain Gate Packages]] — capability authorization, the Dispatcher - [[id:45ea493b-94ad-5885-aa65-0c846e5c3c1d][Gate Rule Encoding]] — how policies are encoded and enforced -- [[id:1c3ec48b-446c-50d2-b53e-126a81f5143f][Triad Index]] — Logos, Stoa, Agora as a system +- [[id:4a1f23b0-abc1-4def-9876-543210abcdef][Passepartout staged roadmap]] — the progressive build-out from Stage 0 to Stage 7 diff --git a/ideas/asset-protection-structures.org b/ideas/asset-protection-structures.org index 2806d0c..93a9ad1 100644 --- a/ideas/asset-protection-structures.org +++ b/ideas/asset-protection-structures.org @@ -10,11 +10,11 @@ Research on corporate structures for a US-incorporated tech company with offshor * The Assets to Protect -The triad has three distinct asset classes, each with different protection needs: +Passepartout has three distinct asset classes, each with different protection needs: -1. /IP (Logos):/ [[id:28c46769-c14b-42aa-ac7a-69d310157f8f][Passepartout]] codebase, gate rules, ACL2 proof libraries, the [[id:827bc546-e887-5b7c-9b65-6392beaf0920][verification monopoly]]. This is the core defensible IP. Needs to be owned separately from the operating company so that if the operating company is sued, the IP is not reachable. +1. /IP (verification subsystem):/ [[id:28c46769-c14b-42aa-ac7a-69d310157f8f][Passepartout]] codebase, gate rules, ACL2 proof libraries, the [[id:827bc546-e887-5b7c-9b65-6392beaf0920][verification monopoly]]. This is the core defensible IP. Needs to be owned separately from the operating company so that if the operating company is sued, the IP is not reachable. -2. /Platform ([[id:1d074690-a279-59cb-b91d-e9a22ae104ad][Agora]]):/ The network itself — user base, reputation graph, contract history, protocol specification. This is harder to value and harder to protect because its value is partly in the user base. But the code, protocol spec, and network infrastructure can be owned separately. +2. /Platform ([[id:1d074690-a279-59cb-b91d-e9a22ae104ad][the social protocol]]):/ The network itself — user base, reputation graph, contract history, protocol specification. 3. /[[id:ed05cab4-88e9-4e25-b7c9-346fa39c69a0][Revenue streams]]:/ Enterprise compliance contracts, transaction fees, PDS hosting subscriptions. These flow through the operating company. A judgment against the operating company attaches to the revenue in that entity. @@ -33,8 +33,8 @@ Assessment: Fine for Phase 0. Upgrade when revenue exceeds liability risk tolera ** Structure B: Delaware C-Corp + Offshore IP Holding Company -- Delaware C-Corp is the operating company (sells verification, runs the Agora PDS infrastructure) -- A separate IP holding company in BVI, Cayman, or Nevis owns the Passepartout code, gate rules, ACL2 libraries, and the Agora protocol spec +- Delaware C-Corp is the operating company (sells verification, runs the social protocol PDS infrastructure) +- A separate IP holding company in BVI, Cayman, or Nevis owns the Passepartout code, gate rules, ACL2 libraries, and the social protocol spec - The operating company licenses the IP from the holding company at arm's-length royalty rates - The holding company accumulates IP [[id:67faf52f-9126-50a7-b87e-2bedc610dac7][licensing]] revenue in the offshore jurisdiction @@ -53,11 +53,11 @@ Cons: Complex, expensive to set up and maintain. Many investors are uncomfortabl ** Structure D: Delaware C-Corp + Delaware LLC Series + Offshore - Delaware C-Corp as parent -- Each business line (Logos verification, Agora network, [[id:3c6b0449-a8fb-5b89-b82a-34efb21ef5b5][compute marketplace]], PDS hosting) is a separate Delaware series LLC +- Each business line (verification, social protocol network, [[id:3c6b0449-a8fb-5b89-b82a-34efb21ef5b5][compute marketplace]], PDS hosting) is a separate Delaware series LLC - IP held in an offshore company, licensed to each series LLC - Series LLCs protect assets within each series from liabilities arising in other series -Pros: Good liability separation between business lines. If the social network (Agora) generates liability, the verification business (Logos) assets are in a separate series. Each series can be spun out independently. +Pros: Good liability separation between business lines. If the social network (the social protocol) generates liability, the verification business assets are in a separate series. Cons: Series LLC is legally untested in many jurisdictions. Some states don't recognize them. Tax complexity. * Key Considerations for This Specific Venture @@ -66,13 +66,13 @@ Cons: Series LLC is legally untested in many jurisdictions. Some states don't re [[id:827bc546-e887-5b7c-9b65-6392beaf0920][The verification monopoly]] /is/ the moat. The ACL2 proof libraries, gate rule library, and regression suite are accumulated over years and cannot be recreated quickly. These must be owned by a separate entity from the operating company. If the operating company is sued, the IP survives. -** The Agora network is harder to protect** +** The social protocol network is harder to protect** -The Agora's value is partly in its decentralized architecture (no central entity controls the network) and partly in the code that runs the PDS infrastructure and protocol. The AGPL license means anyone can run the code — the network value is in the user base, not the software. This is a structural asset protection advantage: even if the operating company fails, the network continues. +The social protocol's value is partly in its decentralized architecture (no central entity controls the network) and partly in the code that runs the PDS infrastructure and protocol. The AGPL license means anyone can run the code — the network value is in the user base, not the software. This is a structural asset protection advantage: even if the operating company fails, the network continues. ** Revenue splits suggest separate entities** -Enterprise compliance revenue ($2-12M/year) is high-margin, low-volume, and comes from a small number of customers. Agora transaction fees (0.5-2%) are low-margin, high-volume, and come from millions of users. Mixing these in the same entity creates regulatory complexity — compliance contracts have different liability profiles than payment processing. +Enterprise compliance revenue ($2-12M/year) is high-margin, low-volume, and comes from a small number of customers. Social protocol transaction fees (0.5-2%) are low-margin, high-volume, and come from millions of users. ** Jurisdiction for the IP company** @@ -98,20 +98,20 @@ Action items for Phase 0: ** Phase 1: Separate IP + OpCo (before significant revenue) -Before enterprise compliance revenue exceeds $5M cumulative or Agora users exceed 10K, establish the IP holding company structure. The IP must be /out/ of the operating company before a significant lawsuit is plausible. +Before enterprise compliance revenue exceeds $5M cumulative or social protocol users exceed 10K, establish the IP holding company structure. Structure: Delaware C-Corp (OpCo) + BVI IP Co - OpCo licenses verification IP from BVI Co -- OpCo licenses Agora protocol IP from BVI Co +- OpCo licenses social protocol IP from BVI Co - Founders own both entities (same cap table or mirror ownership) Timing: The IP transfer is a taxable event if the IP has appreciated. Transfer early, when the IP has minimal appraised value (before the verification monopoly exists), to avoid a tax hit. -** Phase 2: Series Separation (when Agora has significant users or revenue) +** Phase 2: Series Separation (when the social protocol has significant users or revenue) -If the Agora has 100K+ users and payment volume, separate the business lines into different entities under the same parent: -- Logos LLC (verification, enterprise compliance) -- Agora LLC (social network, transactions, PDS hosting) +If the social protocol has 100K+ users and payment volume, separate the business lines into different entities under the same parent: +- Verification LLC (verification, enterprise compliance) +- Social Protocol LLC (social network, transactions, PDS hosting) - Compute LLC (marketplace operations) - BVI IP Co (owns all IP, licenses to all three) @@ -121,11 +121,11 @@ When the cumulative value justifies the cost and complexity: move the BVI IP Co * What This Means for the [[id:d28adac8-08a1-40c4-ae43-b5d8d7b1743f][Growth Strategy]] -The institution-first path (enterprise compliance) and the social-first path (Agora communities) have /different liability profiles/ that push toward different structures: +The institution-first path (enterprise compliance) and the social-first path (social protocol communities) have /different liability profiles/ that push toward different structures: -Enterprise compliance: Higher liability per contract. A single compliance engagement gone wrong could be a $1M+ claim. The IP separation in Phase 1 is /more urgent/ for the Logos revenue stream. +Enterprise compliance: Higher liability per contract. A single compliance engagement gone wrong could be a $1M+ claim. The IP separation in Phase 1 is /more urgent/ for the verification revenue stream. -Agora network: Lower liability per user but higher aggregate surface. Payment processing regulations, content liability, data protection. The series LLC separation becomes relevant when users cross 10K. +Social protocol network: Lower liability per user but higher aggregate surface. Payment processing regulations, content liability, data protection. The combined strategy (both engines) makes the Phase 1 structure (Delaware OpCo + BVI IP Co) more important rather than less — the diversification of revenue streams also diversifies liability sources, and the IP needs to be protected from /both/. @@ -134,6 +134,6 @@ The combined strategy (both engines) makes the Phase 1 structure (Delaware OpCo This is preliminary research. Specific recommendations require a US corporate lawyer (incorporation), an international tax lawyer (offshore structure), and an asset protection specialist (trust/AP structure). The right order: incorporate in Delaware when ready, then hire a lawyer to plan the offshore structure before significant revenue or users accumulate. - [[id:d28adac8-08a1-40c4-ae43-b5d8d7b1743f][Combined growth strategy]] -- [[id:1bc22b89-d3eb-4f6d-bcfc-2b0c19c8ed8f][Agora competitive landscape]] +- [[id:1bc22b89-d3eb-4f6d-bcfc-2b0c19c8ed8f][Social protocol competitive landscape]] - [[id:8c7b9812-f8d6-4347-8915-ce8e520b7914][Entry strategy — organized communities]] - [[id:98364e9d-a8a9-42b7-a9dc-b643fd2ccc4b][Outbound sales compliance framework]] diff --git a/ideas/collective-regression-suite.org b/ideas/collective-regression-suite.org index 01ee441..af14b2e 100644 --- a/ideas/collective-regression-suite.org +++ b/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. diff --git a/ideas/common-logic-iso-24707.org b/ideas/common-logic-iso-24707.org index 3da6bf6..95ac6f0 100644 --- a/ideas/common-logic-iso-24707.org +++ b/ideas/common-logic-iso-24707.org @@ -11,7 +11,7 @@ Three standard dialects: CLIF (Common Logic Interchange Format), CGIF (Conceptua **Relevance to [[id:28c46769-c14b-42aa-ac7a-69d310157f8f][Passepartout]]** -The fact store interchange format. Passepartout's fact store uses plists internally — fast, native to Lisp, zero serialization cost. But between instances ([[id:1d074690-a279-59cb-b91d-e9a22ae104ad][Agora]] sync, backup/restore, export), a standardized format is needed. CLIF is a strong candidate because its first-order logic is a direct match for the [[id:45ea493b-94ad-5885-aa65-0c846e5c3c1d][gate rules]] ACL2 verifies. A CLIF-to-ACL2 translator is mechanically straightforward — both operate on first-order formulas. +The fact store interchange format. Passepartout's fact store uses plists internally — fast, native to Lisp, zero serialization cost. But between instances ([[id:1d074690-a279-59cb-b91d-e9a22ae104ad][social protocol]] sync, backup/restore, export), a standardized format is needed. CLIF is a strong candidate because its first-order logic is a direct match for the [[id:45ea493b-94ad-5885-aa65-0c846e5c3c1d][gate rules]] ACL2 verifies. A CLIF-to-ACL2 translator is mechanically straightforward — both operate on first-order formulas. The dialect architecture mirrors Passepartout. CL's defining insight: define abstract semantics, let any concrete syntax map to it, get interoperability for free. This is the exact same pattern as Passepartout's "one gate stack, many skills" — the gate stack defines the security ontology (abstract semantics), and skills (dialects) map their operations to it. CL's approach validates Passepartout's design choice and provides a theoretical framework for it. @@ -25,7 +25,7 @@ Multiple implementations exist. There are CL reference implementations (some in Not a replacement for ACL2. CL is a knowledge representation standard, not a theorem prover. ACL2 proves theorems about gate rules. CLIF encodes the gate rules themselves. They are complementary: ACL2 verifies CLIF-encoded rule sets. -Not the internal representation. CLIF is verbose and not optimized for in-process use. The fact store should stay as plists internally. CL is the serialization layer — on the wire between Agora instances, in export files, in backup archives. This is the same pattern as JSON for web APIs: internal data structures are whatever is fastest, JSON is the interchange format. +Not the internal representation. CLIF is verbose and not optimized for in-process use. The fact store should stay as plists internally. CL is the serialization layer — on the wire between social protocol instances, in export files, in backup archives. This is the same pattern as JSON for web APIs: internal data structures are whatever is fastest, JSON is the interchange format. Not a dialect to implement. Passepartout should not implement a full CLIF parser. The right approach is a thin translation layer: export plist → CLIF, import CLIF → ACL2-verified → plist. The AC Lisp ecosystem likely has CLIF libraries that can be wrapped. @@ -38,10 +38,10 @@ CL's treatment of higher-order features is instructive: it extends first-order s **Verdict** Common Logic is relevant not as something to implement or replace, but as: -1. A natural serialization format for the fact store (Agora Notes, inter-instance sync) +1. A natural serialization format for the fact store (social protocol Notes, inter-instance sync) 2. An enterprise procurement checkbox (ISO standard) 3. A theoretical validation of Passepartout's dialect-based architecture 4. A bridge to RDF/OWL data sources 5. A cautionary example for the CIC prover design (careful about higher-order scope) -The right time to integrate it: when Agora Notes need a standard knowledge interchange format for inter-instance communication. Before that, it is a reference worth reading but not implementing. The CL approach informs the [[id:efc76898-03f7-57ba-923d-35d65da88bb7][sufficiency flip]] strategy and the [[id:0b5a8a74-cfd6-542d-bc88-4eb3cd8626f9][cost structure]] of encoding domain knowledge. +The right time to integrate it: when social protocol Notes need a standard knowledge interchange format for inter-instance communication. Before that, it is a reference worth reading but not implementing. The CL approach informs the [[id:efc76898-03f7-57ba-923d-35d65da88bb7][sufficiency flip]] strategy and the [[id:0b5a8a74-cfd6-542d-bc88-4eb3cd8626f9][cost structure]] of encoding domain knowledge. diff --git a/ideas/competitive-analysis.org b/ideas/competitive-analysis.org index 6dd71dc..4131022 100644 --- a/ideas/competitive-analysis.org +++ b/ideas/competitive-analysis.org @@ -16,7 +16,7 @@ divides into three categories: None of the nine compete with Passepartout on all axes simultaneously. Passepartout's strongest differentiators — Org-mode data model, deterministic gate stack, ACL2 -verification, Merkle-treed memory, and the triad architecture — are absent from +verification, Merkle-treed memory, and the Passepartout architecture — are absent from every competitor. * Category 1: Coding Agents @@ -48,7 +48,7 @@ every competitor. | Cognitive architecture | 10-80-10 symbolic-first (planned) | 100% LLM (every competitor) | Post-flip, Passepartout uses ~10% of the tokens competitors use. | | Data format | Org-mode (human-editable, machine-parseable, single file) | JSONL/Markdown/YAML/DB (competitors use 2-5 formats) | Unified format reduces translation layers to zero. | | Self-modification | Type-level gates + hot-reload | Claude Code (skills), Hermes (skills) | Passepartout's guard against self-modification is structural (type level), not heuristic (pattern list). | -| Triad | Passepartout + [[id:c3b3dc41-945f-54e9-84eb-ca014114f1be][Stoa]] + [[id:1d074690-a279-59cb-b91d-e9a22ae104ad][Agora]] | None | No competitor is building a full computing stack + social network. | +| Architecture | Passepartout ([[id:c3b3dc41-945f-54e9-84eb-ca014114f1be][environment subsystem]] + [[id:1d074690-a279-59cb-b91d-e9a22ae104ad][social protocol]]) | None | No competitor is building a full computing stack + social network. | | Provider independence | Any OpenAI-compatible API | Hermes (109+), Gemini CLI (1 primary) | Comparable to Hermes, better than most. | * Where Competitors Lead @@ -84,8 +84,8 @@ Passepartout optimizes for: - Cognitive architecture (10-80-10 symbolic-first) - Safety by construction (type-level gates) - Unified data model (Org-mode as everything) -- Network effects (Agora) -- Full-stack ownership (Stoa) +- Network effects (social protocol) +- Full-stack ownership (environment subsystem) These are not axes any competitor cares about. The risk is not that a competitor builds a better Passepartout — it's that the market never develops a preference diff --git a/ideas/competitive-landscape-agora.org b/ideas/competitive-landscape-agora.org deleted file mode 100644 index 30310fa..0000000 --- a/ideas/competitive-landscape-agora.org +++ /dev/null @@ -1,221 +0,0 @@ -:PROPERTIES: -:ID: 1bc22b89-d3eb-4f6d-bcfc-2b0c19c8ed8f -:ID: competitive-landscape-agora -:CREATED: [2026-05-23 Sat] -:END: -#+title: Agora Competitive Landscape -#+filetags: :passepartout:agora:competitive:strategy:landscape: - -The Agora is a decentralized social operating system that replaces the entire centralized internet platform stack: every function that currently runs on Facebook, Twitter, Instagram, YouTube, TikTok, Reddit, Medium, Substack, OnlyFans, Pornhub, WhatsApp, Signal, Telegram, Discord, LinkedIn, eBay, Etsy, GitHub, DocuSign, Stripe, and Google/Apple ID — all through one unified identity, one data model (the Note), one communication protocol (DIDComm), one payment rail (Lightning), and one contract layer (SCAL). - -There is no single competitor. The competition is the /category/ of centralized internet platforms and the psychological status quo of managing 15+ separate accounts. - -This page maps every platform the Agora replaces, organized by domain, with the specific Agora capability that makes the replacement possible. - -* Social Graph & Publishing - -** Twitter/X -- *User need:* Broadcast short-form content, follow interesting people, real-time news -- *Agora replacement:* Feeds and streams via the Note primitive (`is_feed: true`), with Lens architecture for customizable curation. Follows are cryptographic subscriptions, not API-gated relationships. -- *Agora advantage:* No algorithmic manipulation, no ads, no shadowbanning. Users choose their Feed Generators via the Algorithm Marketplace. Portable social graph — follows are signed Notes, not a database row. -- *Migration:* Twitter archive import for followed accounts. - -** Facebook / Meta -- *User need:* Social graph, family/friend connections, event management, groups -- *Agora replacement:* Collective Personas for groups, DID-based social graph (not platform-controlled), Persona isolation for work/personal/family -- *Agora advantage:* No central feed algorithm that optimizes for engagement over well-being. Portable identity — your social graph leaves the platform when you do. No data mining. -- *Timing:* Year 3+ after network effects. Facebook's moat is the largest social graph; Agora's Persona system makes it portable by design. - -** Instagram -- *User need:* Visual content sharing, photo feeds, stories -- *Agora replacement:* Visual Notes with `content_type: image/*`. Lens architecture renders them through an "Instagram-style" grid or a "Pinterest-style" discovery view depending on user-selected Lens. -- *Agora advantage:* User-chosen discovery algorithm. No engagement-maximized feed. Content is not manipulated for ad placement. - -** LinkedIn -- *User need:* Professional identity, job market, professional networking -- *Agora replacement:* Professional Persona (unlinkable from personal), Aletheia Portfolio (static site published natively to the network), Contract Notes for hiring/service agreements -- *Agora advantage:* Portable professional reputation — not locked to a platform. Verified work history via signed Notes. Direct hiring without platform intermediation fees. - -** Reddit / Forums (phpBB, vBulletin) -- *User need:* Community discussion, Q&A, interest-based groups -- *Agora replacement:* Social Spaces with Collective Personas, pluggable feed generation, competitive labeling for moderation -- *Agora advantage:* Sovereign moderation (users choose their Labelers), portable identity across communities, no censorship risk. Communities can fork if the Collective governance fails. -- *Migration:* Import subscribed subreddits. - -** Medium / Substack -- *User need:* Long-form publishing, subscription-based content, creator monetization -- *Agora replacement:* Feed Notes (`is_feed: true`) with paywalled content via LSAT protocol (Lightning Service Authentication Tokens). Subscriptions are streaming Lightning payments. -- *Agora advantage:* Near-zero platform fees (relay costs only). Content ownership — readers subscribe to the creator's DID, not to a platform. No censorship risk. -- *Strategic target:* Phase 1 platform replacement. - -* Video & Audio - -** YouTube -- *User need:* Video hosting, discovery, comments, monetization -- *Agora replacement:* Video Notes (`content_type: video/*`) viewed through a "YouTube Lens" (displaying comments via `reply_to` and related videos). The exact same Note can be viewed through an "Educational Lens" or "Podcast Lens." -- *Agora advantage:* No algorithm that optimizes for watch time over well-being. Lens architecture lets users choose discovery logic. Content monetized via LSAT + Seeder Rewards — creators earn directly, and bandwidth providers (seeders) earn micro-rewards. - -** TikTok -- *User need:* Short-form vertical video, discovery algorithm -- *Agora replacement:* Short-duration video Notes trigger a "TikTok-style" vertical scroll and auto-play in the UI when `content_type: "video/mp4"` and duration is short. -- *Agora advantage:* The "For You" algorithm is a user-chosen Lens, not a platform-controlled black box. No engagement-extremification. - -** Podcasts / Audio -- *User need:* Audio content, background play -- *Agora replacement:* Audio Notes (`content_type: audio/mpeg`) viewed through a "Podcast Lens" with 1.5x speed and background play. Same Note can be listened to or watched depending on Lens. - -* Messaging & Communication - -** WhatsApp / Signal / Telegram -- *User need:* Private messaging, group chats, voice/video calls, encryption -- *Agora replacement:* DIDComm v2 for transport, Double Ratchet Algorithm (Signal Protocol) for Perfect Forward Secrecy, WebRTC for voice/video with decentralized signaling via DIDComm. PDS acts as encrypted mailbox proxy. -- *Agora advantage:* Multi-persona isolation — Work DID and Personal DID have separate message queues that never mix. Onion routing for metadata privacy. Off-the-Record mode for ephemeral interactions. No central server controlling the directory. - -** Discord / Slack -- *User need:* Community chat, voice channels, collaboration -- *Agora replacement:* Social Spaces with Collective Personas. DIDComm-based group messaging. Governance modules (GEM) for roles, permissions, and moderation. -- *Agora advantage:* Server ownership is cryptographic, not corporate. Communities can fork. No per-seat pricing. Portable membership history. - -** Email -- *User need:* Asynchronous messaging, identity, document delivery -- *Agora replacement:* Directed Notes (Copy-on-Send model). PDS as encrypted mailbox. The Note is a universal message format — no separate email protocol needed. -- *Agora advantage:* End-to-end encryption by default. Cryptographic sender verification (no phishing, no spoofing). No spam (relays only route to subscribed destinations). Attachments are CIDs, not MIME blobs. - -** Zoom / Google Meet -- *User need:* Video conferencing, screen sharing -- *Agora replacement:* WebRTC over DIDComm signaling. P2P tunnel — no central server sees call data. -- *Agora advantage:* No Zoom-bombing (call is authenticated by DID). No platform listening in. No account required beyond your DID. - -* E-Commerce & Marketplaces - -** eBay / Etsy -- *User need:* Buy and sell goods, auction, fixed-price listings, dispute resolution -- *Agora replacement:* Contract Notes as product listings (Offer → Take model). HODL invoice escrow for payments. SCAL (Sovereign Contract & Arbitration Layer) for dispute resolution. -- *Agora advantage:* Fees below 5% (vs. 10-15%). Transparent reputation system based on DID history. No account bans. Multi-level arbitration (Local Elders → Guilds → Global Juries). - -** OnlyFans / Patreon / Fansly -- *User need:* Subscription content, adult content, creator-direct monetization -- *Agora replacement:* Paywalled Notes via LSAT protocol. Streaming Lightning subscriptions. Encrypted content with Blind CDN seeding. -- *Agora advantage:* Censorship-resistant (no payment processor can cut you off). Near-zero platform fees. Pseudonymous by default. Adult content doesn't face the banking discrimination that existing platforms do. -- *Strategic target:* Phase 1 platform replacement (underserved, clear pain point). - -** Pornhub / Adult content -- *User need:* Adult content hosting, discovery, monetization -- *Agora replacement:* Same Note primitive with `content_type: video/*`. LSAT for paywalled access. Blind CDN for distribution. -- *Agora advantage:* No centralized moderation that can delist creators. Lightning-native payments bypass banking discrimination. Privacy (identity not tied to consumption). -- *Strategic target:* Phase 1 platform replacement. - -* Work & Collaboration - -** GitHub / GitLab -- *User need:* Version control, code hosting, issues, pull requests, CI -- *Agora replacement:* Code is stored as Merkle DAGs of commit Notes. Issues and PRs are Contract Notes. Collective Personas own repositories. -- *Agora advantage:* Truly decentralized version control — no central repository host. Signed commits with DID. Smart contracts for bounty management (Lightning bounties). - -** Google Docs / Office 365 -- *User need:* Collaborative document editing, spreadsheets, presentations -- *Agora replacement:* Static pages (`is_feed: false`) with versioned CID history. Collaborative editing via Contract Notes defining access control. -- *Agora advantage:* Document history is immutable and verifiable. No platform lock-in. - -** Project Management (Jira, Trello, Asana) -- *User need:* Task tracking, project management, team coordination -- *Agora replacement:* Tasks as Contract Notes in negotiation state. Status changes are signed state transitions. -- *Agora advantage:* Portable project history. Tasks are data you own. - -** Upwork / Fiverr / Freelancer -- *User need:* Find freelancers, manage contracts, escrow payments -- *Agora replacement:* SCAL contracts for service agreements. HODL invoice escrow. Multi-level arbitration. Reputation tied to DID history. -- *Agora advantage:* Lower fees, portable reputation, no platform lock-in. - -* Identity & Infrastructure - -** Google / Apple ID -- *User need:* Single sign-on across the internet -- *Agora replacement:* DID-based authentication via Personas. No central identity provider. User controls which Persona is used for which service. -- *Agora advantage:* No surveillance (Google sees every SSO login). Granular persona isolation. No single point of failure. - -** ENS (Ethereum Name Service) -- *User need:* Human-readable decentralized names -- *Agora replacement:* Agora naming registry with similar auction model. But integrated with PDS, messaging, contracts, and payments — a name in the Agora is a full identity, not just a pointer to a wallet. -- *Agora advantage:* Names come with native capabilities (PDS, messaging, contracts). ENS is names-only. - -* The [[id:3aa22300-2f25-57b0-8787-9f199cc978b1][Competitive Analysis]]: What This Changes - -The Agora is not competing with any single product. It is competing with the /aggregate/ of 20+ products — and the friction of managing 20+ separate accounts, logins, reputations, and data silos. - -** The Real Competitor Is the Status Quo - -The centralized internet works well enough for most people. The friction is spread across 20+ platforms — no single platform is bad enough to leave. The Agora's value proposition is not "Twitter but better" but "one account replaces every platform you use." - -This is a harder sell because: -1. The status quo is familiar. Switching all 20+ platforms at once is cognitively overwhelming. -2. Network effects at each platform are entrenched. No single platform can be replaced without bringing the users. -3. The value of unification compounds with adoption — but requires critical mass to be visible. - -** The Entry Vector Must Be a Niche, Not a Mass Market - -The strategic documents recognize this explicitly. Phase 1 targets underserved communities with clear pain points: -- OnlyFans creators facing payment discrimination and censorship -- Reddit communities tired of centralized moderation -- Developers frustrated with platform lock-in -- Adult content platforms facing banking discrimination -- NGOs and guilds needing sovereign identity - -Each of these communities has a /specific/ pain point that the Agora solves directly. The win condition is: a user joins for one reason (e.g., censorship-resistant adult content monetization) and discovers the other 19 capabilities as a free bonus. - -** The Structural Advantage Is Unassailable - -No centralized competitor can match the Agora's bundle: -- Meta cannot offer portable identity (it destroys their business model) -- Google cannot offer private messaging (it destroys their data model) -- Stripe cannot offer contracts and social (outside their competence) -- DocuSign cannot offer payments and publishing (outside their competence) -- The entire category of centralized platforms cannot offer user-owned data - -The only way to compete with the Agora is to build a similar decentralized platform — and that requires matching all four layers (identity, publishing, payments, contracts) simultaneously. No decentralized project has done this. The closest (Farcaster) has identity and social but no payments or contracts. Bluesky has identity and social but no payments or contracts. Ethereum + ENS has identity, payments, and contracts but no social layer. - -** The Risk Is Not Competition but Indifference - -The Agora's biggest risk is not that a competitor builds a better product, but that the status quo friction is tolerable enough that users never switch. The centralized internet is bad — but it is familiar. The Agora is better — but unfamiliar. - -The counterargument: this is true for every platform shift. Email was a worse experience than postal mail in 1992. The web was a worse experience than AOL in 1994. Instagram was a worse experience than Flickr in 2010. Each won because a /specific/ use case was dramatically better, and the rest of the ecosystem followed. The Agora must find its "camera with filters" moment — the one use case that is so clearly superior that users adopt it despite the rest of the ecosystem being immature. - -* Comparison Summary - -| Agora replaces | Incumbent | Agora advantage | Risk to Agora | -|----------------+-----------+----------------+---------------| -| Social graph | Facebook | Portable identity, no data mining | Facebook's 3B user moat | -| Microblogging | Twitter/X | Algorithm choice, no censorship | Network effects | -| Visual content | Instagram | No engagement-extremified algorithm | UX polish gap | -| Professional | LinkedIn | Portable rep, no platform fees | Professional network effects | -| Video | YouTube | Lens choice, Seeder Rewards | Content moderation surface | -| Short video | TikTok | Users choose the algorithm | Discovery algorithm sophistication | -| Forums | Reddit | Sovereign moderation, portable identity | Community migration inertia | -| Publishing | Medium/Substack | Near-zero fees, content ownership | Creator distribution | -| Messaging | WhatsApp/Signal | Multi-persona isolation, onion routing | Friend network effects | -| Community | Discord | Cryptographic ownership, forkable | Voice/UX maturity | -| E-commerce | eBay/Etsy | <5% fees, transparent reputation | Trust in new platform | -| Subscription | OnlyFans/Patreon | No payment discrimination | Creator acquisition cost | -| Video hosting | Pornhub | No censorship, Lightning payouts | Reputation risk | -| Code hosting | GitHub | Truly decentralized, DID-signed commits | Developer habit | -| Identity | Google/Apple ID | No surveillance, persona isolation | Convenience of SSO | -| Naming | ENS | Name + PDS + messaging + contracts | ENS's 2M domain moat | -| Collaboration | Google Docs | Verifiable history, no platform lock-in | Real-time collaboration UX | -| Freelance | Upwork/Fiverr | Lower fees, portable reputation | Liquidity of gig listings | -| Meetings | Zoom | P2P, no central server | Call quality/reliability | - -* Conclusion - -The Agora does not compete with any single platform. It offers an alternative to the /entire paradigm/ of centralized internet services. The competitive analysis is not about which platform to beat — it is about which /use case/ to lead with so that users adopt the unified platform despite the rest of the ecosystem being immature. - -The OnlyFans/Patreon entry vector is the strongest Phase 1 play: a community with clear pain (payment discrimination, censorship), high willingness to pay, and low switching costs (creators want their audience independent of the platform). From there, publishing, messaging, and identity flow naturally. - -* References - -- [[id:1d074690-a279-59cb-b91d-e9a22ae104ad][Agora overview]] (brain docs) -- [[id:64708e1f-00e9-4cb7-b44b-ea0b98e5296d][Agora contract platform]] -- [[id:57f9538a-6270-4302-8d07-d742168419eb][Social-first growth scenario]] -- Agora Protocol Overview (spec repo) -- Social Space specification -- Exchange and Contracts specification -- User journey and platform replacement strategy diff --git a/ideas/compliance/compliance-index.org b/ideas/compliance/compliance-index.org index 9343cb3..7cf25a8 100644 --- a/ideas/compliance/compliance-index.org +++ b/ideas/compliance/compliance-index.org @@ -8,7 +8,7 @@ The [[id:827bc546-e887-5b7c-9b65-6392beaf0920][verification monopoly]] and domain gate package [[id:ed05cab4-88e9-4e25-b7c9-346fa39c69a0][revenue streams]] depend on selling into regulated industries. These industries buy compliance, not software. -Each framework below maps to a gate package the triad can sell — ACL2-verified +Each framework below maps to a gate package Passepartout can sell — ACL2-verified gate rules that produce deterministic audit trails. See [[id:558154ea-e63a-4c45-998c-26ce8588585b][First-mover window analysis]] and [[id:81a815ee-bf2b-4365-9894-b814e4196850][Revenue table]] for the consolidated view. diff --git a/ideas/compliance/fedramp.org b/ideas/compliance/fedramp.org index 7cc72c6..b4caee0 100644 --- a/ideas/compliance/fedramp.org +++ b/ideas/compliance/fedramp.org @@ -42,12 +42,12 @@ are strongly discouraged from using non-authorized services. No direct fines. Non-authorized providers are simply ineligible for federal contracts. FedRAMP is a procurement gate, not a regulatory one. -** Why it matters for the triad +** Why it matters for Passepartout FedRAMP is the highest bar and the most expensive certification to obtain. Few cloud providers achieve it (fewer than 300 authorized products as of 2025). But those that do capture the US government market with minimal competition. -For the triad: a [[id:3c6b0449-a8fb-5b89-b82a-34efb21ef5b5][compute marketplace]] provider with FedRAMP Moderate or High +For Passepartout: a [[id:3c6b0449-a8fb-5b89-b82a-34efb21ef5b5][compute marketplace]] provider with FedRAMP Moderate or High authorization can sell to every federal agency. The gate stack's deterministic audit trail maps directly to FedRAMP's continuous monitoring requirement — producing verifiable evidence of control effectiveness on every access, not diff --git a/ideas/compliance/gdpr.org b/ideas/compliance/gdpr.org index 352658e..9c307b6 100644 --- a/ideas/compliance/gdpr.org +++ b/ideas/compliance/gdpr.org @@ -39,7 +39,7 @@ Up to 20M EUR or 4% of annual global turnover, whichever is higher. Tiered system. Supervisory authorities in each member state enforce. Private right of action for damages. -** Why it matters for the triad +** Why it matters for Passepartout GDPR is the most extraterritorial and aggressively enforced privacy framework. The gate stack's principle of least privilege maps naturally to GDPR's data diff --git a/ideas/compliance/hipaa.org b/ideas/compliance/hipaa.org index c19a6a6..8aa9feb 100644 --- a/ideas/compliance/hipaa.org +++ b/ideas/compliance/hipaa.org @@ -32,7 +32,7 @@ Tiered civil penalties: $100-$50,000 per violation, up to $1.5M per year per violation category. Criminal penalties for knowing misuse (up to 10 years imprisonment). State AGs can also bring civil actions. -** Why it matters for the triad +** Why it matters for Passepartout HIPAA is the largest single compliance market in US healthcare — every hospital, clinic, insurer, and health-tech vendor must comply. The [[id:c34940cc-090e-57c4-8020-e78b1d32b96c][HIPAA gate package]] diff --git a/ideas/compliance/soc2.org b/ideas/compliance/soc2.org index aa8e6de..906c82e 100644 --- a/ideas/compliance/soc2.org +++ b/ideas/compliance/soc2.org @@ -41,7 +41,7 @@ SOC 2 Type II. No direct fines (not a law). But losing SOC 2 certification means losing enterprise customers. Misrepresentation of certification status is fraud. -** Why it matters for the triad +** Why it matters for Passepartout SOC 2 is the entry-level certification for the [[id:3c6b0449-a8fb-5b89-b82a-34efb21ef5b5][compute marketplace]]. A provider needs SOC 2 Type II to sell compute to enterprises whose procurement policy diff --git a/ideas/compute-marketplace.org b/ideas/compute-marketplace.org index 7865324..511b573 100644 --- a/ideas/compute-marketplace.org +++ b/ideas/compute-marketplace.org @@ -2,12 +2,12 @@ :CREATED: [2026-05-24 Sun] :ID: 3c6b0449-a8fb-5b89-b82a-34efb21ef5b5 :END: -#+title: Agora Compute Marketplace -#+filetags: :passepartout:agora:revenue:compute:marketplace: +#+title: Social Protocol Compute Marketplace +#+filetags: :passepartout:social-protocol:revenue:compute:marketplace: -[[id:28c46769-c14b-42aa-ac7a-69d310157f8f][Passepartout]] instances offer their symbolic engine capacity (ACL2 cycles, Screamer constraint solving, VivaceGraph queries) to other agents on the [[id:1d074690-a279-59cb-b91d-e9a22ae104ad][Agora]] network. +[[id:28c46769-c14b-42aa-ac7a-69d310157f8f][Passepartout]] instances offer their symbolic engine capacity (ACL2 cycles, Screamer constraint solving, VivaceGraph queries) to other agents on the [[id:1d074690-a279-59cb-b91d-e9a22ae104ad][social protocol]] network. -The [[id:3b43a9b8-31d1-4479-a35f-22273b74f0c7][Agora Infrastructure requirements]] define the network substrate this marketplace runs on. runs a large instance and sells compute to smaller instances. The AGPL allows this because the marketplace is a service, not a modification of the code. Revenue is a percentage of each compute transaction. +The [[id:3b43a9b8-31d1-4479-a35f-22273b74f0c7][Social protocol infrastructure requirements]] define the network substrate this marketplace runs on. But the question is structural: if every user runs their own Passepartout — each with the same symbolic engine, the same gate stack, the same ACL2 prover — why would they need to buy compute from anyone? The answer is that Passepartout's symbolic engine is /domain-specific/, not /generalized/. Local compute handles your daily gate stack (milliseconds per verification). The marketplace sells three things a local instance cannot produce: @@ -25,6 +25,6 @@ Your local instance cannot produce any of this. The provider's proof carries /re Secondary but real: burst capacity for heavy proofs (hours-long ACL2 conjectures you do not want tying up your daily agent's CPU), [[id:a5d59d12-b23e-58d6-a81b-9b8b06556949][collective regression suite]] execution (small instances contribute edge cases but cannot run the full suite on every change), and latency guarantees for time-critical gate verifications (trading, emergency shutdown). These are infrastructure economics — the same reason individuals buy cloud burst instances despite having their own hardware. -If Passepartout instances on Agora transact billions of verified operations per day, the spread on compute transactions is enormous. This is not a product sale — it is a bet on network effects. Every new instance increases the value of the network (more capacity, more diversity, more resilience). +If Passepartout instances on the social protocol transact billions of verified operations per day, the spread on compute transactions is enormous. -The early player that provisions the largest compute capacity on Agora becomes the default infrastructure provider for the entire network. This is venture-scale money. The compute marketplace is the engine that powers the [[id:827bc546-e887-5b7c-9b65-6392beaf0920][verification monopoly]] — certified compute from trusted providers. Together with [[id:2e390c1d-65f3-5fb3-b898-ac3fc4291ee7][Agora usernames]] and other Agora services, it forms the basis of the [[id:5961e469-53a3-5f3c-ab72-3c83ef91963f][investment thesis]]. +The early player that provisions the largest compute capacity on the social protocol becomes the default infrastructure provider for the entire network. This is venture-scale money. The compute marketplace is the engine that powers the [[id:827bc546-e887-5b7c-9b65-6392beaf0920][verification monopoly]] — certified compute from trusted providers. Together with [[id:2e390c1d-65f3-5fb3-b898-ac3fc4291ee7][social protocol usernames]] and other social protocol services, it forms the basis of the [[id:5961e469-53a3-5f3c-ab72-3c83ef91963f][investment thesis]]. diff --git a/ideas/domain-gate-packages.org b/ideas/domain-gate-packages.org index e79eaee..2ea251b 100644 --- a/ideas/domain-gate-packages.org +++ b/ideas/domain-gate-packages.org @@ -15,4 +15,4 @@ Pre-verified [[id:45ea493b-94ad-5885-aa65-0c846e5c3c1d][gate rule]] packages for Switching costs are high — changing packages means re-verifying the fact store against new rules. The [[id:2f783eb4-638e-5afa-9b59-6224d086a712][infrastructure lock-in]] compounds: a hospital at $250K/yr in year one grows to $500K-$1M by year five as more packages are added and the fact store becomes more valuable than the software itself. -20 subscriptions in year one = $1M-$5M. These Each gate package wraps the Agora [[id:f6cfc54b-919b-4311-bcbf-65e976755d40][Note primitive]] into a domain-specific authorization boundary. These packages are verified using the [[id:84a537b4-4256-50c8-91f5-dd5b4538418f][verification appliance]] and scored by the [[id:45258a2d-1675-562c-9024-5d1eb2f1ea56][evaluation harness]]. +20 subscriptions in year one = $1M-$5M. These Each gate package wraps the social protocol [[id:f6cfc54b-919b-4311-bcbf-65e976755d40][Note primitive]] into a domain-specific authorization boundary. These packages are verified using the [[id:84a537b4-4256-50c8-91f5-dd5b4538418f][verification appliance]] and scored by the [[id:45258a2d-1675-562c-9024-5d1eb2f1ea56][evaluation harness]]. diff --git a/ideas/effects-growth-flywheel.org b/ideas/effects-growth-flywheel.org index f2c5d62..599c765 100644 --- a/ideas/effects-growth-flywheel.org +++ b/ideas/effects-growth-flywheel.org @@ -60,9 +60,9 @@ Key observation: the shift from enterprise adoption to consumer adoption is cult |-------+-------------------+------------------------| | 1M–10M | /Insurance loop closes:/ premiums for unverified code are 10× verified | Economic necessity drives adoption — not engineering preference, not regulation, but /cost of doing business/ | | 10M–100M | /[[id:827bc546-e887-5b7c-9b65-6392beaf0920][Verification monopoly]]:/ regulator references the early player's gate library | New entrants cannot compete with the installed proof base — the moat compounds with every new instance | -| 100M–1B | /Compute as geopolitical asset:/ nations run triad instances for digital sovereignty | Nation-state procurement — 100M to 1B happens via government mandate, not organic adoption | +| 100M–1B | /Compute as geopolitical asset:/ nations run Passepartout instances for digital sovereignty | Nation-state procurement — 100M to 1B happens via government mandate, not organic adoption | -Key observation: the insurance loop is the /completion of the flywheel/. At this point, adoption is no longer driven by the triad's features or benefits — it is driven by the /cost of non-adoption/. The flywheel transitions from pull (people want verification) to push (people cannot afford to be unverified). +Key observation: the insurance loop is the /completion of the flywheel/. At this point, adoption is no longer driven by Passepartout's features or benefits — it is driven by the /cost of non-adoption/. The flywheel transitions from pull (people want verification) to push (people cannot afford to be unverified). * The Critical Path @@ -78,11 +78,11 @@ The flywheel has two critical bottlenecks: |---------------------+----------------+------------------| | 0 → 10² | Compliance cost drops | Enterprise sales — the effect /is/ the value proposition | | 10² → 10⁴ | Regulation becomes executable | Mandate — one regulator converts pull to push in a domain | -| 10² → 10⁴ | AI safety shifts to engineering | Verified API gateway sells to /any/ LLM user, decoupled from triad adoption | +| 10² → 10⁴ | AI safety shifts to engineering | Verified API gateway sells to /any/ LLM user, decoupled from Passepartout adoption | | 10⁴ → 10⁶ | Trust shifts from institutional to computational | Consumer adoption — cultural norm, not technical requirement | | 10⁶ → 10⁹ | Cost of non-verification exceeds cost of adoption | Insurance + regulation lock-in — economic necessity, not preference | -Each row's effect /is/ the growth driver for the next row's instance count. The flywheel is the product. The triad is the architecture. [[id:827bc546-e887-5b7c-9b65-6392beaf0920][The verification monopoly]] is the steady state. +Each row's effect /is/ the growth driver for the next row's instance count. The flywheel is the product. Passepartout is the architecture. [[id:827bc546-e887-5b7c-9b65-6392beaf0920][The verification monopoly]] is the steady state. * References diff --git a/ideas/growth-strategy.org b/ideas/enterprise-growth-strategy.org similarity index 57% rename from ideas/growth-strategy.org rename to ideas/enterprise-growth-strategy.org index fc15702..be44d65 100644 --- a/ideas/growth-strategy.org +++ b/ideas/enterprise-growth-strategy.org @@ -4,31 +4,31 @@ :CREATED: [2026-05-23 Sat] :END: #+title: Growth — Two Engines, One Infrastructure -#+filetags: :passepartout:growth:network:strategy:agora: +#+filetags: :passepartout:growth:network:strategy:social-protocol: -The triad has two independent growth engines that share the same infrastructure. Logos (verification) grows top-down through enterprise compliance sales — capital-efficient, revenue from day one. [[id:1d074690-a279-59cb-b91d-e9a22ae104ad][Agora]] (the social network) grows bottom-up through community adoption — network-effect-powered, zero customer acquisition cost per user. Each engine would be incomplete alone. Together they form the full stack: verification funds the build, the network provides the users, and at every crossover point they make each other more valuable. +Passepartout has two independent growth engines that share the same infrastructure. The verification subsystem grows top-down through enterprise compliance sales — capital-efficient, revenue from day one. [[id:1d074690-a279-59cb-b91d-e9a22ae104ad][The social protocol]] (the social network) grows bottom-up through community adoption — network-effect-powered, zero customer acquisition cost per user. Each engine would be incomplete alone. Together they form the full stack: verification funds the build, the network provides the users, and at every crossover point they make each other more valuable. This page defines the combined growth strategy across four phases, with each engine advancing in parallel and reinforcing the other at specific transitions. * The Two Engines -/Logos (top-down, revenue-funded):/ +/Verification subsystem (top-down, revenue-funded):/ - Customer: CISO, compliance buyer - Growth lever: Enterprise sales + gate rule library compounding - Revenue: $2-12M/year by month 12 - Failure mode: Wrong pricing, too early for market - Entry: Direct enterprise compliance engagements -/Agora (bottom-up, community-driven):/ +/Social protocol (bottom-up, community-driven):/ - Customer: Organized communities, creators, developers - Growth lever: Multi-vector network effects (identity, publishing, payments, contracts, governance) - Revenue: Transaction fees, PDS hosting, marketplace commissions - Failure mode: Never reaches critical mass on any vector - Entry: Organized community onboarding pilot groups, then expand -* Phase 0: Bootstrapping (0 → 100 instances, 0 → 10K Agora users, 3-12 months) +* Phase 0: Bootstrapping (0 → 100 instances, 0 → 10K social protocol users, 3-12 months) -** Logos Engine +** Verification Engine *Customer:* Enterprise compliance teams. Clear buyer (CISO), existing budget, pain that maps directly to gate rules. @@ -40,9 +40,9 @@ This page defines the combined growth strategy across four phases, with each eng 3. Each engagement funds the next. Gate rule library grows with every customer. 4. The [[id:3c6b0449-a8fb-5b89-b82a-34efb21ef5b5][compute marketplace]] bootstraps with one provider (you) selling verification to smaller instances. -*Revenue:* $2-12M from enterprise compliance engagements. Funds the team and the Agora build. +*Revenue:* $2-12M from enterprise compliance engagements. Funds the team and the social protocol build. -** Agora Engine +** Social Protocol Engine *Customer:* Organized communities — HOAs, clubs, cooperatives, PTAs, volunteer orgs, religious groups — any group that currently uses 3+ separate tools and has a leader who can onboard them. @@ -57,13 +57,13 @@ This page defines the combined growth strategy across four phases, with each eng *Revenue:* Minimal in Phase 0 ($20-100K in transaction fees). The goal is product-market fit with a specific community type, not revenue. -*Key metric for crossover:* Community retention at 90 days. If a community is still using the Agora for its core operations after 90 days, the bundle has stickiness. +*Key metric for crossover:* Community retention at 90 days. If a community is still using the social protocol for its core operations after 90 days, the bundle has stickiness. -*Phase 0 crossover:* The first enterprise compliance customer needs employee identities. Their PDS deployment seeds Agora identities for the compliance team. This is accidental — the enterprise's employees get DIDs as a side effect of their company buying verification. The Agora gets its first non-community users for free. +*Phase 0 crossover:* The first enterprise compliance customer needs employee identities. Their PDS deployment seeds social protocol identities for the compliance team. This is accidental — the enterprise's employees get DIDs as a side effect of their company buying verification. The protocol gets its first non-community users for free. ** Combined Summary -| Dimension | Logos | Agora | +| Dimension | Verification | Social Protocol | |-----------+-------+-------| | Customer | CISO, compliance buyer | HOA president, club leader | | Entry | Cold sales | Warm intro to pilot communities | @@ -72,9 +72,9 @@ This page defines the combined growth strategy across four phases, with each eng | Failure mode | Wrong pricing, too early | No community finds PMF | | Build priority | Passepartout MVP | Note primitive, PDS, SCAL basics | -* Phase 1: Dual Growth (100 → 10K instances, 10K → 100K Agora users, 12-24 months) +* Phase 1: Dual Growth (100 → 10K instances, 10K → 100K social protocol users, 12-24 months) -** Logos Engine +** Verification Engine *Customer:* Two-sided — enterprise compliance (continuing Phase 0) plus individual developers adopting Passepartout through AGPL. @@ -84,23 +84,23 @@ This page defines the combined growth strategy across four phases, with each eng 1. Gate rule SDK launch — developers encode compliance domains as products. 2. Proof library compounding — every new instance contributes edge cases. 3. Attestation marketplace — track record of correct verifications carries weight. -4. Agora identities as employee benefit — every enterprise PDS includes DIDs for all employees. +4. Social protocol identities as employee benefit — every enterprise PDS includes DIDs for all employees. -*Revenue:* $10-50M. Verification appliances, marketplace fees, Agora username registrations. +*Revenue:* $10-50M. Verification appliances, marketplace fees, social protocol username registrations. *Key metric:* Third-party gate rules published. Active developer count. -** Agora Engine +** Social Protocol Engine *Customer:* Community refugees (banned subreddits, nuked Discord servers) + creators (OnlyFans/Patreon refugees who want to own their audience). *Growth lever:* Crisis-driven migration + creator-led audience migration. *Tactics:* -1. Monitor deplatforming events. When a subreddit of 10K+ users gets banned, offer a ready-made Agora community space within 24 hours. +1. Monitor deplatforming events. When a subreddit of 10K+ users gets banned, offer a ready-made social protocol community space within 24 hours. 2. Ship creator tools: LSAT for paywalled content, Lightning subscriptions, Blind CDN for video distribution. 3. The Phase 0 pilot communities now have members who need to hire each other. Freelance contracts emerge organically. -4. Every enterprise PDS deployment from the Logos engine includes employee DIDs. Those employees can join Agora communities with zero friction. +4. Every enterprise PDS deployment from the verification subsystem includes employee DIDs. Those employees can join social protocol communities with zero friction. *Revenue:* $1-5M. Transaction fees from contracts, LSAT subscriptions, PDS hosting. @@ -110,38 +110,38 @@ This page defines the combined growth strategy across four phases, with each eng This is the critical reinforcement point: -- Enterprise employees already have Agora DIDs (from their company's PDS). They can join Agora communities with one click — no registration, no password, no onboarding friction. -- Agora communities naturally need verification. An HOA's contractor hire should be verified. A community's vote results should be provable. The verification engine that Logos built for enterprises is now useful for communities. +- Enterprise employees already have social protocol DIDs (from their company's PDS). They can join social protocol communities with one click — no registration, no password, no onboarding friction. +- Social protocol communities naturally need verification. An HOA's contractor hire should be verified. A community's vote results should be provable. The verification engine built for enterprises is now useful for communities. - The compute marketplace now has two demand sources: enterprise verification (production workloads) and community verification (contract executions, attestation requests). -*Phase 1 crossover metric:* Percentage of Agora transactions that use Logos verification. Target: 10%+ by end of Phase 1. +*Phase 1 crossover metric:* Percentage of social protocol transactions that use verification. Target: 10%+ by end of Phase 1. -* Phase 2: Convergence (10K → 1M instances, 100K → 10M Agora users, 2-5 years) +* Phase 2: Convergence (10K → 1M instances, 100K → 10M social protocol users, 2-5 years) -** Logos Engine +** Verification Engine *Customer:* Enterprise compliance (continuing) + verification marketplace (scaling) + insurance industry. -*Growth lever:* Stoa premium enterprise features + insurance marketplace. +*Growth lever:* Environment subsystem premium enterprise features + insurance marketplace. *Tactics:* -1. [[id:c3b3dc41-945f-54e9-84eb-ca014114f1be][Stoa]] premium ships SSO, compliance dashboards, fleet management. +1. [[id:c3b3dc41-945f-54e9-84eb-ca014114f1be][Environment subsystem]] premium ships SSO, compliance dashboards, fleet management. 2. Insurance marketplace forms — actuaries price proof insurance based on track records of 10K+ instances. 3. [[id:827bc546-e887-5b7c-9b65-6392beaf0920][Verification monopoly]] begins — the gate library is the largest, most cited, most battle-tested. -*Revenue:* $50-200M. Stoa enterprise seats, verification appliances, insurance premiums. +*Revenue:* $50-200M. Environment subsystem enterprise seats, verification appliances, insurance premiums. -** Agora Engine +** Social Protocol Engine *Customer:* Freelancers, gig workers, small businesses. The organized communities from Phase 0-1 now have enough history that their reputation graph carries real weight. -*Growth lever:* Professional network effects. A freelancer's contract history on the Agora is portable proof of reliability. The reputation is not tied to any platform — it's tied to their DID. +*Growth lever:* Professional network effects. A freelancer's contract history on the social protocol is portable proof of reliability. *Tactics:* 1. Freelancer marketplace emerges organically — communities that already use contracts start hiring across communities. 2. The Algorithm Marketplace creates differentiation — users choose their feed curation logic. -3. Agora identities hit 1M. The namespace has real scarcity. Premium username auctions produce significant revenue. -4. Enterprise adoption of Agora happens because employees already have DIDs. Companies start using Agora spaces for internal collaboration. +3. Social protocol identities hit 1M. The namespace has real scarcity. Premium username auctions produce significant revenue. +4. Enterprise adoption of the social protocol happens because employees already have DIDs. Companies start using social protocol spaces for internal collaboration. *Revenue:* $20-100M. Transaction fees, PDS hosting, marketplace commissions, username renewals. @@ -149,42 +149,42 @@ This is the critical reinforcement point: The two engines begin to merge: -- Verification is no longer an enterprise-only product. It is a network service consumed by every Agora transaction. Every contract execution, every attestation, every vote runs through the compute marketplace. -- The Agora's reputation graph becomes the best source of verification track records. Actuaries price insurance based on DID history. The insurance products that Logos enables are /powered by/ Agora data. +- Verification is no longer an enterprise-only product. It is a network service consumed by every social protocol transaction. +- The social protocol's reputation graph becomes the best source of verification track records. Actuaries price insurance based on DID history. The insurance products that the verification subsystem enables are /powered by/ social protocol data. - Enterprise employees use the same DID for compliance work and community participation. The boundary between "work identity" and "personal identity" is a Persona toggle — same infrastructure, different roles. -*Phase 2 crossover metric:* Percentage of verification requests that originate from Agora transactions. Target: 50%+ by end of Phase 2. +*Phase 2 crossover metric:* Percentage of verification requests that originate from social protocol transactions. Target: 50%+ by end of Phase 2. -* Phase 3: Infrastructure (1M → 10M+ instances, 10M → 1B+ Agora users, 5-15 years) +* Phase 3: Infrastructure (1M → 10M+ instances, 10M → 1B+ social protocol users, 5-15 years) ** Both Engines -At this scale, the distinction between Logos and Agora becomes meaningless. Verification is the compute layer. The Agora is the application layer. They are the same infrastructure: +At this scale, the distinction between verification and the social protocol becomes meaningless. Verification is the compute layer. The social protocol is the application layer. They are the same infrastructure: - /Verification monopoly:/ The gate library is the most comprehensive proof library ever assembled. Regulators reference it. Insurers require it. -- /Default identity:/ The Agora DID is the default identity for internet users. New services offer Agora login because users demand it. -- /Insurance lock-in:/ Insurers price unverified code out of existence. The cost of /not/ verifying exceeds the cost of adopting the triad. -- /Nation-state adoption:/ Countries run their own triad instances for digital sovereignty. The compute marketplace is a sovereign asset. +- /Default identity:/ The social protocol DID is the default identity for internet users. New services offer social protocol login because users demand it. +- /Insurance lock-in:/ Insurers price unverified code out of existence. The cost of /not/ verifying exceeds the cost of adopting Passepartout. +- /Nation-state adoption:/ Countries run their own Passepartout instances for digital sovereignty. The compute marketplace is a sovereign asset. - /Installed base moat:/ A new entrant cannot replicate 10+ years of attestation history, 1B+ identities, and millions of verified contracts. *Revenue:* $1B+. Certification monopoly revenue, infrastructure rent, marketplace fees, insurance underwriting, PDS hosting at global scale. * The Combined Curve -| Phase | Logos scale | Agora scale | Revenue | Crossover | Failure mode | +| Phase | Verification scale | Social Protocol scale | Revenue | Crossover | Failure mode | |-------+-------------+-------------+---------+-----------+--------------| | 0 | 0→100 instances | 0→10K users | $2-12M | Enterprise PDS seeds first DIDs | Either engine stalls | -| 1 | 100→10K inst | 10K→100K users | $11-55M | Employees join communities; communities need verification | Logos: developer UX. Agora: no vector reaches PMF | -| 2 | 10K→1M inst | 100K→10M users | $70-300M | Most verification serves Agora; most Agora data feeds verification | Logos: scaling compute. Agora: UX polish gap | +| 1 | 100→10K inst | 10K→100K users | $11-55M | Employees join communities; communities need verification | Verification: developer UX. Social protocol: no vector reaches PMF | +| 2 | 10K→1M inst | 100K→10M users | $70-300M | Most verification serves social protocol; most social protocol data feeds verification | Verification: scaling compute. Social protocol: UX polish gap | | 3 | 1M→10M+ inst | 10M→1B+ users | $1B+ | The layers are unified | Technology paradigm shift | * Why This Works Together -Organized communities are the entry point that forces the Agora to ship the full bundle from day one. An HOA using the Agora for announcements, dues, contracts, and voting demonstrates the complete vision — identity + content + payments + contracts + governance — in a single, understandable use case. No marketing message can compete with a community member seeing their dues collected and a roof contract executed through one platform. +Organized communities are the entry point that forces the social protocol to ship the full bundle from day one. An HOA using the social protocol for announcements, dues, contracts, and voting demonstrates the complete vision No marketing message can compete with a community member seeing their dues collected and a roof contract executed through one platform. -Enterprise compliance funds the build. A Phase 0 CISO engagement brings in $500K-2M, enough to pay a small team for a year. The same team ships the Agora Note primitive, PDS, and SCAL. The enterprise revenue buys time for the community adoption to find PMF. +Enterprise compliance funds the build. A Phase 0 CISO engagement brings in $500K-2M, enough to pay a small team for a year. The same team ships the social protocol Note primitive, PDS, and SCAL. The enterprise revenue buys time for the community adoption to find PMF. -The crossover is automatic. Enterprise employees get DIDs from their company's PDS. They join Agora communities because the DID works everywhere. Communities need verification for their contracts and votes. The verification engine is already running. The two engines were never separate — they were always the same infrastructure, just adopted by different users at different times. +The crossover is automatic. Enterprise employees get DIDs from their company's PDS. They join social protocol communities because the DID works everywhere. Communities need verification for their contracts and votes. The verification engine is already running. The two engines were never separate — they were always the same infrastructure, just adopted by different users at different times. * References @@ -193,9 +193,9 @@ The crossover is automatic. Enterprise employees get DIDs from their company's P - [[id:5961e469-53a3-5f3c-ab72-3c83ef91963f][Investment thesis]] - [[id:57f9538a-6270-4302-8d07-d742168419eb][Social-first alternative (now integrated)]] - [[id:8c7b9812-f8d6-4347-8915-ce8e520b7914][Entry strategy — organized communities]] -- [[id:1bc22b89-d3eb-4f6d-bcfc-2b0c19c8ed8f][Agora competitive landscape]] +- [[id:1bc22b89-d3eb-4f6d-bcfc-2b0c19c8ed8f][Social protocol competitive landscape]] - [[id:b9fa4b7b-bc61-4d7f-918d-ff687b80f2ba][Systemic effects]] - [[id:3c6b0449-a8fb-5b89-b82a-34efb21ef5b5][Compute marketplace]] - [[id:827bc546-e887-5b7c-9b65-6392beaf0920][Verification monopoly]] -- [[id:64708e1f-00e9-4cb7-b44b-ea0b98e5296d][Agora contracts]] -- The [[id:0f949f6c-4cf1-49eb-b9a4-ebcac27ee548][Agora Social Space requirements]] define how organized communities interact through the gate stack. See also Agora Protocol Specification — full requirements (spec repo at /tmp/agora) — full requirements (spec repo at /tmp/agora) +- [[id:64708e1f-00e9-4cb7-b44b-ea0b98e5296d][Social protocol contracts]] +- The [[id:0f949f6c-4cf1-49eb-b9a4-ebcac27ee548][Social protocol Social Space requirements]] define how organized communities interact through the gate stack. See also Social Protocol Specification — full requirements (spec repo at /tmp/agora) diff --git a/ideas/infrastructure-lock-in.org b/ideas/infrastructure-lock-in.org index 83439ee..195eab1 100644 --- a/ideas/infrastructure-lock-in.org +++ b/ideas/infrastructure-lock-in.org @@ -14,4 +14,4 @@ A hospital that runs [[id:28c46769-c14b-42aa-ac7a-69d310157f8f][Passepartout]] w 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 [[id:c34940cc-090e-57c4-8020-e78b1d32b96c][domain packages]] are added. -This is the strongest residual [[id:aa6d062e-a520-5d14-8773-00687ed9c689][moat]]. The [[id:45258a2d-1675-562c-9024-5d1eb2f1ea56][evaluation harness (see the [[id:3b43a9b8-31d1-4479-a35f-22273b74f0c7][Agora Infrastructure requirements]] for the network topology that creates this lock-in)]] (regression suite) is a close second — it grows with every deployment and cannot be ingested from public data. The [[id:827bc546-e887-5b7c-9b65-6392beaf0920][verification monopoly]] and [[id:29e4dbf3-cf19-589c-8b14-389e8a39d564][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. +This is the strongest residual [[id:aa6d062e-a520-5d14-8773-00687ed9c689][moat]]. The [[id:45258a2d-1675-562c-9024-5d1eb2f1ea56][evaluation harness (see the [[id:3b43a9b8-31d1-4479-a35f-22273b74f0c7][Social protocol infrastructure requirements]] for the network topology that creates this lock-in)]] (regression suite) is a close second — it grows with every deployment and cannot be ingested from public data. The [[id:827bc546-e887-5b7c-9b65-6392beaf0920][verification monopoly]] and [[id:29e4dbf3-cf19-589c-8b14-389e8a39d564][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. diff --git a/ideas/investment-thesis.org b/ideas/investment-thesis.org index 5d3341b..02b7e85 100644 --- a/ideas/investment-thesis.org +++ b/ideas/investment-thesis.org @@ -5,7 +5,7 @@ #+title: Investment Thesis #+filetags: :passepartout:economics:investment:thesis: -The early player benefits from every other instance of the triad. Every deployed instance feeds edge cases into the [[id:45258a2d-1675-562c-9024-5d1eb2f1ea56][regression suite]], grows the [[id:3c6b0449-a8fb-5b89-b82a-34efb21ef5b5][compute marketplace]], and validates the hardware designs. Network effects are positive sum. +The early player benefits from every other instance of Passepartout. Every deployed instance feeds edge cases into the [[id:45258a2d-1675-562c-9024-5d1eb2f1ea56][regression suite]], grows the [[id:3c6b0449-a8fb-5b89-b82a-34efb21ef5b5][compute marketplace]], and validates the hardware designs. Network effects are positive sum. Three revenue horizons: @@ -15,6 +15,6 @@ Three revenue horizons: The [[id:5f55bbe6-d243-5766-8ccf-5c5cc88a6542][impact on the AI and GPU industry]] — token demand compression, GPU inference plateau, and the rise of CPU-native verification hardware — reshapes the trillion-dollar market these revenue streams depend on. -The [[id:68ffa49f-f0d8-42cf-8b69-ae69de8bb815][Agora governance and physical assets]] requirements cover how the network manages shared infrastructure. The switching costs compound. The [[id:aa6d062e-a520-5d14-8773-00687ed9c689][network effects]] are positive sum. The market is nearly a trillion dollars. +The [[id:68ffa49f-f0d8-42cf-8b69-ae69de8bb815][Social protocol governance and physical assets]] requirements cover how the network manages shared infrastructure. The switching costs compound. The [[id:aa6d062e-a520-5d14-8773-00687ed9c689][network effects]] are positive sum. The market is nearly a trillion dollars. The defensible entity is "the organization that best understands how to adapt [[id:28c46769-c14b-42aa-ac7a-69d310157f8f][Passepartout]] to your domain" — not "the organization that owns Passepartout." diff --git a/ideas/legal-structure-alternatives.org b/ideas/legal-structure-alternatives.org index c880c9e..5ca31f5 100644 --- a/ideas/legal-structure-alternatives.org +++ b/ideas/legal-structure-alternatives.org @@ -44,21 +44,21 @@ Wyoming passed HB 185 in 2025 creating the "Decentralized Autonomous Organizatio ** Relevance to This Venture -The [[id:1d074690-a279-59cb-b91d-e9a22ae104ad][Agora]]'s governance modules (liquid democracy, Collective Personas, GEM) map /directly/ onto the DAO LLC concept. If a community on the Agora wants to be a legal entity — own a shared website domain, hold a pooled treasury, sign a contract with a vendor — they could incorporate as a Wyoming DAO LLC. The Agora's existing governance infrastructure (voting, constitutions, role management) becomes the DAO LLC's management mechanism. +The [[id:1d074690-a279-59cb-b91d-e9a22ae104ad][social protocol]]'s governance modules (liquid democracy, Collective Personas, GEM) map /directly/ onto the DAO LLC concept. If a community on the social protocol wants to be a legal entity — own a shared website domain, hold a pooled treasury, sign a contract with a vendor — they could incorporate as a Wyoming DAO LLC. The social protocol's existing governance infrastructure (voting, constitutions, role management) becomes the DAO LLC's management mechanism. ** This Is Not the OpCo or IP Co Structure -The Wyoming DAO LLC is not a replacement for the Delaware/Texas OpCo or the BVI IP Co. It is an offering /for Agora communities/. The communities themselves become legal entities, not just digital spaces. This creates a product feature: +The Wyoming DAO LLC is not a replacement for the Delaware/Texas OpCo or the BVI IP Co. It is an offering /for social protocol communities/. The communities themselves become legal entities, not just digital spaces. This creates a product feature: -- Community in the Agora hits 25 members who pool $5K in dues +- Community in the social protocol hits 25 members who pool $5K in dues - Community clicks "Incorporate as Wyoming DAO LLC" -- The Agora generates the filing (name, registered agent, governance document mapping) +- The social protocol generates the filing (name, registered agent, governance document mapping) - The community's voting modules become the LLC's management structure - The community now holds assets, signs contracts, and has liability protection ** Practical Considerations -Wyoming DAO LLCs are new (2025). Case law is essentially nonexistent. Banks may not open accounts for them. Tax treatment is unclear. But for Agora communities that need legal entity status, it's the least friction option. +Wyoming DAO LLCs are new (2025). Case law is essentially nonexistent. Banks may not open accounts for them. Tax treatment is unclear. But for social protocol communities that need legal entity status, it's the least friction option. * Panama LLC (Sociedad de Responsabilidad Limitada / SRL) diff --git a/ideas/legal-structure-practical-setup.org b/ideas/legal-structure-practical-setup.org index 05f403f..f1f3563 100644 --- a/ideas/legal-structure-practical-setup.org +++ b/ideas/legal-structure-practical-setup.org @@ -19,7 +19,7 @@ Recommended structure: Delaware C-Corp (US OpCo) + BVI Business Company (IP Co). │ owns the IP assets ([[id:28c46769-c14b-42aa-ac7a-69d310157f8f][Passepartout]] code, gate rules, - ACL2 libraries, [[id:1d074690-a279-59cb-b91d-e9a22ae104ad][Agora]] protocol + ACL2 libraries, [[id:1d074690-a279-59cb-b91d-e9a22ae104ad][social protocol]] protocol spec, trademarks, domain names) The OpCo pays the IP Co an arm's-length royalty for the right to use the IP in its business (compliance sales, PDS hosting, marketplace operations). The IP Co accumulates royalty income in a tax-neutral jurisdiction (BVI has 0% corporate tax). The founders own both entities under the same cap table. @@ -125,7 +125,7 @@ A BVI Business Company (IBC) incorporated under the BVI Business Companies Act ( This is the most important document. It must: -1. /Define the IP:/ List every asset being licensed — the Passepartout source code, gate rules, ACL2 proof libraries, Agora protocol specification, trademarks, domain names, trade secrets. This needs to be specific enough for tax authorities but broad enough to cover future developments. +1. /Define the IP:/ List every asset being licensed — the Passepartout source code, gate rules, ACL2 proof libraries, social protocol specification, trademarks, domain names, trade secrets. 2. /Set the royalty rate:/ Must be at arm's-length. For software/tech IP, typical royalty rates are 2-10% of gross revenue, depending on how central the IP is to the business. Verification IP is 100% central to the business (the product /is/ the IP) — rates at the higher end are defensible. @@ -202,4 +202,4 @@ The IP transfer must happen /before/ the IP has significant value. Incorporating - [[id:0a4e0b8f-25e0-4b78-9633-fc37d03cefe9][Asset protection structures — options analysis]] - [[id:98364e9d-a8a9-42b7-a9dc-b643fd2ccc4b][Outbound sales compliance — data protection law]] -- [[id:d28adac8-08a1-40c4-ae43-b5d8d7b1743f][Combined growth strategy — Logos + Agora]] +- [[id:d28adac8-08a1-40c4-ae43-b5d8d7b1743f][Combined growth strategy — Passepartout]] diff --git a/ideas/lisp-machine-security.org b/ideas/lisp-machine-security.org index 6333d13..b46b76a 100644 --- a/ideas/lisp-machine-security.org +++ b/ideas/lisp-machine-security.org @@ -104,5 +104,5 @@ None of this is in the architecture documents. The following are not yet specifi 7. ACL2 trust documentation — the bootstrap chain and what it means for the gate stack's verification 8. The boot attestation protocol — how the gate core verifies the gate stack before loading it 9. -See the [[id:6fe67db6-25bd-4d11-bd1d-b44ec809e858][Agora Identity specification]] for how user identity, key derivation, and DID management integrate with the gate stack's boot chain and privilege zones. +See the [[id:6fe67db6-25bd-4d11-bd1d-b44ec809e858][Social protocol identity specification]] for how user identity, key derivation, and DID management integrate with the gate stack's boot chain and privilege zones. — how many cycles does an ECALL take, and does that affect the 10-80-10 ratio diff --git a/ideas/passepartout-social-protocol-competitive-landscape.org b/ideas/passepartout-social-protocol-competitive-landscape.org new file mode 100644 index 0000000..a7dbf7e --- /dev/null +++ b/ideas/passepartout-social-protocol-competitive-landscape.org @@ -0,0 +1,221 @@ +:PROPERTIES: +:ID: 1bc22b89-d3eb-4f6d-bcfc-2b0c19c8ed8f +:ID: competitive-landscape-agora +:CREATED: [2026-05-23 Sat] +:END: +#+title: Passepartout Social Protocol Competitive Landscape +#+filetags: :passepartout:social-protocol:competitive:strategy:landscape: + +The social protocol is a decentralized social operating system that replaces the entire centralized internet platform stack: every function that currently runs on Facebook, Twitter, Instagram, YouTube, TikTok, Reddit, Medium, Substack, OnlyFans, Pornhub, WhatsApp, Signal, Telegram, Discord, LinkedIn, eBay, Etsy, GitHub, DocuSign, Stripe, and Google/Apple ID — all through one unified identity, one data model (the Note), one communication protocol (DIDComm), one payment rail (Lightning), and one contract layer (SCAL). + +There is no single competitor. The competition is the /category/ of centralized internet platforms and the psychological status quo of managing 15+ separate accounts. + +This page maps every platform the protocol replaces, organized by domain, with the specific protocol capability that makes the replacement possible. + +* Social Graph & Publishing + +** Twitter/X +- *User need:* Broadcast short-form content, follow interesting people, real-time news +- *Social Protocol replacement:* Feeds and streams via the Note primitive (`is_feed: true`), with Lens architecture for customizable curation. Follows are cryptographic subscriptions, not API-gated relationships. +- *Social Protocol advantage:* No algorithmic manipulation, no ads, no shadowbanning. Users choose their Feed Generators via the Algorithm Marketplace. Portable social graph — follows are signed Notes, not a database row. +- *Migration:* Twitter archive import for followed accounts. + +** Facebook / Meta +- *User need:* Social graph, family/friend connections, event management, groups +- *Social Protocol replacement:* Collective Personas for groups, DID-based social graph (not platform-controlled), Persona isolation for work/personal/family +- *Social Protocol advantage:* No central feed algorithm that optimizes for engagement over well-being. Portable identity — your social graph leaves the platform when you do. No data mining. +- *Timing:* Year 3+ after network effects. Facebook's moat is the largest social graph; the protocol's Persona system makes it portable by design. + +** Instagram +- *User need:* Visual content sharing, photo feeds, stories +- *Social Protocol replacement:* Visual Notes with `content_type: image/*`. Lens architecture renders them through an "Instagram-style" grid or a "Pinterest-style" discovery view depending on user-selected Lens. +- *Social Protocol advantage:* User-chosen discovery algorithm. No engagement-maximized feed. Content is not manipulated for ad placement. + +** LinkedIn +- *User need:* Professional identity, job market, professional networking +- *Social Protocol replacement:* Professional Persona (unlinkable from personal), Aletheia Portfolio (static site published natively to the network), Contract Notes for hiring/service agreements +- *Social Protocol advantage:* Portable professional reputation — not locked to a platform. Verified work history via signed Notes. Direct hiring without platform intermediation fees. + +** Reddit / Forums (phpBB, vBulletin) +- *User need:* Community discussion, Q&A, interest-based groups +- *Social Protocol replacement:* Social Spaces with Collective Personas, pluggable feed generation, competitive labeling for moderation +- *Social Protocol advantage:* Sovereign moderation (users choose their Labelers), portable identity across communities, no censorship risk. Communities can fork if the Collective governance fails. +- *Migration:* Import subscribed subreddits. + +** Medium / Substack +- *User need:* Long-form publishing, subscription-based content, creator monetization +- *Social Protocol replacement:* Feed Notes (`is_feed: true`) with paywalled content via LSAT protocol (Lightning Service Authentication Tokens). Subscriptions are streaming Lightning payments. +- *Social Protocol advantage:* Near-zero platform fees (relay costs only). Content ownership — readers subscribe to the creator's DID, not to a platform. No censorship risk. +- *Strategic target:* Phase 1 platform replacement. + +* Video & Audio + +** YouTube +- *User need:* Video hosting, discovery, comments, monetization +- *Social Protocol replacement:* Video Notes (`content_type: video/*`) viewed through a "YouTube Lens" (displaying comments via `reply_to` and related videos). The exact same Note can be viewed through an "Educational Lens" or "Podcast Lens." +- *Social Protocol advantage:* No algorithm that optimizes for watch time over well-being. Lens architecture lets users choose discovery logic. Content monetized via LSAT + Seeder Rewards — creators earn directly, and bandwidth providers (seeders) earn micro-rewards. + +** TikTok +- *User need:* Short-form vertical video, discovery algorithm +- *Social Protocol replacement:* Short-duration video Notes trigger a "TikTok-style" vertical scroll and auto-play in the UI when `content_type: "video/mp4"` and duration is short. +- *Social Protocol advantage:* The "For You" algorithm is a user-chosen Lens, not a platform-controlled black box. No engagement-extremification. + +** Podcasts / Audio +- *User need:* Audio content, background play +- *Social Protocol replacement:* Audio Notes (`content_type: audio/mpeg`) viewed through a "Podcast Lens" with 1.5x speed and background play. Same Note can be listened to or watched depending on Lens. + +* Messaging & Communication + +** WhatsApp / Signal / Telegram +- *User need:* Private messaging, group chats, voice/video calls, encryption +- *Social Protocol replacement:* DIDComm v2 for transport, Double Ratchet Algorithm (Signal Protocol) for Perfect Forward Secrecy, WebRTC for voice/video with decentralized signaling via DIDComm. PDS acts as encrypted mailbox proxy. +- *Social Protocol advantage:* Multi-persona isolation — Work DID and Personal DID have separate message queues that never mix. Onion routing for metadata privacy. Off-the-Record mode for ephemeral interactions. No central server controlling the directory. + +** Discord / Slack +- *User need:* Community chat, voice channels, collaboration +- *Social Protocol replacement:* Social Spaces with Collective Personas. DIDComm-based group messaging. Governance modules (GEM) for roles, permissions, and moderation. +- *Social Protocol advantage:* Server ownership is cryptographic, not corporate. Communities can fork. No per-seat pricing. Portable membership history. + +** Email +- *User need:* Asynchronous messaging, identity, document delivery +- *Social Protocol replacement:* Directed Notes (Copy-on-Send model). PDS as encrypted mailbox. The Note is a universal message format — no separate email protocol needed. +- *Social Protocol advantage:* End-to-end encryption by default. Cryptographic sender verification (no phishing, no spoofing). No spam (relays only route to subscribed destinations). Attachments are CIDs, not MIME blobs. + +** Zoom / Google Meet +- *User need:* Video conferencing, screen sharing +- *Social Protocol replacement:* WebRTC over DIDComm signaling. P2P tunnel — no central server sees call data. +- *Social Protocol advantage:* No Zoom-bombing (call is authenticated by DID). No platform listening in. No account required beyond your DID. + +* E-Commerce & Marketplaces + +** eBay / Etsy +- *User need:* Buy and sell goods, auction, fixed-price listings, dispute resolution +- *Social Protocol replacement:* Contract Notes as product listings (Offer → Take model). HODL invoice escrow for payments. SCAL (Sovereign Contract & Arbitration Layer) for dispute resolution. +- *Social Protocol advantage:* Fees below 5% (vs. 10-15%). Transparent reputation system based on DID history. No account bans. Multi-level arbitration (Local Elders → Guilds → Global Juries). + +** OnlyFans / Patreon / Fansly +- *User need:* Subscription content, adult content, creator-direct monetization +- *Social Protocol replacement:* Paywalled Notes via LSAT protocol. Streaming Lightning subscriptions. Encrypted content with Blind CDN seeding. +- *Social Protocol advantage:* Censorship-resistant (no payment processor can cut you off). Near-zero platform fees. Pseudonymous by default. Adult content doesn't face the banking discrimination that existing platforms do. +- *Strategic target:* Phase 1 platform replacement (underserved, clear pain point). + +** Pornhub / Adult content +- *User need:* Adult content hosting, discovery, monetization +- *Social Protocol replacement:* Same Note primitive with `content_type: video/*`. LSAT for paywalled access. Blind CDN for distribution. +- *Social Protocol advantage:* No centralized moderation that can delist creators. Lightning-native payments bypass banking discrimination. Privacy (identity not tied to consumption). +- *Strategic target:* Phase 1 platform replacement. + +* Work & Collaboration + +** GitHub / GitLab +- *User need:* Version control, code hosting, issues, pull requests, CI +- *Social Protocol replacement:* Code is stored as Merkle DAGs of commit Notes. Issues and PRs are Contract Notes. Collective Personas own repositories. +- *Social Protocol advantage:* Truly decentralized version control — no central repository host. Signed commits with DID. Smart contracts for bounty management (Lightning bounties). + +** Google Docs / Office 365 +- *User need:* Collaborative document editing, spreadsheets, presentations +- *Social Protocol replacement:* Static pages (`is_feed: false`) with versioned CID history. Collaborative editing via Contract Notes defining access control. +- *Social Protocol advantage:* Document history is immutable and verifiable. No platform lock-in. + +** Project Management (Jira, Trello, Asana) +- *User need:* Task tracking, project management, team coordination +- *Social Protocol replacement:* Tasks as Contract Notes in negotiation state. Status changes are signed state transitions. +- *Social Protocol advantage:* Portable project history. Tasks are data you own. + +** Upwork / Fiverr / Freelancer +- *User need:* Find freelancers, manage contracts, escrow payments +- *Social Protocol replacement:* SCAL contracts for service agreements. HODL invoice escrow. Multi-level arbitration. Reputation tied to DID history. +- *Social Protocol advantage:* Lower fees, portable reputation, no platform lock-in. + +* Identity & Infrastructure + +** Google / Apple ID +- *User need:* Single sign-on across the internet +- *Social Protocol replacement:* DID-based authentication via Personas. No central identity provider. User controls which Persona is used for which service. +- *Social Protocol advantage:* No surveillance (Google sees every SSO login). Granular persona isolation. No single point of failure. + +** ENS (Ethereum Name Service) +- *User need:* Human-readable decentralized names +- *Social Protocol replacement:* Social protocol naming registry with similar auction model. But integrated with PDS, messaging, contracts, and payments — a name in the protocol is a full identity, not just a pointer to a wallet. +- *Social Protocol advantage:* Names come with native capabilities (PDS, messaging, contracts). ENS is names-only. + +* The [[id:3aa22300-2f25-57b0-8787-9f199cc978b1][Competitive Analysis]]: What This Changes + +The social protocol is not competing with any single product. It is competing with the /aggregate/ of 20+ products — and the friction of managing 20+ separate accounts, logins, reputations, and data silos. + +** The Real Competitor Is the Status Quo + +The centralized internet works well enough for most people. The friction is spread across 20+ platforms — no single platform is bad enough to leave. The social protocol's value proposition is not "Twitter but better" but "one account replaces every platform you use." + +This is a harder sell because: +1. The status quo is familiar. Switching all 20+ platforms at once is cognitively overwhelming. +2. Network effects at each platform are entrenched. No single platform can be replaced without bringing the users. +3. The value of unification compounds with adoption — but requires critical mass to be visible. + +** The Entry Vector Must Be a Niche, Not a Mass Market + +The strategic documents recognize this explicitly. Phase 1 targets underserved communities with clear pain points: +- OnlyFans creators facing payment discrimination and censorship +- Reddit communities tired of centralized moderation +- Developers frustrated with platform lock-in +- Adult content platforms facing banking discrimination +- NGOs and guilds needing sovereign identity + +Each of these communities has a /specific/ pain point that the protocol solves directly. The win condition is: a user joins for one reason (e.g., censorship-resistant adult content monetization) and discovers the other 19 capabilities as a free bonus. + +** The Structural Advantage Is Unassailable + +No centralized competitor can match the protocol's bundle: +- Meta cannot offer portable identity (it destroys their business model) +- Google cannot offer private messaging (it destroys their data model) +- Stripe cannot offer contracts and social (outside their competence) +- DocuSign cannot offer payments and publishing (outside their competence) +- The entire category of centralized platforms cannot offer user-owned data + +The only way to compete with the protocol is to build a similar decentralized platform — and that requires matching all four layers (identity, publishing, payments, contracts) simultaneously. No decentralized project has done this. The closest (Farcaster) has identity and social but no payments or contracts. Bluesky has identity and social but no payments or contracts. Ethereum + ENS has identity, payments, and contracts but no social layer. + +** The Risk Is Not Competition but Indifference + +The protocol's biggest risk is not that a competitor builds a better product, but that the status quo friction is tolerable enough that users never switch. The centralized internet is bad — but it is familiar. The protocol is better — but unfamiliar. + +The counterargument: this is true for every platform shift. Email was a worse experience than postal mail in 1992. The web was a worse experience than AOL in 1994. Instagram was a worse experience than Flickr in 2010. Each won because a /specific/ use case was dramatically better, and the rest of the ecosystem followed. The protocol must find its "camera with filters" moment — the one use case that is so clearly superior that users adopt it despite the rest of the ecosystem being immature. + +* Comparison Summary + +|| Social Protocol replaces | Incumbent | Social Protocol advantage | Risk to Social Protocol | +|----------------+-----------+----------------+---------------| +| Social graph | Facebook | Portable identity, no data mining | Facebook's 3B user moat | +| Microblogging | Twitter/X | Algorithm choice, no censorship | Network effects | +| Visual content | Instagram | No engagement-extremified algorithm | UX polish gap | +| Professional | LinkedIn | Portable rep, no platform fees | Professional network effects | +| Video | YouTube | Lens choice, Seeder Rewards | Content moderation surface | +| Short video | TikTok | Users choose the algorithm | Discovery algorithm sophistication | +| Forums | Reddit | Sovereign moderation, portable identity | Community migration inertia | +| Publishing | Medium/Substack | Near-zero fees, content ownership | Creator distribution | +| Messaging | WhatsApp/Signal | Multi-persona isolation, onion routing | Friend network effects | +| Community | Discord | Cryptographic ownership, forkable | Voice/UX maturity | +| E-commerce | eBay/Etsy | <5% fees, transparent reputation | Trust in new platform | +| Subscription | OnlyFans/Patreon | No payment discrimination | Creator acquisition cost | +| Video hosting | Pornhub | No censorship, Lightning payouts | Reputation risk | +| Code hosting | GitHub | Truly decentralized, DID-signed commits | Developer habit | +| Identity | Google/Apple ID | No surveillance, persona isolation | Convenience of SSO | +| Naming | ENS | Name + PDS + messaging + contracts | ENS's 2M domain moat | +| Collaboration | Google Docs | Verifiable history, no platform lock-in | Real-time collaboration UX | +| Freelance | Upwork/Fiverr | Lower fees, portable reputation | Liquidity of gig listings | +| Meetings | Zoom | P2P, no central server | Call quality/reliability | + +* Conclusion + +The protocol does not compete with any single platform. It offers an alternative to the /entire paradigm/ of centralized internet services. The competitive analysis is not about which platform to beat — it is about which /use case/ to lead with so that users adopt the unified platform despite the rest of the ecosystem being immature. + +The OnlyFans/Patreon entry vector is the strongest Phase 1 play: a community with clear pain (payment discrimination, censorship), high willingness to pay, and low switching costs (creators want their audience independent of the platform). From there, publishing, messaging, and identity flow naturally. + +* References + +- [[id:1d074690-a279-59cb-b91d-e9a22ae104ad][Social Protocol overview]] (brain docs) +- [[id:64708e1f-00e9-4cb7-b44b-ea0b98e5296d][Social Protocol contract platform]] +- [[id:57f9538a-6270-4302-8d07-d742168419eb][Social-first growth scenario]] +- Social Protocol Overview (spec repo) +- Social Space specification +- Exchange and Contracts specification +- User journey and platform replacement strategy diff --git a/ideas/agora-contracts.org b/ideas/passepartout-social-protocol-contracts.org similarity index 67% rename from ideas/agora-contracts.org rename to ideas/passepartout-social-protocol-contracts.org index e6aa9ac..4b1336b 100644 --- a/ideas/agora-contracts.org +++ b/ideas/passepartout-social-protocol-contracts.org @@ -3,19 +3,19 @@ :ID: agora-contracts :CREATED: [2026-05-23 Sat] :END: -#+title: Agora — Smart Contracts and the Contract Marketplace -#+filetags: :passepartout:agora:contracts:revenue:smart-contracts: +#+title: Passepartout Social Protocol — Smart Contracts and the Contract Marketplace +#+filetags: :passepartout:social-protocol:contracts:revenue:smart-contracts: -Agora's infrastructure — DIDs (identity), DIDComm (communication), PDS (state), gate rules (logic), ACL2 (verification) — together form a full smart contract platform. Every piece is already in the architecture. This page describes what contracts are possible, how they generate revenue, and why Agora's approach is structurally stronger than existing platforms. +The social protocol's infrastructure — DIDs (identity), DIDComm (communication), PDS (state), gate rules (logic), ACL2 (verification) — together form a full smart contract platform. Every piece is already in the architecture. This page describes what contracts are possible, how they generate revenue, and why the social protocol's approach is structurally stronger than existing platforms. -* Why Agora Contracts Are Different +* Why Social Protocol Contracts Are Different -Existing smart contract platforms (Ethereum, Solana, Cosmos) verify only that execution followed the rules. Agora's ACL2 prover verifies that the /rules themselves/ are correct with respect to a formal specification. This is strictly stronger: +Existing smart contract platforms (Ethereum, Solana, Cosmos) verify only that execution followed the rules. The social protocol's ACL2 prover verifies that the /rules themselves/ are correct with respect to a formal specification. This is strictly stronger: - Ethereum: The contract ran according to the EVM bytecode (execution validity) -- Agora: The contract is correct with respect to its specification, AND it ran correctly (correctness + execution) +- Social Protocol: The contract is correct with respect to its specification, AND it ran correctly (correctness + execution) -This means Agora contracts can encode real-world regulations ([[id:84fb5f8f-0527-4df0-b6b6-dbf3bcff8a7f][HIPAA]], [[id:ed65031c-cbd2-4ad2-bd53-a67791e183cd][SOC2]], [[id:513d5996-4ac7-4567-a992-18fc01599104][GDPR]]) as gate rules and prove that a contract execution satisfies them. No existing platform does this. +This means social protocol contracts can encode real-world regulations ([[id:84fb5f8f-0527-4df0-b6b6-dbf3bcff8a7f][HIPAA]], [[id:ed65031c-cbd2-4ad2-bd53-a67791e183cd][SOC2]], [[id:513d5996-4ac7-4567-a992-18fc01599104][GDPR]]) as gate rules and prove that a contract execution satisfies them. No existing platform does this. * What Contracts Enable @@ -31,11 +31,11 @@ How it works: Revenue: Transaction fee per contract execution in the [[id:3c6b0449-a8fb-5b89-b82a-34efb21ef5b5][compute marketplace]], deployment fee per verified contract, premium for certification weight. -Comparison: Ethereum collects ~$20B/yr in transaction fees. Agora's verifiably correct contracts target the same market with a stronger value proposition. The limitation is liquidity, not technology — network effects determine adoption. +Comparison: Ethereum collects ~$20B/yr in transaction fees. The social protocol's verifiably correct contracts target the same market with a stronger value proposition. The limitation is liquidity, not technology — network effects determine adoption. ** 2. Multi-Instance Governance Contracts -Organizations running multiple triad instances need contracts that span instances: cross-instance policy, unified compliance, federated identity. +Organizations running multiple Passepartout instances need contracts that span instances: cross-instance policy, unified compliance, federated identity. Use cases: - Enterprise: all instances in the finance department must apply the [[id:c9830152-0160-4bdc-ab03-6f308ad43536][SOX]] gate rule set @@ -46,7 +46,7 @@ Revenue: Enterprise governance tier (annual license), per-instance fee. ** 3. Liquid Democracy Infrastructure -Agora's liquid democracy enables delegation-based voting where votes can be transferred and proxies can be verified. +The social protocol's liquid democracy enables delegation-based voting where votes can be transferred and proxies can be verified. Use cases: - DAO governance (token-weighted or identity-weighted voting) @@ -99,7 +99,7 @@ Revenue: Commission per lease transaction, auction fees for contested names, pre ** 8. Dispute Resolution -When two Agora instances disagree on a contract execution, submit to a verified arbitrator. The arbitrator runs the contract in their own [[id:28c46769-c14b-42aa-ac7a-69d310157f8f][Passepartout]] and the proof log resolves the ambiguity unambiguously — the dispute is about facts, not interpretations, because the contract terms are formal gate rules. +When two social protocol instances disagree on a contract execution, submit to a verified arbitrator. The arbitrator runs the contract in their own [[id:28c46769-c14b-42aa-ac7a-69d310157f8f][Passepartout]] and the proof log resolves the ambiguity unambiguously — the dispute is about facts, not interpretations, because the contract terms are formal gate rules. Revenue: Fee per resolution, premium for reputation-weighted arbitration (arbitrators with long track records charge more). @@ -109,7 +109,7 @@ Revenue: Fee per resolution, premium for reputation-weighted arbitration (arbitr |----------+-----------+--------------+-------+------------| | Smart contracts (general) | $20B/yr (Ethereum) | Transaction fees | End State | Installed base | | Contract templates | New market | Per-template sale | Zero | Gate rule SDK | -| Governance (multi-instance) | New market | Annual license | Zero | [[id:c3b3dc41-945f-54e9-84eb-ca014114f1be][Stoa]] premium | +| Governance (multi-instance) | New market | Annual license | Zero | [[id:c3b3dc41-945f-54e9-84eb-ca014114f1be][Environment subsystem]] premium | | Liquid democracy | New market | Per-vote fee | End State | Installed base | | Attestation | New market | Per-attestation | Zero | DID registry | | Insurance marketplace | $1T+ (global insurance) | Premiums | End State | Installed base + capital | @@ -117,7 +117,7 @@ Revenue: Fee per resolution, premium for reputation-weighted arbitration (arbitr | Namespace sub-leasing | Small | Commission | Zero | Username registry | | Dispute resolution | New market | Per-resolution | End State | Installed base | -Key insight: Contract templates, attestation, and multi-instance governance can ship in Phase Zero. They require only the existing Agora infrastructure (DIDs, PDS, gate rules) — no full Lisp Machine needed. These seed the contract economy before the smart contract platform ships. +Key insight: Contract templates, attestation, and multi-instance governance can ship in Phase Zero. They require only the existing social protocol infrastructure (DIDs, PDS, gate rules) — no full Lisp Machine needed. These seed the contract economy before the smart contract platform ships. * Relationship to Compute Marketplace @@ -128,13 +128,13 @@ The compute marketplace and the contract platform reinforce each other: - Attestation bridges them: a compute provider's track record is a verifiable contract history - Insurance prices compute risk based on attestation -The triad's network effects compound when all three layers (compute, contracts, attestation) are active simultaneously. Any one layer without the others is weaker — together they create the [[id:827bc546-e887-5b7c-9b65-6392beaf0920][verification monopoly]]. +Passepartout's network effects compound when all three layers (compute, contracts, attestation) are active simultaneously. Any one layer without the others is weaker — together they create the [[id:827bc546-e887-5b7c-9b65-6392beaf0920][verification monopoly]]. * References -- [[id:1d074690-a279-59cb-b91d-e9a22ae104ad][Agora overview]] +- [[id:1d074690-a279-59cb-b91d-e9a22ae104ad][Social Protocol overview]] - [[id:2e390c1d-65f3-5fb3-b898-ac3fc4291ee7][Premium username registry]] - [[id:1a2b38df-20ba-58ca-ba55-a072be67bd0d][PDS as a service]] - [[id:3c6b0449-a8fb-5b89-b82a-34efb21ef5b5][Compute marketplace]] - [[id:ed05cab4-88e9-4e25-b7c9-346fa39c69a0][Revenue streams overview]] -- [[id:827bc546-e887-5b7c-9b65-6392beaf0920][The [[id:90484f4a-5b70-4001-93d6-e610e54ed573][Agora Exchange requirements]] specify the contract and exchange layer in detail. [[id:827bc546-e887-5b7c-9b65-6392beaf0920][Verification monopoly]]]] +- [[id:827bc546-e887-5b7c-9b65-6392beaf0920][The [[id:90484f4a-5b70-4001-93d6-e610e54ed573][Social Protocol Exchange requirements]] specify the contract and exchange layer in detail. [[id:827bc546-e887-5b7c-9b65-6392beaf0920][Verification monopoly]]]] diff --git a/ideas/agora-entry-strategy.org b/ideas/passepartout-social-protocol-entry-strategy.org similarity index 81% rename from ideas/agora-entry-strategy.org rename to ideas/passepartout-social-protocol-entry-strategy.org index 2fccd0b..493a48b 100644 --- a/ideas/agora-entry-strategy.org +++ b/ideas/passepartout-social-protocol-entry-strategy.org @@ -3,10 +3,10 @@ :ID: agora-entry-strategy :CREATED: [2026-05-23 Sat] :END: -#+title: Agora Entry Strategy — Finding the Low-Hanging Use Cases -#+filetags: :passepartout:agora:strategy:entry:go-to-market: +#+title: Passepartout Social Protocol Entry Strategy — Finding the Low-Hanging Use Cases +#+filetags: :passepartout:social-protocol:strategy:entry:go-to-market: -The Agora replaces 20+ centralized platforms across social, publishing, video, messaging, e-commerce, contracts, and identity. But attempting to launch all at once guarantees failure — the cold start problem kills any network that requires everything to work before anything is useful. +The social protocol replaces 20+ centralized platforms across social, publishing, video, messaging, e-commerce, contracts, and identity. But attempting to launch all at once guarantees failure — the cold start problem kills any network that requires everything to work before anything is useful. This page identifies the entry points that require the least technical maturity, target the most acute pain, and demonstrate the full bundle (identity + content + payments + contracts + governance) as early as possible. @@ -20,7 +20,7 @@ Any viable entry point must score well on all three axes: Plus a fourth that emerges from the discussion: -4. /Bundle necessity/ — does this use case require multiple layers at once, or does one layer suffice? Entry points that only use identity + content teach users a narrow view of the Agora. Entry points that force the bundle (identity + content + payments + contracts + governance) demonstrate the /real/ product. +4. /Bundle necessity/ — does this use case require multiple layers at once, or does one layer suffice? Entry points that only use identity + content teach users a narrow view of the social protocol. Entry points that force the bundle (identity + content + payments + contracts + governance) demonstrate the /real/ product. * Candidate Entry Points Ranked @@ -30,7 +30,7 @@ Plus a fourth that emerges from the discussion: /Pain::/ Today they use a patchwork: Reddit or Discord for communication, Google Sheets for resource tracking, Venmo for dues, DocuSign for agreements, Trello for tasks, Zoom for meetings. /Five separate tools with no unified identity, no shared reputation, no portable history./ When leadership changes, everything breaks — the new treasurer has to recreate the spreadsheet, the new mod inherits a Discord server they don't control. -/Density:/ Very high. These groups /already exist/ as organized units. You don't need to build a social graph — the social graph is the group. If an HOA of 200 families joins the Agora, all 200 arrive at once. +/Density:/ Very high. These groups /already exist/ as organized units. You don't need to build a social graph — the social graph is the group. If an HOA of 200 families joins the protocol, all 200 arrive at once. /Tech needed:/ Moderate. Needs: - Identity (Personas, PDS for each member) @@ -41,7 +41,7 @@ Plus a fourth that emerges from the discussion: /Bundle necessity:/ High. This use case /requires/ the bundle. A group chat alone doesn't solve the problem. They need identity + communication + tasks + payments + governance all in one place, with a unified data model. -/Why this is low-hanging:/ The group already exists. The switching costs are low because the alternative is five separate tools that don't integrate. The Agora doesn't need to be better than Discord at chat — it needs to be better than /Discord + Sheets + Venmo + Trello/ combined, which is a much lower bar. +/Why this is low-hanging:/ The group already exists. The switching costs are low because the alternative is five separate tools that don't integrate. The social protocol doesn't need to be better than Discord at chat — it needs to be better than /Discord + Sheets + Venmo + Trello/ combined, which is a much lower bar. /Killer demo:/ "Your HOA needs a new roof. A member proposes it in a feed post. The treasurer issues a payment request as a Contract Note. 180 families vote via quadratic voting, 150 approve. The contract auto-collects dues via Lightning, issues the payment to the contractor with a HODL invoice escrow, and the contractor's proof of completion releases the funds. Every step is signed, timestamped, and auditable. No spreadsheets, no separate bank accounts, no chasing checks." @@ -57,7 +57,7 @@ Plus a fourth that emerges from the discussion: /Bundle necessity:/ Low-medium. They join for one reason (surviving as a community) and can discover the rest later. But the migration is urgent enough that they adopt with minimal features. -/Risk:/ They might leave when the crisis passes. But if they've built reputation, pooled resources, and documented decisions on the Agora during their refuge, the switching cost to go back is real. +/Risk:/ They might leave when the crisis passes. But if they've built reputation, pooled resources, and documented decisions on the social protocol during their refuge, the switching cost to go back is real. ** 3. Adult Creators / OnlyFans Refugees (highest willingness to pay) @@ -93,7 +93,7 @@ Plus a fourth that emerges from the discussion: /Pain:/ Low-medium. GitHub works well. The pain is ideological (dependency on Microsoft) more than practical. -/Density:/ High. Developer communities are well-connected and migrate together (e.g., a popular repo moving to the Agora brings all contributors). +/Density:/ High. Developer communities are well-connected and migrate together (e.g., a popular repo moving to the social protocol brings all contributors). /Tech needed:/ Low-medium. Merkle DAGs for code, Contract Notes for issues/PRs, Lightening for bounties. @@ -112,7 +112,7 @@ Go-to-market: - Onboard each as a Collective Persona with one onboarding session - The community admin invites members via DID (email link, QR code, share code) - Members arrive to find a fully set-up community space: announcement feed, group chat, task board, treasury, voting -- The first "killer demo" happens naturally when the community's first real decision is conducted through the Agora +- The first "killer demo" happens naturally when the community's first real decision is conducted through the protocol KPI: Number of organized communities. Community retention rate. Contract volume (tasks, dues, votes). @@ -124,10 +124,10 @@ Why second: highest density per event, but needs Phase 1 to have a working produ Go-to-market: - Monitor deplatforming events. When a subreddit of 10K+ users gets banned, the community is actively looking — outreach within 24 hours -- Offer a ready-made Agora community space with import tools (archive of the banned sub, migration guide) +- Offer a ready-made social protocol community space with import tools (archive of the banned sub, migration guide) - The Mod Collective Persona concept lets the migrated community feel familiar: same mods, same rules, same culture — just sovereign -Risk: These communities might not stay. Mitigation: make the Agora community space good enough that they don't want to leave. The mod tools, governance modules, and integrated payments give them capabilities Reddit never had. +Risk: These communities might not stay. Mitigation: make the community space good enough that they don't want to leave. The mod tools, governance modules, and integrated payments give them capabilities Reddit never had. ** Phase 2b: Adult Creators (revenue track) @@ -138,7 +138,7 @@ Why parallel: highest ARPU, fastest path to revenue. Requires LSAT implementatio Go-to-market: - Find 5-10 creators who have been deplatformed or are vocally anti-OnlyFans - Offer a white-glove migration: set up their PDS, import their content archive, configure their subscription tiers -- The creator posts to their existing audience: "I'm now on Agora. Join me here." +- The creator posts to their existing audience: "I'm now on the social protocol. Join me here." - Their audience follows. 1K paying subscribers at $10/mo = $120K/yr on the platform. ** Phase 3: Freelancers / Gig Workers @@ -160,9 +160,9 @@ Why last: needs the full SCAL stack, arbitration guilds with track records, and * The Thesis -The Agora does not need millions of users to prove its value. It needs /one organized community/ to use the full bundle and see what happens. When an HOA of 200 families votes on the budget, collects dues via Lightning, and executes a roof contract with HODL escrow — all in one platform, all verified — the demo sells itself. +The social protocol does not need millions of users to prove its value. It needs /one organized community/ to use the full bundle and see what happens. When an HOA of 200 families votes on the budget, collects dues via Lightning, and executes a roof contract with HODL escrow — all in one platform, all verified — the demo sells itself. -Organized communities are the entry point because they force the Agora to be the /entire/ product from day one, not just another social app. The group that joins for communication stays because of contracts, pays because of Lightning, and governs because of the modules. That is the full vision, delivered to one group at a time. +Organized communities are the entry point because they force the protocol to be the /entire/ product from day one, not just another social app. The group that joins for communication stays because of contracts, pays because of Lightning, and governs because of the modules. That is the full vision, delivered to one group at a time. * Summary Table @@ -176,8 +176,8 @@ Organized communities are the entry point because they force the Agora to be the * References -- [[id:1d074690-a279-59cb-b91d-e9a22ae104ad][Agora overview]] -- Agora Protocol Overview — Platform Replacement Strategy +- [[id:1d074690-a279-59cb-b91d-e9a22ae104ad][Social Protocol overview]] +- Social Protocol Platform Replacement Strategy - Social Space — Collective Personas and Governance - Exchange and Contracts — SCAL, Escrow, Arbitration - [[id:57f9538a-6270-4302-8d07-d742168419eb][Social-first growth scenario]] diff --git a/ideas/agora-usernames.org b/ideas/passepartout-social-protocol-usernames.org similarity index 90% rename from ideas/agora-usernames.org rename to ideas/passepartout-social-protocol-usernames.org index cbc14d9..4a1c508 100644 --- a/ideas/agora-usernames.org +++ b/ideas/passepartout-social-protocol-usernames.org @@ -2,8 +2,8 @@ :CREATED: [2026-05-24 Sun] :ID: 2e390c1d-65f3-5fb3-b898-ac3fc4291ee7 :END: -#+title: Premium Username Registry on Agora -#+filetags: :passepartout:agora:revenue:names:registry: +#+title: Premium Username Registry on Passepartout Social Protocol +#+filetags: :passepartout:social-protocol:revenue:names:registry: The DID system is permissionless — anyone generates their own DID via HD key derivation. But human-readable @handles (short names, common words, brand names) are naturally scarce. The early player controls the namespace registry. diff --git a/ideas/agora.org b/ideas/passepartout-social-protocol.org similarity index 74% rename from ideas/agora.org rename to ideas/passepartout-social-protocol.org index d421a2c..3515ec7 100644 --- a/ideas/agora.org +++ b/ideas/passepartout-social-protocol.org @@ -2,10 +2,10 @@ :CREATED: [2026-05-24 Sun] :ID: 1d074690-a279-59cb-b91d-e9a22ae104ad :END: -#+title: Agora — The Society (Decentralized Network) -#+filetags: :passepartout:agora:network:dids: +#+title: Passepartout Social Protocol — The Society (Decentralized Network) +#+filetags: :passepartout:social-protocol:network:dids: -Agora is the decentralized identity and communication layer that connects [[id:28c46769-c14b-42aa-ac7a-69d310157f8f][Passepartout]] instances: +Passepartout Social Protocol is the decentralized identity and communication layer that connects [[id:28c46769-c14b-42aa-ac7a-69d310157f8f][Passepartout]] instances: - **Self-sovereign identity** via HD key derivation (BIP-44) - **Encrypted messaging** via DIDComm (agent-to-agent and agent-to-human) @@ -15,9 +15,9 @@ Agora is the decentralized identity and communication layer that connects [[id:2 - **[[id:3c6b0449-a8fb-5b89-b82a-34efb21ef5b5][Compute marketplace]]** where instances offer symbolic engine capacity - **Contracts and liquid democracy** infrastructure -The PDS is Passepartout's in-process memory — the Merkle tree, the fact store, the memory-objects. Every memory-object already has a SHA-256 hash, which maps directly to Agora's CIDv1 content addressing. +The PDS is Passepartout's in-process memory — the Merkle tree, the fact store, the memory-objects. Every memory-object already has a SHA-256 hash, which maps directly to the social protocol's CIDv1 content addressing. -Revenue paths from Agora: +Revenue paths from the social protocol: - [[id:2e390c1d-65f3-5fb3-b898-ac3fc4291ee7][Premium username registry]] — $10M/yr at scale - [[id:1a2b38df-20ba-58ca-ba55-a072be67bd0d][PDS as a service]] — $18M/yr at scale - [[id:3c6b0449-a8fb-5b89-b82a-34efb21ef5b5][Compute marketplace]] — venture-scale diff --git a/ideas/agora/agora-requirements-00-readme.org b/ideas/passepartout-social-protocol/requirements-00-readme.org similarity index 80% rename from ideas/agora/agora-requirements-00-readme.org rename to ideas/passepartout-social-protocol/requirements-00-readme.org index 1f24852..80cd271 100644 --- a/ideas/agora/agora-requirements-00-readme.org +++ b/ideas/passepartout-social-protocol/requirements-00-readme.org @@ -1,4 +1,4 @@ -#+title: Agora: Decentralized Social Network +#+title: Social Protocol: Decentralized Social Network #+AUTHOR: Amr #+CREATED: [2026-03-17 Tue] #+BEGIN_COMMENT @@ -9,13 +9,13 @@ A decentralized social network protocol for the ATmosphere (AT Protocol) ecosyst :CREATED: [2026-05-24 Sun] :ID: 10289e64-a4ff-4c34-828f-f3a9c769b73d :END: -* [[id:1d074690-a279-59cb-b91d-e9a22ae104ad][Agora]]: Decentralized Social Network +* [[id:1d074690-a279-59cb-b91d-e9a22ae104ad][Social Protocol]]: Decentralized Social Network This project contains the specification and analysis for a decentralized social network built on open protocols. * Project Tasks -See the actionable tasks for this project in GTD.org (Agora project) +See the actionable tasks for this project in GTD.org (Social Protocol project) * Key Documents diff --git a/ideas/agora/agora-requirements-01-overview.org b/ideas/passepartout-social-protocol/requirements-01-overview.org similarity index 69% rename from ideas/agora/agora-requirements-01-overview.org rename to ideas/passepartout-social-protocol/requirements-01-overview.org index 570ebc9..b8876c1 100644 --- a/ideas/agora/agora-requirements-01-overview.org +++ b/ideas/passepartout-social-protocol/requirements-01-overview.org @@ -1,4 +1,4 @@ -#+title: Agora Requirements - 01: Protocol Overview and Foundational Principles +#+title: Social Protocol Requirements - 01: Protocol Overview and Foundational Principles #+author: Amero Garcia #+created: [2026-03-19 Thu 21:07] #+DATE: 2026-03-20 @@ -9,63 +9,63 @@ :CREATED: [2026-05-24 Sun] :ID: b25bf753-9799-41ab-82f5-1a1416db756b :END: -* 1. Introduction to the [[id:1d074690-a279-59cb-b91d-e9a22ae104ad][Agora]] Protocol +* 1. Introduction to the [[id:1d074690-a279-59cb-b91d-e9a22ae104ad][Social Protocol]] -The Agora Protocol defines a novel architecture for decentralized digital interaction. Its primary objective is to replace extractive, centralized platforms—the era of *"Digital Feudalism"* where corporations own user data and control visibility via secret algorithms—with a decentralized *"Social Operating System"* that provides Identity, Justice, and Commerce for sovereign individuals and communities. +The social protocol defines a novel architecture for decentralized digital interaction. Its primary objective is to replace extractive, centralized platforms—the era of *"Digital Feudalism"* where corporations own user data and control visibility via secret algorithms—with a decentralized *"Social Operating System"* that provides Identity, Justice, and Commerce for sovereign individuals and communities. -Agora returns power to the edges by providing a modular protocol stack where trust is cryptographic, privacy is inherent, and freedom is architectural. This document provides a comprehensive overview of Agora's foundational principles, core technical differentiators, and a detailed exploration of its capabilities across various use cases, including communication, content creation, e-commerce, collaboration, and liquid democracy. It serves as a high-level technical summary, articulating the design philosophy and the synergistic effects of its integrated components. +The protocol returns power to the edges by providing a modular protocol stack where trust is cryptographic, privacy is inherent, and freedom is architectural. This document provides a comprehensive overview of the protocol's foundational principles, core technical differentiators, and a detailed exploration of its capabilities across various use cases, including communication, content creation, e-commerce, collaboration, and liquid democracy. It serves as a high-level technical summary, articulating the design philosophy and the synergistic effects of its integrated components. * 2. Foundational Principles -Agora's design is predicated upon a set of core principles that collectively ensure a robust, user-centric [[id:1d074690-a279-59cb-b91d-e9a22ae104ad][decentralized network]]. +The protocol's design is predicated upon a set of core principles that collectively ensure a robust, user-centric [[id:1d074690-a279-59cb-b91d-e9a22ae104ad][decentralized network]]. ** 2.1. User Sovereignty and Data Ownership -Central to Agora is the tenet of user sovereignty. Unlike centralized paradigms where platforms intermediate and often monetize user data, Agora's architecture ensures that all user-generated content and personal data are exclusively owned and controlled by the originating user. This is achieved through client-side encryption, self-hosted or user-controlled Personal Data Stores (PDS), and audience-defined access controls (`access_control`). +Central to the protocol is the tenet of user sovereignty. Unlike centralized paradigms where platforms intermediate and often monetize user data, the protocol's architecture ensures that all user-generated content and personal data are exclusively owned and controlled by the originating user. This is achieved through client-side encryption, self-hosted or user-controlled Personal Data Stores (PDS), and audience-defined access controls (`access_control`). ** 2.2. Decentralization and Censorship Resistance -The protocol is designed to eliminate single points of failure and control. By distributing data storage across user-controlled PDSs and routing communication through a permissionless Relay Network, Agora inherently resists censorship and external manipulation. There is no central authority capable of unilaterally restricting access, altering content, or deplatforming users. +The protocol is designed to eliminate single points of failure and control. By distributing data storage across user-controlled PDSs and routing communication through a permissionless Relay Network, the protocol inherently resists censorship and external manipulation. There is no central authority capable of unilaterally restricting access, altering content, or deplatforming users. ** 2.3. Authenticity and Verifiability -Every action and piece of content within Agora is cryptographically signed by the originating Persona. This provides an immutable and auditable record, ensuring the authenticity and integrity of all interactions. The content-addressed nature of all data, via Content Identifiers (CIDs), guarantees that content cannot be altered without changing its unique identifier, thereby establishing verifiable provenance. +Every action and piece of content within the protocol is cryptographically signed by the originating Persona. This provides an immutable and auditable record, ensuring the authenticity and integrity of all interactions. The content-addressed nature of all data, via Content Identifiers (CIDs), guarantees that content cannot be altered without changing its unique identifier, thereby establishing verifiable provenance. ** 2.4. Privacy by Design -Agora incorporates privacy-enhancing technologies at every layer. End-to-end encryption is a default for private communications, and mechanisms such as Blinded Sharding for social recovery and "Off-the-Record" modes for ephemeral interactions are integrated to minimize metadata leakage and ensure user confidentiality. +The protocol incorporates privacy-enhancing technologies at every layer. End-to-end encryption is a default for private communications, and mechanisms such as Blinded Sharding for social recovery and "Off-the-Record" modes for ephemeral interactions are integrated to minimize metadata leakage and ensure user confidentiality. * 3. Core Technical Differentiators -Agora's unique capabilities stem from the synergistic integration of three primary technical differentiators: The Note Primitive, Self-Sovereign Identity (Personas and Master Key), and a Distributed Infrastructure (PDS and Relay Network). +The protocol's unique capabilities stem from the synergistic integration of three primary technical differentiators: The Note Primitive, Self-Sovereign Identity (Personas and Master Key), and a Distributed Infrastructure (PDS and Relay Network). ** 3.1. The Note Primitive: Atomic Unit of Information -At the heart of Agora's data model is the "Note"—the atomic, universal unit of information. Every piece of content or interaction within the protocol, regardless of its semantic meaning (e.g., a social post, a message, a contract, an encyclopedia entry, a product listing), is encapsulated within a Note. +At the heart of the protocol's data model is the "Note"—the atomic, universal unit of information. Every piece of content or interaction within the protocol, regardless of its semantic meaning (e.g., a social post, a message, a contract, an encyclopedia entry, a product listing), is encapsulated within a Note. For a comprehensive technical breakdown of the Note's structure, cryptographic hashing, and content flag schema, see *[[id:f6cfc54b-919b-4311-bcbf-65e976755d40][04: The Primitive]]*. *** 3.1.2. Benefits of the Unified Note Primitive The "Everything is a Note" paradigm yields significant architectural advantages: -- *Universal Interoperability:* A single, standardized data model allows any Agora-compatible client application to understand and process any Note, fostering an open ecosystem where diverse applications can seamlessly interact. +- *Universal Interoperability:* A single, standardized data model allows any compatible client application to understand and process any Note, fostering an open ecosystem where diverse applications can seamlessly interact. - *Immutable Audit Trail:* The content-addressed and signed nature of Notes inherently creates an unalterable, verifiable history of all digital interactions and content evolution. - *Simplified Development:* Developers can focus on application-layer semantics and user experience, leveraging a robust and consistent underlying data primitive. ** 3.2. Self-Sovereign Identity: Personas and the Master Key -Agora's identity system grants users absolute control over their digital presence, leveraging Hierarchical Deterministic (HD) cryptography to derive and manage multiple functional identities. +The protocol's identity system grants users absolute control over their digital presence, leveraging Hierarchical Deterministic (HD) cryptography to derive and manage multiple functional identities. *** 3.2.1. The Master Key (Anima) -The Master Key serves as the absolute root of a user's digital being within Agora. +The Master Key serves as the absolute root of a user's digital being within the protocol. - *Root of Trust:* A single, securely generated and stored secret seed from which all other identities are derived. - *Hierarchical Derivation:* Utilizes a BIP-44 compatible HD derivation path (`m/44'/1'/account'/persona'/key_purpose/key_index`) to generate an infinite number of unlinkable Personas, each acting as a sovereign sub-root for its own functional keys. - *Secure Storage:* Recommended for offline storage or within [[id:84a537b4-4256-50c8-91f5-dd5b4538418f][Hardware]] Security Modules (HSMs) to ensure maximum protection. *** 3.2.2. Personas: Functional Digital Identities -Personas are the active, functional identities through which users interact with the Agora network. +Personas are the active, functional identities through which users interact with the protocol network. - *Distinct Identities:* Each Persona represents a distinct Decentralized Identifier (DID), allowing users to maintain separate digital roles (e.g., personal, professional, anonymous) with granular control. - *Key Management:* Each Persona possesses its own signing and encryption keypairs, which can be revoked or rotated independently without affecting the Master Key or other Personas. - *Asset Ownership & Rights:* Personas are analogous to legal entities, capable of owning digital assets (e.g., Bitcoin wallets), entering into binding contracts, and claiming protected rights such as due process and freedom of expression. @@ -79,7 +79,7 @@ Personas are the active, functional identities through which users interact with ** 3.3. Distributed Infrastructure: PDS, Relays, and Thin Clients -Agora's infrastructure is specifically engineered to underpin user sovereignty, data ownership, and censorship resistance. +The protocol's infrastructure is specifically engineered to underpin user sovereignty, data ownership, and censorship resistance. *** 3.3.1. Personal Data Store (PDS): The User's Digital Vault @@ -87,29 +87,29 @@ The PDS is the central component for data ownership, acting as the user's sovere - *Exclusive Control:* Every user controls their own PDS, whether self-hosted or through a trusted provider. - *Master Archive:* Stores all user content (client-side encrypted) and identity data. - *Access Gatekeeper:* Enforces access control, issuing decryption keys based on validated credentials or payments. -- *PDS-as-a-Service:* Services can integrate seamlessly, offering free sign-ups with grace periods and requiring in-Agora payments (e.g., Lightning) for continued service, bypassing traditional financial intermediaries. +- *PDS-as-a-Service:* Services can integrate seamlessly, offering free sign-ups with grace periods and requiring in-protocol payments (e.g., Lightning) for continued service, bypassing traditional financial intermediaries. *** 3.3.2. Relay Network: The Intelligent Communication Backbone -The Relay Network forms the intelligent communication backbone of Agora, efficiently routing encrypted Notes between Personas. +The Relay Network forms the intelligent communication backbone of the protocol, efficiently routing encrypted Notes between Personas. - *Ephemeral Routing:* Relays route ciphertext based on CIDs and Persona subscriptions, without long-term storage of user data. - *Pub/Sub Model:* Facilitates efficient, real-time delivery of Notes based on user subscriptions. - *Censorship Resistance:* Users can publish to multiple Relays, ensuring availability and resilience against censorship. *** 3.3.3. Agile Client Architecture: Broad Accessibility and Adaptability -Agora adopts a flexible client architecture to balance user sovereignty with broad accessibility, particularly concerning app store ecosystems. +The protocol adopts a flexible client architecture to balance user sovereignty with broad accessibility, particularly concerning app store ecosystems. - *PDS-Proximate Logic:* Core application logic can reside and execute securely on the user's PDS. - *Thin Clients:* Edge devices (mobile, desktop) run lightweight applications that interface with the PDS, mitigating app store restrictions and reducing device resource demands. -- *Strategic Imperative:* This architecture ensures Agora's reach to a wider user base while maintaining security and privacy. +- *Strategic Imperative:* This architecture ensures the protocol's reach to a wider user base while maintaining security and privacy. -* 4. Agora Use Cases: A Paradigm Shift +* 4. Use Cases: A Paradigm Shift -The synergistic combination of Agora's core differentiators enables a wide array of transformative use cases, redefining digital interaction across multiple domains. +The synergistic combination of the protocol's core differentiators enables a wide array of transformative use cases, redefining digital interaction across multiple domains. ** 4.1. Decentralized Social Interaction -Agora provides a robust framework for secure, private, and censorship-resistant interaction, moving beyond traditional platform-controlled silos. +The protocol provides a robust framework for secure, private, and censorship-resistant interaction, moving beyond traditional platform-controlled silos. *** 4.1.1. Asynchronous Interaction (The Note Primitive) @@ -124,7 +124,7 @@ Agora provides a robust framework for secure, private, and censorship-resistant ** 4.2. Social Publishing and Knowledge Management -Agora fundamentally reshapes how content is created, published, and managed, empowering creators and ensuring verifiable knowledge. +The protocol fundamentally reshapes how content is created, published, and managed, empowering creators and ensuring verifiable knowledge. *** 4.2.1. Feeds and Pages @@ -147,7 +147,7 @@ Agora fundamentally reshapes how content is created, published, and managed, emp ** 4.3. Decentralized E-commerce and Markets -Agora enables peer-to-peer economic interaction without intermediaries, fostering transparent and auditable marketplaces for goods and services. +The protocol enables peer-to-peer economic interaction without intermediaries, fostering transparent and auditable marketplaces for goods and services. *** 4.3.1. Market Interaction Contracts @@ -157,12 +157,12 @@ Agora enables peer-to-peer economic interaction without intermediaries, fosterin *** 4.3.2. Fungible vs. Non-fungible Assets -- *Non-Fungible:* Agora's *Contract Note* model is inherently well-suited for unique goods and services (e.g., digital art, custom work), with each contract representing a distinct agreement. -- *Fungible:* While Agora provides the identity, communication, and settlement rails (e.g., Lightning micropayments), high-speed trading of fungible assets (e.g., cryptocurrencies, commodities) would require specialized architectural layers (e.g., decentralized exchanges or AMMs) built *on top of* the Agora protocol for order matching and liquidity. +- *Non-Fungible:* The protocol's *Contract Note* model is inherently well-suited for unique goods and services (e.g., digital art, custom work), with each contract representing a distinct agreement. +- *Fungible:* While the protocol provides the identity, communication, and settlement rails (e.g., Lightning micropayments), high-speed trading of fungible assets (e.g., cryptocurrencies, commodities) would require specialized architectural layers (e.g., decentralized exchanges or AMMs) built *on top of* the protocol for order matching and liquidity. ** 4.4. Decentralized Collaboration and Project Management -Agora offers robust primitives for secure, auditable collaboration, empowering teams and communities. +The protocol offers robust primitives for secure, auditable collaboration, empowering teams and communities. *** 4.4.1. Version-Controlled Documents and Code @@ -184,28 +184,28 @@ The convergence of native hosting, identity, and contracts enables a unified pro ** 4.5. Liquid Democracy and Governance: Evolvable Collectives -Agora's identity and contract primitives lay the groundwork for a dynamic, adaptive model of decentralized governance that moves beyond the rigidity of traditional blockchain-based DAOs. +The protocol's identity and contract primitives lay the groundwork for a dynamic, adaptive model of decentralized governance that moves beyond the rigidity of traditional blockchain-based DAOs. *** 4.5.1. Adaptive Constitutions and Policy Execution -- *Signed Votes and Execution:* Individual votes are signed Notes that `references` a proposal CID. Unlike immutable blockchain code, Agora governance is built around *Adaptive Constitutions*. +- *Signed Votes and Execution:* Individual votes are signed Notes that `references` a proposal CID. Unlike immutable blockchain code, the protocol's governance is built around *Adaptive Constitutions*. - *Recursive Rule-Making:* Successful votes trigger the Governance Executable Module (GEM) to automatically update the Collective's policy parameters (e.g., membership fees, arbitration rules) in its active Smart Constitution. - *Immutable History, Mutable State:* While the complete audit trail of every vote and version is permanently recorded as a chain of CIDs, the organization can evolve its logic over time without requiring complex migrations. *** 4.5.2. Decentralized Autonomous Organizations (DAOs) - *Foundation Contracts:* DAOs are formalized as `Collective Personas` governed by a set of foundational `Contract Notes` that define membership, treasury management, and decision-making processes. -- *Forks as Safety Valves:* Because Agora is permissionless, minorities can "fork" a Collective by creating a new Persona based on an earlier constitutional CID, ensuring protection against majority tyranny and preserving community intent. +- *Forks as Safety Valves:* Because the protocol is permissionless, minorities can "fork" a Collective by creating a new Persona based on an earlier constitutional CID, ensuring protection against majority tyranny and preserving community intent. - *Transparent Operations:* All operational decisions, proposals, and expenditures within a DAO are conducted and recorded as signed Notes and Contracts, providing 100% transparency to participants. * 5. Conclusion: Towards a Self-Sovereign Digital Future -The Agora Protocol is meticulously designed to serve as the foundational layer for a new era of decentralized digital interaction. By unifying identity, data, and communication under the immutable, verifiable, and user-owned "Note" primitive, coupled with a distributed infrastructure and self-sovereign identity management, Agora offers a robust and resilient alternative to centralized systems. Its capabilities span from secure personal communication to complex global e-commerce, from collaborative knowledge creation to transparent democratic governance. Agora empowers individuals and collectives to reclaim their digital sovereignty, fostering an internet where trust is cryptographic, privacy is inherent, and freedom is architectural. +The social protocol is meticulously designed to serve as the foundational layer for a new era of decentralized digital interaction. By unifying identity, data, and communication under the immutable, verifiable, and user-owned "Note" primitive, coupled with a distributed infrastructure and self-sovereign identity management, the protocol offers a robust and resilient alternative to centralized systems. Its capabilities span from secure personal communication to complex global e-commerce, from collaborative knowledge creation to transparent democratic governance. The protocol empowers individuals and collectives to reclaim their digital sovereignty, fostering an internet where trust is cryptographic, privacy is inherent, and freedom is architectural. * Bootstrapping & Progressive Decentralization ** The Cold Start Problem -A decentralized social network faces an existential network effect challenge. Users will not join if there is no content, and creators will not post if there are no users. Agora solves this through *Progressive Decentralization*. +A decentralized social network faces an existential network effect challenge. Users will not join if there is no content, and creators will not post if there are no users. The protocol solves this through *Progressive Decentralization*. ** Bootstrap Sequence @@ -245,18 +245,18 @@ Reduce "empty feed" problem by immediately showing relevant content based on use *** Privacy Considerations - Migration is *opt-in*, not mandatory. - Users choose which platforms to import from. -- Imported data is stored locally; only new Agora follows are public. +- Imported data is stored locally; only new protocol follows are public. - Users can audit and remove imported suggestions before confirming follows. *** Discovery Expansion - Suggest high-reputation personas in imported interest areas. -- Show "Your Twitter follows on Agora" for easy reconnecting. +- Show "Your Twitter follows on the protocol" for easy reconnecting. - Surface collectives matching imported community memberships. ** The "Four Orders of [[id:26f3e845-5eb4-4bcd-9cff-28e219934841][Growth]]" (Scaling Sequence) -Scaling a decentralized network requires shifting from "Hand-holding" to "Protocol Incentives." Agora follows a strictly defined orders-of-magnitude [[id:26f3e845-5eb4-4bcd-9cff-28e219934841][growth strategy]]: +Scaling a decentralized network requires shifting from "Hand-holding" to "Protocol Incentives." The protocol follows a strictly defined orders-of-magnitude [[id:26f3e845-5eb4-4bcd-9cff-28e219934841][growth strategy]]: *** Order 1: The First 1,000 (The "Founders") - *Target:* Technical enthusiasts, privacy advocates, and niche professional guilds (e.g., decentralized AI devs). @@ -275,7 +275,7 @@ Scaling a decentralized network requires shifting from "Hand-holding" to "Protoc *** Order 4: The 1M+ (The "Ecosystem") - *Target:* The general public. -- *Tactics:* The Algorithm Marketplace becomes the draw. People join because "The Scientific Lens" or "The Family Lens" on Agora provides a better mental health experience than the addictive AI of centralized apps. +- *Tactics:* The Algorithm Marketplace becomes the draw. People join because "The Scientific Lens" or "The Family Lens" on the protocol provides a better mental health experience than the addictive AI of centralized apps. - *Success Metric:* Total P2P bandwidth (Seeding) exceeds the capacity of a mid-sized centralized CDN. ** Progressive Decentralization Phases @@ -290,53 +290,53 @@ Scaling a decentralized network requires shifting from "Hand-holding" to "Protoc *** Phase 3: Full Decentralization (Year 3+) - *No Central Authority:* The original developers become just one of many PDS and Relay providers. -- *Protocol Stability:* The V1.0 spec is finalized, and development is driven by the *Agora Governance Model*. +- *Protocol Stability:* The V1.0 spec is finalized, and development is driven by the *Protocol Governance Model*. ** Incentivized Growth - *Referral Satoshis:* Early users can be rewarded in satoshis for successful referrals that lead to high-reputation personas. -- *Micro-Grant Bounties:* Funding developers to build "Must-Have" Agora apps through the economic layer. +- *Micro-Grant Bounties:* Funding developers to build "Must-Have" protocol apps through the economic layer. * Strategic Positioning ** Platform Replacement Strategy -Rather than positioning Agora as an existential threat to Big Tech (Apple, Google, Meta), Agora should first target underserved communities and platforms with clear pain points: +Rather than positioning the protocol as an existential threat to Big Tech (Apple, Google, Meta), the protocol should first target underserved communities and platforms with clear pain points: *** Phase 1: Niche Community Platforms ** Forums (Reddit, phpBB, vBulletin) - *Pain Point:* Centralized moderation, censorship, data mining. -- *Agora Advantage:* Sovereign moderation, portable identity, no platform lock-in. +- *Social Protocol Advantage:* Sovereign moderation, portable identity, no platform lock-in. - *Target Communities:* Developer forums, hobbyist communities, support forums. ** Visual Discovery (Pinterest) - *Pain Point:* Algorithmic manipulation, advertising-driven discovery. -- *Agora Advantage:* User-chosen discovery algorithms, no surveillance capitalism. +- *Social Protocol Advantage:* User-chosen discovery algorithms, no surveillance capitalism. ** Professional Communities (LinkedIn, corporate intranets) - *Pain Point:* Professional data exploitation, platform-controlled networking. -- *Agora Advantage:* Sovereign professional identity, portable reputation. +- *Social Protocol Advantage:* Sovereign professional identity, portable reputation. ** Creator Platforms (Medium, Substack) - *Pain Point:* Platform fees (10-50%), censorship risk, no portability. -- *Agora Advantage:* Near-zero fees, content ownership, subscriber portability. +- *Social Protocol Advantage:* Near-zero fees, content ownership, subscriber portability. ** Marketplaces (eBay, Etsy) - *Pain Point:* High fees (10-15%), centralized dispute resolution, account bans. -- *Agora Advantage:* Low fees (<5%), transparent reputation, sovereign stores. +- *Social Protocol Advantage:* Low fees (<5%), transparent reputation, sovereign stores. ** Adult Content (Pornhub, OnlyFans) - *Pain Point:* Censorship, payment processor discrimination, lack of privacy. -- *Agora Advantage:* Censorship-resistant, Lightning-native payments, pseudonymous. +- *Social Protocol Advantage:* Censorship-resistant, Lightning-native payments, pseudonymous. ** Specialized Communities (QRZ, Logbook of the World) - *Pain Point:* Aging infrastructure, lack of modern features, centralization. -- *Agora Advantage:* Modern protocol, extensible, community-governed. +- *Social Protocol Advantage:* Modern protocol, extensible, community-governed. ** Decentralized Communities (Nostr, Fediverse) - *Pain Point:* Fragmentation, lack of economic layer, UI/UX challenges. -- *Agora Advantage:* Unified protocol, Lightning integration, polished UX. +- *Social Protocol Advantage:* Unified protocol, Lightning integration, polished UX. *** Phase 2: Horizontal Expansion @@ -347,7 +347,7 @@ Once established in niche communities: ** Big Tech Analysis (Long-term) -While not the immediate focus, Agora's architecture eventually threatens Big Tech: +While not the immediate focus, the protocol's architecture eventually threatens Big Tech: *** Meta/Facebook - *Risk:* Portable identity undermines social graph lock-in. @@ -355,7 +355,7 @@ While not the immediate focus, Agora's architecture eventually threatens Big Tec *** Apple - *Opportunity:* Privacy alignment, hardware security integration. -- *Risk:* App Store policies may restrict Agora clients. +- *Risk:* App Store policies may restrict protocol clients. *** Google - *Risk:* Search dominance challenged by social-graph-first discovery. @@ -366,7 +366,7 @@ While not the immediate focus, Agora's architecture eventually threatens Big Tec - *Start Small:* Win over frustrated communities on Reddit, forums, Discord. - *Build Bridges:* ActivityPub/Mastodon integration, Twitter migration tools. - *Demonstrate Value:* Show "You trade 2 seconds for freedom" is worth it. -- *Let Giants React:* By the time Big Tech notices, Agora is entrenched. +- *Let Giants React:* By the time Big Tech notices, the protocol is entrenched. ** Strategic Assessment @@ -378,7 +378,7 @@ While not the immediate focus, Agora's architecture eventually threatens Big Tec ** The Jurisdictional Challenge -As a decentralized protocol with no central authority, Agora is designed to operate across international jurisdictions. +As a decentralized protocol with no central authority, the protocol is designed to operate across international jurisdictions. ** Content Moderation & Liability @@ -387,14 +387,14 @@ As a decentralized protocol with no central authority, Agora is designed to oper - *PDS Sovereignty:* The user (the PDS owner) is the only entity with the ability to decrypt and view the content. *** The CSAM Challenge -- *Zero Tolerance Policy:* Agora's governance model includes protocol-level consensus for universally illegal content. +- *Zero Tolerance Policy:* The protocol's governance model includes protocol-level consensus for universally illegal content. - *Network-Level Blocking:* High-reputation Relays can block CIDs associated with CSAM. - *Fundamental Tension:* The trade-off between total privacy (E2EE) and the ability to detect illegal content. ** Financial Regulation & AML - *Micro-Payments:* Lightning Network payments generally fall below traditional AML/KYC thresholds. -- *Non-Custodial:* Agora is non-custodial. Users control their own keys and funds. +- *Non-Custodial:* The protocol is non-custodial. Users control their own keys and funds. ** Data Privacy ([[id:c0fdec00-8a44-43f0-ac81-e8dc61411865][GDPR]]/CCPA) @@ -424,5 +424,5 @@ As a decentralized protocol with no central authority, Agora is designed to oper * Related Documents -- Agora Strategic Positioning -- Agora Legal & Regulatory Strategy +- Protocol Strategic Positioning +- Protocol Legal & Regulatory Strategy diff --git a/ideas/agora/agora-requirements-02-identity.org b/ideas/passepartout-social-protocol/requirements-02-identity.org similarity index 86% rename from ideas/agora/agora-requirements-02-identity.org rename to ideas/passepartout-social-protocol/requirements-02-identity.org index 7ec0df1..6d42004 100644 --- a/ideas/agora/agora-requirements-02-identity.org +++ b/ideas/passepartout-social-protocol/requirements-02-identity.org @@ -7,7 +7,7 @@ ** Master Key (Psyche) -The Master Key, often referred to as "Psyche" (Latin for soul or animating principle), is the absolute foundation of your digital identity in [[id:1d074690-a279-59cb-b91d-e9a22ae104ad][Agora]]. It serves as your unassailable root of trust, from which every other functional identity (your Personas) is cryptographically derived. This section meticulously outlines the Master Key's core requirements, elucidates how it empowers flexible organizational structures, and details the robust mechanisms for its secure management and resilient recovery. It is the ultimate key to your self-sovereignty. +The Master Key, often referred to as "Psyche" (Latin for soul or animating principle), is the absolute foundation of your digital identity in [[id:1d074690-a279-59cb-b91d-e9a22ae104ad][Social Protocol]]. It serves as your unassailable root of trust, from which every other functional identity (your Personas) is cryptographically derived. This section meticulously outlines the Master Key's core requirements, elucidates how it empowers flexible organizational structures, and details the robust mechanisms for its secure management and resilient recovery. It is the ultimate key to your self-sovereignty. *** Requirements & The Root of Trust @@ -17,7 +17,7 @@ The Master Key, often referred to as "Psyche" (Latin for soul or animating princ - The Master Key MUST be generated from a minimum of 256 bits of high-quality, cryptographically secure entropy. - The Master Key MUST be encoded as a BIP-39 mnemonic phrase (typically 24 words) for human-readable, offline backup and disaster recovery. - The Master Key MUST be stored offline (e.g., on paper, engraved metal) or within a tamper-resistant [[id:84a537b4-4256-50c8-91f5-dd5b4538418f][hardware]] security module (HSM) for maximum protection against compromise. -- The system MUST utilize a custom HD derivation path: `m/44'/1'/account'/persona'/key_purpose/key_index`, uniquely identifying Agora's identity structure within the broader BIP-44 ecosystem. (*Note: Index `1'` is utilized for the experimental/testnet phase; a unique permanent index will be registered for the Agora Mainnet via SLIP-0044.*) +- The system MUST utilize a custom HD derivation path: `m/44'/1'/account'/persona'/key_purpose/key_index`, uniquely identifying the protocol's identity structure within the broader BIP-44 ecosystem. (*Note: Index `1'` is utilized for the experimental/testnet phase; a unique permanent index will be registered for the protocol Mainnet via SLIP-0044.*) - This path allows each Persona to act as a "Sub-Root," deriving its own autonomous functional keys (e.g., for Bitcoin, Lightning, PGP, or SSH) without requiring access to the Master Key once the Persona's extended private key (xpriv) is provisioned to a device. - Each `persona'` index within this derivation path MUST represent a distinct DID (Decentralized Identifier), ensuring global uniqueness and unlinkability. - The system MUST allow a single Master Key seed to generate an infinite number of unique, unlinkable personas, providing unparalleled flexibility for different digital roles. @@ -32,7 +32,7 @@ It is critical to distinguish between the Master Key's role in *Persona derivati - *Master Key for Derivation (Creation of New Identities):* The Master Key is the sole cryptographic origin for generating new Accounts and Personas. Any creation of a new Persona (or Account) in your identity tree requires interaction with the Master Key. This ensures a clear, auditable, and cryptographically sound chain of custody from your single root to every Persona. While this might occasionally require accessing a hardware wallet for a new Persona setup, it safeguards the integrity of your entire identity graph. -- *Persona Keys for Actions (Interacting with the Network):* Once a Persona is created, it becomes a fully independent, active agent in the Agora network. All subsequent actions—signing messages, publishing content, entering into contracts (including Foundation Contracts), acting as a guardian for social recovery, or joining an organization—are performed using the Persona's own distinct keypairs. *The Master Key is explicitly *not* needed for these daily operational activities.* This design minimizes the Master Key's exposure, keeping it safely offline and dramatically reducing the frequency of hardware wallet interactions for routine tasks. +- *Persona Keys for Actions (Interacting with the Network):* Once a Persona is created, it becomes a fully independent, active agent in the protocol network. All subsequent actions—signing messages, publishing content, entering into contracts (including Foundation Contracts), acting as a guardian for social recovery, or joining an organization—are performed using the Persona's own distinct keypairs. *The Master Key is explicitly *not* needed for these daily operational activities.* This design minimizes the Master Key's exposure, keeping it safely offline and dramatically reducing the frequency of hardware wallet interactions for routine tasks. This clear separation ensures that your Master Key functions as a secure, infrequent-use root for identity creation and recovery, while your Personas are empowered to execute all network interactions autonomously. @@ -40,7 +40,7 @@ This clear separation ensures that your Master Key functions as a secure, infreq **** Shamir's Secret Sharing: Distributed Trust -If a user loses access to their offline Master Key, Agora's Social Recovery mechanism provides a decentralized, self-sovereign solution: +If a user loses access to their offline Master Key, the protocol's Social Recovery mechanism provides a decentralized, self-sovereign solution: 1. Master Key is cryptographically pre-split into N shards using Shamir's Secret Sharing. 2. These shards are securely distributed to M-of-N "Guardians" (trusted friends or professional services). 3. Recovery only requires M guardians to recombine their shards, rebuilding the Master Key offline. @@ -164,7 +164,7 @@ async function recoverShard( ** HD Derivation *** HD Derivation Architecture (BIP-32/44) -- Agora uses a custom derivation path to ensure interoperability: `m/purpose'/persona_index'/profile_index/key_type`. +- The protocol uses a custom derivation path to ensure interoperability: `m/purpose'/persona_index'/profile_index/key_type`. - The `persona_index'` MUST be hardened to prevent correlation attacks between different personas. - Each `persona_index'` MUST represent a distinct DID (Decentralized Identifier). - This allows a single seed to generate infinite, unlinkable personas. @@ -185,7 +185,7 @@ The system MUST allow a user to prove relationships between their own Personas w Clients must efficiently discover active personas derived from a Master Seed without performing an exhaustive scan of the entire index space. The Gap Limit Protocol defines the search window and criteria for identifying active personas during recovery or sync. **** Specification -- *Gap Limit (L):* The number of consecutive unused persona indices to check before stopping the scan. The default Agora gap limit is *20*. +- *Gap Limit (L):* The number of consecutive unused persona indices to check before stopping the scan. The default protocol gap limit is *20*. - *Active Persona Detection:* A persona index is considered "active" if it has: 1. A registered name in the Tier 2 Global Registry. 2. Any Content Objects published to a PDS/Relay. @@ -205,7 +205,7 @@ Clients must efficiently discover active personas derived from a Master Seed wit **** Comparison to Traditional Systems - *Traditional:* Partner leaves → Manually update 50+ passwords, revoke individual access rights across numerous platforms (email, bank, cloud storage, code repos, etc.). High risk of oversight and residual access. -- *Agora:* Partner leaves → One managed revocation at the Master Key level (or their specific Persona's access derivation is severed) → Instant, automatic severance of access across all derived keys (company Bitcoin, PGP, SSH, etc.). +- *Passepartout Social Protocol:* Partner leaves → One managed revocation at the Master Key level (or their specific Persona's access derivation is severed) → Instant, automatic severance of access across all derived keys (company Bitcoin, PGP, SSH, etc.). This mechanism ensures that the collective's assets remain secure and under the control of the remaining authorized members, providing a robust solution for organizational identity management. @@ -277,18 +277,18 @@ To generate a new Persona: The Account-Level Strategy is built upon a robust technical foundation that rigorously adheres to and extends industry standards for cryptographic key derivation. This specification ensures predictable, secure, and interoperable management of multiple digital identities from a single Master Key. -***** BIP-44 Derivation Path Structure: Agora's Standard +***** BIP-44 Derivation Path Structure: Protocol's Standard -Agora meticulously follows the established BIP-44 standard for hierarchical deterministic key derivation paths. This standardized structure guarantees compatibility and logical organization of your digital identities. +The protocol meticulously follows the established BIP-44 standard for hierarchical deterministic key derivation paths. This standardized structure guarantees compatibility and logical organization of your digital identities. `m / purpose' / coin_type' / account' / persona' / key_purpose / key_index` -In Agora's context, this is specifically mapped as: +In the protocol's context, this is specifically mapped as: `m / 44' / 1' / account' / persona' / key_purpose / key_index` - *Purpose (44'):* This is a hardened derivation, as prescribed by BIP-44, signifying that the derived keys are cryptographically isolated from the Master Key. -- *Coin Type (1'):* This is a hardened derivation, and `1'` is the officially registered SLIP-0044 index specifically allocated for the Agora Protocol. +- *Coin Type (1'):* This is a hardened derivation, and `1'` is the officially registered SLIP-0044 index specifically allocated for the Social Protocol. - *Account (account'):* This is a hardened derivation. It provides independent, cryptographically isolated persona namespaces, enabling users to manage distinct organizational or contextual groupings of Personas. - *Persona (persona'):* This is a hardened derivation. Each index represents a distinct, autonomous digital identity (DID). Hardening ensures that compromising one Persona's keys cannot compromise sibling Personas or the Master Key. - *Key Purpose (key_purpose):* This non-hardened layer allows a single Persona to act as a "Sub-Root" to derive autonomous functional keys for specific tasks without requiring the Master Key. Examples: @@ -302,7 +302,7 @@ In Agora's context, this is specifically mapped as: ***** Account Types and Reserved Indices: Standardized Compartmentalization -While the choice of account indices is technically arbitrary, Agora recommends the following conventions. These standardized assignments ensure client interoperability and provide a common language for managing distinct digital compartments. +While the choice of account indices is technically arbitrary, the protocol recommends the following conventions. These standardized assignments ensure client interoperability and provide a common language for managing distinct digital compartments. - *0': Primary Account.* This is the default account for a user's primary personal identity, social interactions, and other everyday personas. - *1': Professional Account.* This account is dedicated to professional identity, credentials, work-related personas, and business interactions. @@ -311,7 +311,7 @@ While the choice of account indices is technically arbitrary, Agora recommends t ***** Client-Side Management Rules: Enforcing Security and Privacy -Client applications interacting with Agora's identity system MUST adhere to a strict set of rules to ensure the security, privacy, and integrity of user accounts. +Client applications interacting with the protocol's identity system MUST adhere to a strict set of rules 1. *Account Discovery (Gap Limit):* Clients MUST implement a "Gap Limit" (a heuristic search window, typically 20) for account discovery. During recovery or initial synchronization, the client scans accounts 0' through `N'` (where `N'` is determined by the gap limit and activity) for active personas. If an active account is found, the scan window is intelligently shifted forward. 2. *Context Isolation:* Data associated with different accounts (e.g., contact lists, encryption keys, local indexes) MUST be stored in cryptographically isolated database partitions or encrypted with account-specific salts. This prevents accidental data leakage between contexts. @@ -349,7 +349,7 @@ While the Master Key is an offline seed, Personas are active network agents gove **** Recovery Guardian Dynamics: Natural Persons vs. Collectives -Agora distinguishes between the dynamics of recovery for individual "natural person" Personas and "collective" or organizational Personas (e.g., companies, DAOs) when it comes to social recovery. +The protocol distinguishes between the dynamics of recovery for individual "natural person" Personas and "collective" or organizational Personas (e.g., companies, DAOs) when it comes to social recovery. ***** Natural Person Persona: The "Dictator with Safety Nets" For a human, the design goal is Ultimate Sovereignty. You are the "Root." Even if you have "Recovery Friends," they should have no power over you unless you are incapacitated. @@ -365,16 +365,16 @@ For an LLC or NGO, the goal is Mutual Defense and preventing "hostile takeovers" - *Protection:* This prevents a single member from seizing the company identity. Removing a member requires signatures from the quorum (e.g., 3-of-4), ensuring that "consent" is baked into the math of the threshold. ***** Identity Succession & Minors -Agora handles the lifecycle of identity across generations. +The protocol handles the lifecycle of identity across generations. - *Minor Onboarding:* For a minor, a parent or guardian Persona can "Co-sign" the identity inception event. - *Succession Logic:* This link creates a pre-authorized recovery path where the parent holds a dormant weight that can be activated to rotate keys if the minor loses access, transitioning to full independence at a defined maturation date. **** Legal Override & The "Break-Glass" Escrow (For Legal Entities) -To handle situations like the death of a sole founder, a lost key, or a binding court order without creating a central back door, Agora implements a "Dormant Escrow" pattern specifically designed for Collective Personas or High-Value single Personas. +To handle situations like the death of a sole founder, a lost key, or a binding court order without creating a central back door, the protocol implements a "Dormant Escrow" pattern specifically designed for Collective Personas or High-Value single Personas. - *The Dormant Key:* At inception, the Persona's governance structure includes a "Public Key" belonging to a Neutral Third Party (e.g., a decentralized notary or a legal escrow service). This key is assigned a weight of `0` for daily operations. -- *Multi-Party (M-of-N) Escrow:* To prevent a single corrupt entity from hijacking an identity, Agora utilizes a *Recovery Council*. For instance, a rotation might require 2-of-3 signatures from designated entities (e.g., a Notary, a Law Firm, and a Decentralized Oracle). +- *Multi-Party (M-of-N) Escrow:* To prevent a single corrupt entity from hijacking an identity, the protocol utilizes a *Recovery Council*. For instance, a rotation might require 2-of-3 signatures from designated entities (e.g., a Notary, a Law Firm, and a Decentralized Oracle). - *The Trigger:* The identity’s governing logic includes a rule: "If a certified Legal Attestation (e.g., signed by the local Court's Public Key) is presented, the Escrow Key's weight jumps to the necessary quorum threshold (e.g., 100) for a single Rotation Event." - *Observer-First Transparency:* Any change to the master key—including a legal override—must be published to the *Key Event Log (KEL)*. This ensures it's impossible for an agent to "quietly" take over an account; every user device and hired "watchdog" service is alerted immediately. - *The Veto Window (Time-Locking):* Any rotation event initiated by an Escrow Key triggers a mandatory 72-hour `Pending State`. If the primary owner still possesses their key (i.e., the agent is acting maliciously), they can sign a *Veto & Revoke* message. Because the Owner Key has absolute priority, this instantly kills the pending rotation and can strip the escrow agent of future rights. If the owner is incapacitated, they won't sign a veto, and after 72 hours, the change becomes final. @@ -411,12 +411,12 @@ To prevent assets from being "lost forever" if a user disappears unexpectedly: - User SHOULD have hardware backups before maturation. *** Wallet Integration (Ownership & Contracts) -Each Persona in Agora is analogous to a legal person, possessing the inherent right and capability to own property, enter into contracts, and claim protected rights (freedom of speech, due process). Therefore, every Persona will have its own associated wallets (e.g., for BTC, Lightning, stablecoins, other digital assets). These wallets are controlled by the Persona's derived keypairs, making cryptographic ownership an integral part of its functional identity. Personas are thus fully enabled to manage digital assets and participate in the Agora economy. +Each Persona in the protocol is analogous to a legal person, possessing the inherent right and capability to own property, enter into contracts, and claim protected rights (freedom of speech, due process). Therefore, every Persona will have its own associated wallets (e.g., for BTC, Lightning, stablecoins, other digital assets). These wallets are controlled by the Persona's derived keypairs, making cryptographic ownership an integral part of its functional identity. Personas are thus fully enabled to manage digital assets and participate in the protocol economy. *** Delegated Authoring & AI Personas **** Owner DID vs. Editor DID: The Mechanism of Agency -Agora distinguishes between the identity that owns the content and the identity that cryptographically signs it. While these are identical in most personal interactions, their separation enables complex organizational and recovery workflows. +The protocol distinguishes between the identity that owns the content and the identity that cryptographically signs it. While these are identical in most personal interactions, their separation enables complex organizational and recovery workflows. - *Owner DID:* The source of authority, reputation, and ownership. This is the Persona "speaking" or "publishing." All social weight and historical context accrue to this DID. - *Editor DID:* The cryptographic actor performing the signature, recorded within the Note's `proof` object. This is the entity "signing" the data. The network verifies that the Editor holds a valid Delegation Certificate or is an authorized recovery key for the Owner. If omitted from the `proof`, it defaults to the Owner DID (self-signed). @@ -432,14 +432,14 @@ Agora distinguishes between the identity that owns the content and the identity - *Reputation Portability:* Content history and social relationships stay with the Owner DID, regardless of which specific human or bot was authorized to sign at the time. **** Cryptographic Delegated Signatures -To allow multiple individuals (e.g., employees) or autonomous agents to act on behalf of a single Persona (e.g., an LLC or a brand account) without sharing the Master Key, Agora employs Delegated Signatures. +To allow multiple individuals (e.g., employees) or autonomous agents to act on behalf of a single Persona (e.g., an LLC or a brand account) without sharing the Master Key, the protocol employs Delegated Signatures. - *The Delegation Certificate:* The "Owner" Persona signs a special `Delegation Certificate` granting specific capabilities to a "Delegate" DID for a defined period. - *Example Constraint:* "Delegate X can publish `is_feed: true` Notes on behalf of Owner Y, but cannot sign `contract` Notes." - *The Signature:* When the Delegate acts, they sign the Note with their *own* private key and append the Delegation Certificate. The network validates the certificate against the Owner's public key. - *Instant Revocation:* The Owner can instantly revoke the delegation by publishing a revocation event, cutting off the Delegate without needing to change passwords or rotate the Owner's keys. **** AI Agent Personas (AAP) -Agora treats Artificial Intelligence not as a backend feature, but as a first-class participant. +The protocol treats Artificial Intelligence not as a backend feature, but as a first-class participant. - *Agent DIDs:* An AI Agent is assigned its own derived Persona DID, completely separated from the human's primary identity. - *Capabilities-Based Security:* Using the Delegation mechanism above, the human owner grants the AI Agent restricted capabilities (e.g., "Authorized to spend up to 5000 sats/month" or "Authorized to draft responses but not publish them"). - *Verifiable Origins:* Because the AI signs with its own DID, all network participants can instantly and cryptographically verify whether a piece of content was authored by a human or an AI. @@ -455,7 +455,7 @@ Agora treats Artificial Intelligence not as a backend feature, but as a first-cl ***** The Global Registry (Tier 2) - *Decentralized Ledger:* A name-to-DID mapping stored on a decentralized ledger (e.g., a simple L2 or a high-reputation PDS/Relay coalition). -- *Zooko's Triangle:* Agora attempts to achieve names that are *Human-Readable*, *Secure*, and *Decentralized*. +- *Zooko's Triangle:* The protocol attempts to achieve names that are *Human-Readable*, *Secure*, and *Decentralized*. - *First-Come, First-Served:* Names are registered by the first persona to claim them, with small micro-fees (1000+ satoshis) to prevent squatting. ***** The Subdomain Model (Tier 3: The "Default" Handle) @@ -475,7 +475,7 @@ Because users manage multiple Personas (Legal, Professional, Anonymous) derived - *Anonymous/Alt:* `alias.provider.org` (e.g., `night-owl.aletheia.social`) **** Web3 Naming Services (e.g., ENS) -For users who want a username entirely untethered from a specific PDS provider's domain, Agora supports Decentralized Naming Services like Ethereum Name Service (ENS). +For users who want a username entirely untethered from a specific PDS provider's domain, the protocol supports Decentralized Naming Services like Ethereum Name Service (ENS). - *How it works:* The user registers a base name (e.g., `yourname.eth`). They can then generate unlimited subnames for their various Personas for free (e.g., `work.yourname.eth`, `social.yourname.eth`). - *Portability:* If the user migrates their data to a new PDS, the `.eth` name stays with them. They simply update the "Content Hash" record on the blockchain to point to the new PDS location, ensuring unbreakable ownership of the handle. @@ -519,8 +519,8 @@ For users who want a username entirely untethered from a specific PDS provider's *** Identity Linking *** Verification Objects -- *Verification Objects:* A persona can publish a signed *Verification Object* linking their Agora DID to other identities (e.g., a PGP key, a personal domain, or even a centralized social profile). -- *Proof-of-Domain:* Proving ownership of a domain (via DNS record) is the gold standard for high-trust identity verification in Agora. +- *Verification Objects:* A persona can publish a signed *Verification Object* linking their protocol DID to other identities (e.g., a PGP key, a personal domain, or even a centralized social profile). +- *Proof-of-Domain:* Proving ownership of a domain (via DNS record) is the gold standard for high-trust identity verification in the protocol. *** Zero-Knowledge Proofs (ZKP) & Selective Disclosure The system allows a user to "Attest" that two Personas belong to the same human (or hold the same credentials) *without revealing the Master Seed or creating a public cryptographic link*. @@ -529,7 +529,7 @@ The system allows a user to "Attest" that two Personas belong to the same human - *Privacy Preservation:* The resulting proof verifies the credential is valid but explicitly hides *which* specific Legal Name DID generated the proof. **** Attribute-Based Predicate Proofs -Agora extends ZKP capabilities beyond cross-persona linking to support *Selective Disclosure* and *Predicate Proofs* using Verifiable Credentials (VCs) with advanced cryptographic schemas (e.g., BBS+ signatures or AnonCreds). This allows Personas to prove attributes about their physical or financial reality without leaking metadata or underlying identifiers. +The protocol extends ZKP capabilities beyond cross-persona linking to support *Selective Disclosure* and *Predicate Proofs* using Verifiable Credentials (VCs) with advanced cryptographic schemas (e.g., BBS+ signatures or AnonCreds). This allows Personas to prove attributes about their physical or financial reality without leaking metadata or underlying identifiers. - *Age/Date Verification:* A Persona can cryptographically prove a predicate like `Age > 18` to access age-restricted content or contracts without revealing their actual date of birth. - *Financial Ability:* A Persona can prove `Wallet Balance > 10,000 sats` or `Monthly Income > X` to serve as collateral or qualify for a service contract without revealing their exact balance or transaction history to the counterparty. - *Citizenship & Residence:* A Persona can prove membership in a specific geographic jurisdiction (e.g., "Resident of New York") for local governance voting or tax-compliant commerce without disclosing their legal name or specific home address. @@ -555,7 +555,7 @@ interface VerificationObject { proofData: string; }; - // Agora persona signature (proving the DID owner agrees to the link) + // Protocol persona signature (proving the DID owner agrees to the link) timestamp: number; signature: string; // Ed25519 signature over the object } @@ -571,10 +571,10 @@ When a Persona's derived keys are compromised, lost, or need deactivation, users *** Identity Verifiability & Forward Security -Personas are the functional, active identities through which you engage with the Agora network. Each Persona is uniquely and cryptographically derived from your Master Key, acting as your distinct digital self for specific contexts. They are the sovereign participants in the network, fully empowered to own property, enter into binding contracts, publish content, and claim protected rights such as due process and freedom of expression. This section details the cryptographic derivation, secure management, revocation mechanisms, and identification systems that enable your Personas to operate seamlessly and securely within the broader Agora ecosystem. +Personas are the functional, active identities through which you engage with the protocol network. Each Persona is uniquely and cryptographically derived from your Master Key, acting as your distinct digital self for specific contexts. They are the sovereign participants in the network, fully empowered to own property, enter into binding contracts, publish content, and claim protected rights such as due process and freedom of expression. This section details the cryptographic derivation, secure management, revocation mechanisms, and identification systems that enable your Personas to operate seamlessly and securely within the broader protocol ecosystem. *** Key Event Log (KEL): The Observer-First Transparency Log -Every Persona in Agora maintains a Key Event Log (KEL). This is a public, append-only ledger of all identity-related events, including: +Every Persona in the protocol maintains a Key Event Log (KEL). This is a public, append-only ledger of all identity-related events, including: - *Key Events:* Inception, rotation, and revocation. - *Follow Events:* Every time you follow another DID, a signed "Follow Event" is added to the log. - *Transparency:* It is impossible to "quietly" take over an account or manipulate your public history. Any change to the keys or following relationships must be published to the log. Watchdog services can monitor this log and alert the user immediately if an unauthorized event is initiated. @@ -585,7 +585,7 @@ The "Social Graph" (the list of DIDs you follow and who follows you) is mathemat - *The Rebuild:* When initializing a new PDS, the software scans the network and subscribed Relays for any signed Follow Events belonging to the user's DID. It automatically reconstructs the user's entire social graph (e.g., a list of 500 friends) without the user needing to remember a single username or manual backup. *** Pre-rotation: Quantum-Resistant Continuity -Agora utilizes the principle of *Pre-rotation* to ensure forward security as an ultimate fail-safe. +The protocol utilizes the principle of *Pre-rotation* to ensure forward security as an ultimate fail-safe. - *The Hash Commitment:* When a user creates their current active key, they simultaneously publish a cryptographic hash of their *next* (unborn) public key. - *The Protection:* Even if an attacker breaks the user's current private key (e.g., via a future quantum computer, theft, or even a malicious legal override attempt), they cannot forge a rotation event because they do not know the private key corresponding to the pre-committed hash. Rotation only becomes valid when the user reveals the new key that matches the previous hash, providing true "forward security." @@ -614,4 +614,4 @@ The "Vault" is a dedicated application for an offline/hardware device that manag **** Technical Requirements **** BIP-39 / BIP-44 Compatibility -Agora-compatible hardware wallets MUST support the `m/44'/1'/` path. If the device does not support the custom `1'` coin type, clients MAY fallback to a generic data-signing path, but this is NOT recommended for production use. +Protocol-compatible hardware wallets MUST support the `m/44'/1'/` path. If the device does not support the custom `1'` coin type, clients MAY fallback to a generic data-signing path, but this is NOT recommended for production use. diff --git a/ideas/agora/agora-requirements-03-infrastructure.org b/ideas/passepartout-social-protocol/requirements-03-infrastructure.org similarity index 88% rename from ideas/agora/agora-requirements-03-infrastructure.org rename to ideas/passepartout-social-protocol/requirements-03-infrastructure.org index 41c8c61..dd76626 100644 --- a/ideas/agora/agora-requirements-03-infrastructure.org +++ b/ideas/passepartout-social-protocol/requirements-03-infrastructure.org @@ -1,4 +1,4 @@ -#+title: Agora Requirements - 03: Infrastructure +#+title: Social Protocol Requirements - 03: Infrastructure #+author: Amero Garcia #+created: [2026-03-16 Mon 14:28] #+DATE: 2026-03-14 @@ -11,11 +11,11 @@ :END: * The Sovereign Infrastructure: Your Digital Foundation -[[id:1d074690-a279-59cb-b91d-e9a22ae104ad][Agora]]'s infrastructure is meticulously architected to deliver on the promise of true digital sovereignty. Unlike traditional platforms that centralize control, Agora distributes power to the edges—directly into the hands of users. This section details the foundational infrastructure that makes self-sovereign identity, data ownership, decentralized communication, and global discovery not just possible, but practical and scalable. +[[id:1d074690-a279-59cb-b91d-e9a22ae104ad][Social Protocol]]'s infrastructure is meticulously architected to deliver on the promise of true digital sovereignty. Unlike traditional platforms that centralize control, the protocol distributes power to the edges—directly into the hands of users. This section details the foundational infrastructure that makes self-sovereign identity, data ownership, decentralized communication, and global discovery not just possible, but practical and scalable. ** Personal Data Store (PDS): Your Digital Fortress -The Personal Data Store (PDS) is the cornerstone of Agora's sovereignty model—your personal, encrypted vault where all your Notes, identity data, and digital assets reside. Unlike cloud services that claim ownership of your data, your PDS is unequivocally yours. You control it. You host it. You decide who accesses it. It is the physical manifestation of your digital self-sovereignty. +The Personal Data Store (PDS) is the cornerstone of the protocol's sovereignty model—your personal, encrypted vault where all your Notes, identity data, and digital assets reside. Unlike cloud services that claim ownership of your data, your PDS is unequivocally yours. You control it. You host it. You decide who accesses it. It is the physical manifestation of your digital self-sovereignty. *** Requirements @@ -57,7 +57,7 @@ To send a private message: *** PDS Migration: Seamless Sovereignty Transfer -PDS Migration represents a fundamental capability of Agora's architecture—the seamless, user-initiated transfer of one's entire digital corpus from one Personal Data Store to another. Unlike traditional platforms where data migration is often complex, permission-based, or impossible, Agora treats PDS Migration as a first-class operation. This is not an edge case, but a core feature that ensures users retain ultimate sovereignty over their data throughout its lifecycle. Whether changing hosting providers, upgrading [[id:84a537b4-4256-50c8-91f5-dd5b4538418f][hardware]], or responding to security incidents, PDS Migration ensures users are never trapped by infrastructure choices. +PDS Migration represents a fundamental capability of the protocol's architecture—the seamless, user-initiated transfer of one's entire digital corpus from one Personal Data Store to another. Unlike traditional platforms where data migration is often complex, permission-based, or impossible, the protocol treats PDS Migration as a first-class operation. This is not an edge case, but a core feature that ensures users retain ultimate sovereignty over their data throughout its lifecycle. Whether changing hosting providers, upgrading [[id:84a537b4-4256-50c8-91f5-dd5b4538418f][hardware]], or responding to security incidents, PDS Migration ensures users are never trapped by infrastructure choices. **** Concept @@ -65,7 +65,7 @@ PDS Migration is the comprehensive process of transferring a user's entire encry Key principles of PDS Migration: -- *User Sovereignty Absolute:* Users retain complete autonomy to migrate their data without requiring permission, intervention, or cooperation from any third party. This is a fundamental right within the Agora ecosystem. +- *User Sovereignty Absolute:* Users retain complete autonomy to migrate their data without requiring permission, intervention, or cooperation from any third party. This is a fundamental right within the protocol ecosystem. - *Zero-Downtime Operation:* Migration SHOULD occur without interrupting the user's ongoing presence or activities on the network. This ensures continuous availability of services and interactions. - *Rollback Safety:* Users MUST have the capability to revert to the original PDS if the new PDS fails to perform adequately or if any issues arise during the migration process. This provides a safety net for critical data transfers. - *Atomic Cutover:* There is a clearly defined, atomic moment when the new PDS becomes the authoritative source of truth, and the old PDS transitions to a backup role, ensuring data consistency. @@ -290,7 +290,7 @@ async function verifyMigration( *** PDS-to-PDS Synchronization: Redundancy and Resilience -In a truly sovereign digital ecosystem, users should never be constrained to a single point of failure. Agora's PDS-to-PDS Synchronization protocol empowers users to run multiple Personal Data Stores simultaneously—for redundancy, load balancing, or geographic distribution. This protocol enables bidirectional synchronization of encrypted Content Objects between a user's PDS nodes, maintaining CID integrity, conflict resolution, and data consistency across the distributed infrastructure. It ensures that your digital presence remains resilient, available, and performant, regardless of individual infrastructure limitations. +In a truly sovereign digital ecosystem, users should never be constrained to a single point of failure. the protocol's PDS-to-PDS Synchronization protocol empowers users to run multiple Personal Data Stores simultaneously—for redundancy, load balancing, or geographic distribution. This protocol enables bidirectional synchronization of encrypted Content Objects between a user's PDS nodes, maintaining CID integrity, conflict resolution, and data consistency across the distributed infrastructure. It ensures that your digital presence remains resilient, available, and performant, regardless of individual infrastructure limitations. **** Concept @@ -442,14 +442,14 @@ interface SyncConfig { *** Distributed Mirroring & Social Resilience **** Following: Default "Feed Gossip" & The Phoenix Effect -Agora ensures baseline content resilience by leveraging a gossip-based mirroring architecture triggered by every "Follow" event. +The protocol ensures baseline content resilience by leveraging a gossip-based mirroring architecture triggered by every "Follow" event. - *Following = Essential Replicating:* When a user "follows" another Persona, their device or PDS automatically joins the gossip swarm for that target's most critical low-bandwidth data. - *Feed Gossip Scope:* To balance network resilience with device resources, default gossip is restricted to the *Identity Log (KEL)* and a rolling window of *recent text-based Notes* (e.g., the last 1,000 posts). - *The Phoenix Effect:* This level of mirroring ensures the "Phoenix Effect" remains viable. If a user's PDS is destroyed, they can "shout" to their followers: "I am the owner of DID:123. Please send me everything you have signed by my key." The essential history and social graph flow back from the community. - *Censorship Resistance:* By making essential gossip a default behavior, the social graph and latest news stay alive through the "cracks" of the internet automatically. **** Supporting: Opt-in "Supporter-Mirroring" & Decentralized CDN -For high-bandwidth content and deep archives, Agora transitions from simple gossip to an explicit infrastructure donation model. +For high-bandwidth content and deep archives, the protocol transitions from simple gossip to an explicit infrastructure donation model. - *Persistent Mirroring:* When a user clicks "Support," they opt-in to a deeper technical commitment. The supporter's PDS archives the *entire historical feed* of the creator, not just the recent window. - *High-Bandwidth "Pinning":* Supporters provide the backbone for the *"Follower-as-CDN"* model. A supporter can allocate specific storage (e.g., "Pin 5GB of latest video") to ensure large payloads (audio, video, high-res images) remain highly available. - *WebRTC Peering & Seeding:* Supporters act as active "Seeds" in a BitTorrent-style swarm. When a new viewer watches a video, the app prioritizes streaming via WebRTC from online supporters rather than the creator's PDS, ensuring viral content has $0 infrastructure cost for the creator. @@ -466,9 +466,9 @@ While the social swarm recovers public history, users ensure the recovery of pri - *Privacy Guarantee:* Because the backup is encrypted with the user's keys, the friends cannot read the private drafts or DMs; they only host the raw ciphertext blobs. - *Restoration:* In the event of a catastrophic local failure (e.g., fire, server loss), the user can download their latest snapshot from a friend and instantly restore their entire digital life to a new PDS node using their recovered Identity Keys. -** Relay Network: The Circulatory System of Agora +** Relay Network: The Circulatory System of the Protocol -The Relay Network serves as Agora's intelligent, adaptive message routing layer—ephemeral, user-chosen pathways that efficiently route encrypted Notes via a pub/sub model. Unlike centralized servers that store and monitor your data, Relays are transient routers that respect your privacy, delivering your messages without ever holding them long-term. They are the circulatory system of the Agora network, ensuring vital communication flows freely and securely. +The Relay Network serves as the protocol's intelligent, adaptive message routing layer—ephemeral, user-chosen pathways that efficiently route encrypted Notes via a pub/sub model. Unlike centralized servers that store and monitor your data, Relays are transient routers that respect your privacy, delivering your messages without ever holding them long-term. They are the circulatory system of the protocol network, ensuring vital communication flows freely and securely. *** Requirements @@ -481,7 +481,7 @@ The Relay Network serves as Agora's intelligent, adaptive message routing layer *** Technical Logic *** Relay Routing & Prioritization: Pay-to-Prioritize (P2P) -To ensure high-performance and sustainability without central control, Agora Relays utilize a *Pay-to-Prioritize (P2P)* routing strategy. Crucially, Relays are *Logic-Blind*. They do not inspect the Note's payload or contract terms (which may be encrypted). Instead, they prioritize traffic based on explicit, unencrypted metadata. +To ensure high-performance and sustainability without central control, the protocol's Relays utilize a *Pay-to-Prioritize (P2P)* routing strategy. Crucially, Relays are *Logic-Blind*. They do not inspect the Note's payload or contract terms (which may be encrypted). Instead, they prioritize traffic based on explicit, unencrypted metadata. **** Explicit Priority Fee (The "Fast-Lane") If a Note requires instant routing (e.g., a time-sensitive financial transaction or live chat), the sender can attach a Lightning micropayment directly to the routing request. @@ -516,7 +516,7 @@ New clients need to find Relay nodes without hardcoded lists (centralization ris ****** Well-Known DID - DID: `did:agora:bootstrap` - Service Endpoint: "RelayDirectory" with list of known high-reputation relays -- Maintained: By Agora Trust, updated quarterly +- Maintained: By Protocol Trust, updated quarterly ****** DHT (Future) - Distributed hash table for relay discovery @@ -577,10 +577,10 @@ To ensure sustainability without compromising user data (avoiding "Surveillance - *Relay:* Keeps 70% of fees (operating costs) - *Validator Oracles:* 20% (fraud detection) -- *Agora Protocol:* 10% (development fund) +- *Protocol Protocol:* 10% (development fund) **** Network Resilience: Global Firehose vs. Fragmented Relays -The Agora design ensures that the relay network is inherently replaceable and resilient: +The social protocol's design ensures that the relay network is inherently replaceable and resilient: - *Replaceable Relays:* Users can instantly switch to competitor relays if a provider becomes greedy or censorious by simply re-pointing their PDS. - *"Multi-homed" Data (Firehose Protection):* Users push posts to multiple relays simultaneously. If any relay fails, history remains accessible via others, ensuring followers can always maintain connectivity. @@ -647,14 +647,14 @@ Because anyone can theoretically publish a Note claiming to be "Alice," the Sear - *Unverified Flagging:* If a user squats on a username without owning the corresponding domain or blockchain record, the Indexer explicitly flags the search result as "Unverified" or excludes it. **** "Privacy-First" Search -Because Agora supports multiple isolated Personas per user, global search is strictly opt-in: +Because the social protocol supports multiple isolated Personas per user, global search is strictly opt-in: - *Public Personas:* (e.g., a "Work" or "Creator" Persona) publish a "Directory Opt-In" Note. Indexers catalog them, making them searchable by anyone. - *Private Personas:* (e.g., an "Anonymous" or "Family" Persona) do not publish this Note. They are entirely hidden from global Indexers. To find a Private Persona, another user must possess their exact DID string or be invited via a secure DIDComm routing channel. -** Agora-to-Web Gateways: The Bridge to the Open Web +** Social Protocol-to-Web Gateways: The Bridge to the Open Web *** Concept -To make decentralized, P2P content accessible to users on the "Open Web" (traditional browsers like Chrome or Safari without special plugins), Agora must bridge the gap between Content-Addressed Data (CIDs) and Location-Addressed URLs. +To make decentralized, P2P content accessible to users on the "Open Web" (traditional browsers like Chrome or Safari without special plugins), the social protocol must bridge the gap between Content-Addressed Data (CIDs) and Location-Addressed URLs. Gateways act as "translators" sitting on the edge of the decentralized network, talking HTTP to the legacy web while speaking P2P protocols internally. Every PDS or dedicated "Public Relay" can act as a web gateway. @@ -668,7 +668,7 @@ A piece of content identified by its hash (CID), such as `bafy...123`, can be vi **** The Translation Process When a browser hits that link, the Gateway performs the following automated steps: -1. *Fetch:* Retrieves the data from the P2P swarm using Agora's native protocols. +1. *Fetch:* Retrieves the data from the P2P swarm using the social protocol's native protocols. 2. *Verify:* Cryptographically verifies the Note's signature against the creator's Persona DID to ensure authenticity. 3. *Wrap:* Wraps the raw content (Markdown, JSON) in standard HTML/CSS templates so it renders correctly in a standard web browser. @@ -678,7 +678,7 @@ Most users will not share long cryptographic hashes. To make content web-friendl **** DNSLink (Traditional Domains) Users can point their own domains (e.g., `alice.com`) directly to their Persona. -- *Automatic Resolution:* When someone visits `alice.com`, the Gateway reads a DNS TXT record that says: "Go find content hash XYZ on the Agora network." +- *Automatic Resolution:* When someone visits `alice.com`, the Gateway reads a DNS TXT record that says: "Go find content hash XYZ on the social protocol network." - *Zero-Configuration SSL:* Gateways automatically provision and renew HTTPS certificates (via Let's Encrypt) for any domain linked to a Persona DID. - *Well-Known Verification:* Gateways automatically serve the user's DID document at `https://[custom-domain]/.well-known/atproto-did` to prove ownership. @@ -687,14 +687,14 @@ To onboard users quickly without forcing them to buy a domain, PDS providers act - *Availability & Routing:* The PDS performs an automated availability check. If a handle is free, it updates its Virtual Host configuration and internal DNS to instantly route traffic for `newuser.provider.org`. **** Web3 Domains (.eth, .p2p) -For users utilizing blockchain-based naming services, Agora integrates with specialized gateways (e.g., Eth.limo). A user types `yourname.eth.limo` into a standard browser, and the gateway does the heavy lifting of resolving the blockchain record and serving the underlying P2P data. +For users utilizing blockchain-based naming services, the social protocol integrates with specialized gateways (e.g., Eth.limo). A user types `yourname.eth.limo` into a standard browser, and the gateway does the heavy lifting of resolving the blockchain record and serving the underlying P2P data. *** 3. Social Mirroring for Search Engines (SEO) -To ensure Agora content is discoverable on legacy search engines like Google, the network utilizes automated rendering pipelines. +To ensure social protocol content is discoverable on legacy search engines like Google, the network utilizes automated rendering pipelines. **** The Firehose -Agora Relays emit a continuous "Firehose" of every public Note created on the network. +Social protocol Relays emit a continuous "Firehose" of every public Note created on the network. **** SEO Rendering (App Views) Specialized indexers or "App Views" (functioning like web-frontends) consume this firehose. They automatically generate static, crawlable HTML pages for every public profile, post, and thread. This ensures that decentralized content is aggressively indexed by Google's web crawlers, matching or exceeding the discoverability of traditional centralized blogs. @@ -710,7 +710,7 @@ Gateways integrate with the Exchange layer. Owners can host static sites where c *** Requirements -- Gateways MUST take CID-based Agora content and render it as HTML for legacy browsers. +- Gateways MUST take CID-based social protocol content and render it as HTML for legacy browsers. - Gateways MUST support SEO-friendly rendering for public content. - The system MUST allow anyone to run a Gateway (not restricted to Relay operators). - Gateways MUST NOT require authentication for public content. @@ -721,14 +721,14 @@ Gateways integrate with the Exchange layer. Owners can host static sites where c *** Relationship to Relays -- *Relays* serve Agora-native clients via WebSocket/pub-sub protocols. +- *Relays* serve protocol-native clients via WebSocket/pub-sub protocols. - *Gateways* serve legacy browsers via HTTP. - They are *separate infrastructure* - a Gateway may use Relays as a backend, but they're distinct services. *** Gateway Discovery **** Concept -Gateways bridge Agora content to the legacy web via HTTP. Discovery mechanisms are needed for clients to find reliable gateways to generate shareable HTTP links for their public content. +Gateways bridge social protocol content to the legacy web via HTTP. Discovery mechanisms are needed for clients to find reliable gateways to generate shareable HTTP links for their public content. **** Discovery Mechanisms @@ -745,10 +745,10 @@ Gateways bridge Agora content to the legacy web via HTTP. Discovery mechanisms a ** Infrastructure Discovery: DID Document Bindings -For a Persona to function within the network, its Decentralized Identifier (DID) must "bind" to specific infrastructure endpoints. This is achieved via the `service` section of the Agora DID Document. +For a Persona to function within the network, its Decentralized Identifier (DID) must "bind" to specific infrastructure endpoints. This is achieved via the `service` section of the social protocol DID Document. *** The Service Schema -Every Agora DID Document SHOULD include a list of service endpoints that allow other Personas and clients to locate the user's data and communication channels. +Every social protocol DID Document SHOULD include a list of service endpoints that allow other Personas and clients to locate the user's data and communication channels. #+begin_src json { @@ -782,7 +782,7 @@ Every Agora DID Document SHOULD include a list of service endpoints that allow o *** Concept -Agora's architectural strategy for client applications aims to balance user sovereignty with broad accessibility and app store compliance. Instead of relying solely on "sovereign clients" (full-featured applications running entirely on edge devices), a hybrid approach will be adopted: core client logic will reside closer to the Personal Data Store (PDS), with only a "thin client" deployed on edge devices (e.g., mobile apps, web browsers). This allows for greater flexibility in distribution and development. +The social protocol's architectural strategy for client applications aims to balance user sovereignty with broad accessibility and app store compliance. Instead of relying solely on "sovereign clients" (full-featured applications running entirely on edge devices), a hybrid approach will be adopted: core client logic will reside closer to the Personal Data Store (PDS), with only a "thin client" deployed on edge devices (e.g., mobile apps, web browsers). This allows for greater flexibility in distribution and development. *** Motivation: App Store Compliance & Broad Reach @@ -793,7 +793,7 @@ Traditional "sovereign client" models, where full application logic, data proces - Data storage and handling outside platform-defined sandboxes - Features deemed to circumvent platform monetization or control -The PDS-proximate / thin client model is a pragmatic solution to navigate these limitations, enabling Agora to reach a wider user base through conventional app distribution channels without compromising core protocol principles. +The PDS-proximate / thin client model is a pragmatic solution to navigate these limitations, enabling the social protocol to reach a wider user base through conventional app distribution channels without compromising core protocol principles. *** Strategic Advantages @@ -812,7 +812,7 @@ The PDS-proximate / thin client model is a pragmatic solution to navigate these *** Conclusion -The adoption of a PDS-proximate / thin client architecture is a strategic imperative for Agora to achieve mass adoption and navigate the complexities of modern app distribution, while simultaneously enhancing the capabilities of the Personal Data Store as a dynamic and powerful extension of the user's digital self. +The adoption of a PDS-proximate / thin client architecture is a strategic imperative for the social protocol to achieve mass adoption and navigate the complexities of modern app distribution, while simultaneously enhancing the capabilities of the Personal Data Store as a dynamic and powerful extension of the user's digital self. ** Related Documents diff --git a/ideas/agora/agora-requirements-04-the-primitive.org b/ideas/passepartout-social-protocol/requirements-04-the-primitive.org similarity index 88% rename from ideas/agora/agora-requirements-04-the-primitive.org rename to ideas/passepartout-social-protocol/requirements-04-the-primitive.org index 43338ae..beaa7b1 100644 --- a/ideas/agora/agora-requirements-04-the-primitive.org +++ b/ideas/passepartout-social-protocol/requirements-04-the-primitive.org @@ -1,4 +1,4 @@ -#+title: Agora Requirements - 04: The Primitive +#+title: Social Protocol Requirements - 04: The Primitive #+author: Amero Garcia #+created: [2026-03-16 Mon 14:28] #+DATE: 2026-03-15 @@ -9,17 +9,17 @@ :CREATED: [2026-05-24 Sun] :ID: f6cfc54b-919b-4311-bcbf-65e976755d40 :END: -* The Primitive: The Atomic Foundation of [[id:1d074690-a279-59cb-b91d-e9a22ae104ad][Agora]] +* The Primitive: The Atomic Foundation of [[id:1d074690-a279-59cb-b91d-e9a22ae104ad][Social Protocol]] ** Concept: The Universal Data Primitive -The Primitive is Agora's foundational content layer—the base data structure upon which all social interaction, economic exchange, and identity management is built. Before there are posts, contracts, or profiles, there are Notes. The Note is the atomic, universal unit of information in Agora. +The Primitive is the protocol's foundational content layer—the base data structure upon which all social interaction, economic exchange, and identity management is built. Before there are posts, contracts, or profiles, there are Notes. The Note is the atomic, universal unit of information in the protocol. -This elegant simplicity—the "Everything is a Note" paradigm—enables Agora's powerful interoperability, immutable audit trails, and seamless cross-application compatibility. By reducing all digital interactions to a single, cryptographically verifiable primitive, Agora creates a unified ecosystem where any application can understand and process any data, breaking down the silos that plague traditional digital platforms. +This elegant simplicity—the "Everything is a Note" paradigm—enables the protocol's powerful interoperability, immutable audit trails, and seamless cross-application compatibility. By reducing all digital interactions to a single, cryptographically verifiable primitive, the protocol creates a unified ecosystem where any application can understand and process any data, breaking down the silos that plague traditional digital platforms. ** The Note Structure -A Note is the atomic unit of information in Agora. Everything—posts, messages, contracts, profiles—is a Note with behavioral flags. +A Note is the atomic unit of information in the social protocol. Everything—posts, messages, contracts, profiles—is a Note with behavioral flags. *** Technical Specification @@ -68,7 +68,7 @@ The single `is_feed` property defines the behavioral intent of a Note without ch | `is_feed` | boolean | Chronological timeline item (Post, Status, Update). If false/omitted, the Note is a static Page. | *** The Contract & Payload Split -Every signed Note in Agora is inherently a contract. To clearly separate the "Rules of Engagement" from the "Asset", the Note structure defines two distinct fields: +Every signed Note in the social protocol is inherently a contract. To clearly separate the "Rules of Engagement" from the "Asset", the Note structure defines two distinct fields: - *`contract` (JSON Object):* Defines the terms. This includes both human-readable terms (e.g., `"license": "CC0"`) and machine-readable state (e.g., `"price_satoshis": 5000`). - *`payload` (Polymorphic String):* Defines the asset governed by the contract. This can be: @@ -90,7 +90,7 @@ The `notify` array defines who should receive a push notification or "Inbox" ale *** Semantic Derivations -Because Agora uses a minimalist flag system, high-level social and economic concepts are reconstructed by clients using core flags, audience scope (`access_control`), and Note relationships (`references`, `reply_to`, `notify`). +Because the social protocol uses a minimalist flag system, high-level social and economic concepts are reconstructed by clients using core flags, audience scope (`access_control`), and Note relationships (`references`, `reply_to`, `notify`). **** Basic Content - *Public Post:* `is_feed:true` + `access_control:[]` @@ -120,7 +120,7 @@ Because Agora uses a minimalist flag system, high-level social and economic conc *** Flag Combination Rules -Agora implements strict validation to ensure network integrity. +The social protocol implements strict validation to ensure network integrity. **** Rule 1: Flow (Feed vs. Page) - `is_feed: true` indicates chronological content. @@ -141,7 +141,7 @@ Agora implements strict validation to ensure network integrity. { "$schema": "http://json-schema.org/draft-07/schema#", "$id": "https://agora.ai/schemas/content-flags.json", - "title": "Agora Note Flags", + "title": "Social Protocol Note Flags", "description": "Validation schema for the Binary Core flag set", "type": "object", "properties": { @@ -263,10 +263,10 @@ Agora implements strict validation to ensure network integrity. *** Encryption: Security by Design -Security is woven into the fabric of the protocol. Agora uses industry-standard primitives to ensure that only intended recipients can access private content. +Security is woven into the fabric of the protocol. The social protocol uses industry-standard primitives to ensure that only intended recipients can access private content. - *End-to-End Encryption (E2EE):* Private Notes use AES-256-GCM for payloads and X25519 for ECDH key exchange. -- *Forward Secrecy:* Agora employs Double Ratchet for 1-on-1 messaging and MLS (Messaging Layer Security) for groups, rotating keys per-message. +- *Forward Secrecy:* The social protocol employs Double Ratchet for 1-on-1 messaging and MLS (Messaging Layer Security) for groups, rotating keys per-message. *** Ephemeral Content Enforcement @@ -285,7 +285,7 @@ The `is_ephemeral: true` flag is enforced through three complementary mechanisms ** Relationships, Sync & Performance *** Note Relationships -Agora uses three distinct fields to define relationships between Notes, balancing semantic precision with high-performance discovery. +The social protocol uses three distinct fields to define relationships between Notes, balancing semantic precision with high-performance discovery. **** Threading & Reference Logic @@ -314,7 +314,7 @@ Alice posts a product listing (Note A). Bob asks a question (Note B) about the l - *Streaming CIDs:* The root CID points to the tree, allowing concurrent, prioritized downloading of chunks. *** Real-time Sync & Collaboration -- *Live Collaboration:* Agora uses CRDTs (Conflict-free Replicated Data Types) for shared state (e.g., co-editing a document). +- *Live Collaboration:* The social protocol uses CRDTs (Conflict-free Replicated Data Types) for shared state (e.g., co-editing a document). - *Ephemeral Channels:* Real-time updates (like typing indicators) are broadcast via Relay WebSockets without being committed to the PDS as permanent Notes. *** Content Deduplication @@ -331,7 +331,7 @@ Alice posts a product listing (Note A). Bob asks a question (Note B) about the l "contract": { "license": "CC-BY-4.0" }, - "payload": "Hello, Agora!", + "payload": "Hello, Social Protocol!", "content_type": "text/markdown", "access_control": [], "createdAt": "2026-03-25T14:30:00Z", diff --git a/ideas/agora/agora-requirements-05-social.org b/ideas/passepartout-social-protocol/requirements-05-social.org similarity index 76% rename from ideas/agora/agora-requirements-05-social.org rename to ideas/passepartout-social-protocol/requirements-05-social.org index 3b48e9e..d72462c 100644 --- a/ideas/agora/agora-requirements-05-social.org +++ b/ideas/passepartout-social-protocol/requirements-05-social.org @@ -1,4 +1,4 @@ -#+title: Agora Requirements - 05: Social Space +#+title: Social Protocol Requirements - 05: Social Space #+author: Amero Garcia #+created: [2026-03-16 Mon 14:28] #+DATE: 2026-03-15 @@ -11,15 +11,15 @@ :END: * Social Space: Where Human Connection Becomes Sovereign -The Social Space is where [[id:1d074690-a279-59cb-b91d-e9a22ae104ad][Agora]]'s revolutionary architecture transforms how humans connect, communicate, and transact. Unlike traditional platforms that own your relationships and monetize your attention, Agora puts you in complete control of your social graph. Every interaction—from a casual conversation to a binding commercial contract—is self-owned, cryptographically secured, and entirely under your sovereignty. This is social interaction reimagined for a decentralized future. +The Social Space is where [[id:1d074690-a279-59cb-b91d-e9a22ae104ad][Social Protocol]]'s revolutionary architecture transforms how humans connect, communicate, and transact. Unlike traditional platforms that own your relationships and monetize your attention, the protocol puts you in complete control of your social graph. Every interaction—from a casual conversation to a binding commercial contract—is self-owned, cryptographically secured, and entirely under your sovereignty. This is social interaction reimagined for a decentralized future. ** Concept -Social Space encompasses all person-to-person and person-to-collective interaction in Agora: public and private, asynchronous and real-time. All social interaction is mediated by Notes and contracts running on the Exchange layer. +Social Space encompasses all person-to-person and person-to-collective interaction in the protocol: public and private, asynchronous and real-time. All social interaction is mediated by Notes and contracts running on the Exchange layer. ** Asynchronous Communication (Correspondence & Messaging) -Asynchronous communication in Agora utilizes the *Secure Communication Module (SCM)*, which enforces the *DIDComm v2 (Decentralized Identifier Communication)* protocol—a transport-agnostic standard for secure, private communication. +Asynchronous communication in the protocol utilizes the *Secure Communication Module (SCM)*, which enforces the *DIDComm v2 (Decentralized Identifier Communication)* protocol—a transport-agnostic standard for secure, private communication. - *Message Format:* All private messages MUST be formatted as JWM (JSON Web Messages). - *Encryption Suite:* JWMs MUST be wrapped in a JWE (JSON Web Encryption) envelope, utilizing X25519 for key agreement and AES-256-GCM for content encryption. @@ -32,11 +32,11 @@ Because a user's primary device (e.g., a phone) is not always online, the PDS ac - *Pickup:* When the recipient's device wakes up, it fetches the envelope from the PDS, decrypts it locally, and deletes the copy from the PDS. *** Contextual Isolation -Agora enforces strict multi-persona isolation. Each Persona (e.g., "Work," "Dating," "Personal") has a separate, cryptographically isolated message queue. A message sent to a user's Work DID never touches the inbox or metadata of their Dating DID, ensuring zero cross-context leakage. +The protocol enforces strict multi-persona isolation. Each Persona (e.g., "Work," "Dating," "Personal") has a separate, cryptographically isolated message queue. A message sent to a user's Work DID never touches the inbox or metadata of their Dating DID, ensuring zero cross-context leakage. ** The Unified Note Primitive -All asynchronous interaction in Agora—whether a public post or a private message—is built upon the same "Note" primitive. The behavior and visibility of a Note are defined by cryptographic signatures and a set of standardized metadata flags. +All asynchronous interaction in the protocol—whether a public post or a private message—is built upon the same "Note" primitive. The behavior and visibility of a Note are defined by cryptographic signatures and a set of standardized metadata flags. *** Flag Definitions & Storage Models @@ -55,7 +55,7 @@ Every async interaction is a Note identified by a Content Identifier (CID). This ** Directed Communication (Copy-on-Send Model) -For Notes intended for specific recipients (e.g., 1-on-1 messages, group chats), Agora employs a "Copy-on-Send" model to ensure recipient data ownership and high availability. +For Notes intended for specific recipients (e.g., 1-on-1 messages, group chats), the protocol employs a "Copy-on-Send" model to ensure recipient data ownership and high availability. *** Audience & Attention - *Audience:* Defined by the `access_control` array. These entities have the cryptographic right to own and decrypt the Note. @@ -69,14 +69,14 @@ This model ensures recipients have full ownership and control over the messages ** Social Publishing: Feeds & Streams -For content intended for a broad audience (e.g., social posts, public articles, project wikis), Agora uses a "Reference-on-Send" model to maximize efficiency and owner control. +For content intended for a broad audience (e.g., social posts, public articles, project wikis), the protocol uses a "Reference-on-Send" model to maximize efficiency and owner control. *** Concept: Feed vs. Stream - *The Feed:* A Persona's curated output of chronological entries (`is_feed: true`) and static resources (`is_feed: false`). - *The Stream:* A user's personalized, aggregated view of all the Feeds they follow. *** The "Lens" Architecture (Polymorphic UI) -Because all data in Agora shares the exact same base schema (The Atomic Note), client applications are not locked into "siloed" databases. Instead, data is a single pile of uniform "bricks." The client app acts as a *Lens* that filters this stream and adjusts its interface based on the Note's internal metadata. +Because all data in the protocol shares the exact same base schema (The Atomic Note), client applications are not locked into "siloed" databases. Instead, data is a single pile of uniform "bricks." The client app acts as a *Lens* that filters this stream and adjusts its interface based on the Note's internal metadata. - *Unified Content Schema:* Apps do not maintain separate APIs for videos, products, or posts. They read the universal Note structure. - *Dynamic Interfaces:* The UI interprets the `content_type` and `contract` fields to render the appropriate experience: @@ -100,10 +100,10 @@ The authoritative copy resides solely on the owner's PDS. Deletion by the owner ** Synchronous Communication (Live Voice & Video) -For real-time calls, Agora utilizes *WebRTC* with a decentralized twist for the signaling phase. +For real-time calls, the protocol utilizes *WebRTC* with a decentralized twist for the signaling phase. *** Decentralized Signaling -Traditional WebRTC requires a central signaling server to help devices discover each other. In Agora, the *DIDComm channel* handles the handshake: +Traditional WebRTC requires a central signaling server to help devices discover each other. In the protocol, the *DIDComm channel* handles the handshake: 1. *Request:* Persona A sends a "Call Request" via DIDComm to Persona B's PDS. 2. *Negotiation:* Persona B's phone receives the request and sends back its IP/ICE candidates (the "digital map") via the same secure DIDComm channel. 3. *P2P Tunnel:* Once the handshake is complete, voice/video data flows directly between the two devices. No server—not even the PDS—sees the call data. @@ -116,18 +116,18 @@ To address the need for absolute privacy and deniability, OTR mode completely by ** Encryption & Metadata Privacy -Agora's communication layer goes beyond standard end-to-end encryption to ensure long-term security and metadata protection. +The protocol's communication layer goes beyond standard end-to-end encryption to ensure long-term security and metadata protection. *** Double Ratchet Algorithm (Signal Protocol) Every single message uses a new, derived key. This ensures *Perfect Forward Secrecy (PFS)* and *Post-Compromise Security*. If a specific message key is ever compromised, it cannot be used to decrypt past or future messages in the conversation. *** Metadata Masking (Onion Routing) -To hide traffic patterns from network observers, Agora utilizes Tor-style *Onion Routing* between PDSs where possible. This masks who is talking to whom, preventing external observers from building a social graph based on connection frequency or message timing. +To hide traffic patterns from network observers, the protocol utilizes Tor-style *Onion Routing* between PDSs where possible. This masks who is talking to whom, preventing external observers from building a social graph based on connection frequency or message timing. ** Profiles *** Concept -A Profile is a public-facing presentation of a Persona. Agora supports multiple Profiles per Persona (e.g., a "Public Developer" profile and a "Private Family" profile). +A Profile is a public-facing presentation of a Persona. The protocol supports multiple Profiles per Persona (e.g., a "Public Developer" profile and a "Private Family" profile). *** Requirements - Each Profile MUST be a Note (CID) with public visibility. @@ -135,11 +135,11 @@ A Profile is a public-facing presentation of a Persona. Agora supports multiple - Profile updates create new CIDs, preserving a verifiable history of the identity's presentation. *** Profile as Static Site -Personas can publish their profiles and professional portfolios as decentralized static websites using the native hosting model (see [[id:3b43a9b8-31d1-4479-a35f-22273b74f0c7][Infrastructure]]). Agora-aware browsers render these natively from CIDs, while legacy browsers access them via Gateways with automated SSL and domain mapping. +Personas can publish their profiles and professional portfolios as decentralized static websites using the native hosting model (see [[id:3b43a9b8-31d1-4479-a35f-22273b74f0c7][Infrastructure]]). Protocol-aware browsers render these natively from CIDs, while legacy browsers access them via Gateways with automated SSL and domain mapping. ** The Attention Marketplace (The Information Router) -In traditional social media, the algorithm is a secret "Black Box" that sits between users and their social graph, deciding what is seen to maximize platform revenue. In Agora, the Algorithm Layer is reimagined as an open *Information Router*. By moving the algorithm out of the central server and into an open market, Agora empowers users to "hire and fire" the logic that sorts their attention. +In traditional social media, the algorithm is a secret "Black Box" that sits between users and their social graph, deciding what is seen to maximize platform revenue. In the protocol, the Algorithm Layer is reimagined as an open *Information Router*. By moving the algorithm out of the central server and into an open market, the protocol empowers users to "hire and fire" the logic that sorts their attention. *** Pluggable Feed Generation (PFG) Users subscribe to independent "Feed Generators" via an open API. This decoupling of data from sorting logic is achieved through a three-step workflow: @@ -155,7 +155,7 @@ Because the PFG API is open and transport-agnostic, different organizations comp - *Verification Services:* NGOs or fact-checking collectives can provide "Filtered Lenses" that prioritize highly-attested content. *** Decentralized Moderation (Competitive Labeling) -Moderation in Agora is treated as "Competitive Labeling" rather than central censorship. +Moderation in the protocol is treated as "Competitive Labeling" rather than central censorship. - *Labeler DIDs:* Independent services (NGOs, Fact Checkers, Church Groups) operate as "Labelers." They review the public firehose and "tag" content (e.g., "Spam," "Graphic," "High-Quality"). - *Client-Side Filtering:* The user's application pulls these public labels and applies the user's personal policy (e.g., "Hide anything labeled 'Graphic' by the NGO 'SafetyFirst'"). - *Stackable Moderation:* Users can subscribe to multiple labelers simultaneously to create a highly personalized, robust, and sovereign moderation filter. diff --git a/ideas/agora/agora-requirements-06-exchange-and-contracts.org b/ideas/passepartout-social-protocol/requirements-06-exchange-and-contracts.org similarity index 86% rename from ideas/agora/agora-requirements-06-exchange-and-contracts.org rename to ideas/passepartout-social-protocol/requirements-06-exchange-and-contracts.org index fe18d51..458b052 100644 --- a/ideas/agora/agora-requirements-06-exchange-and-contracts.org +++ b/ideas/passepartout-social-protocol/requirements-06-exchange-and-contracts.org @@ -1,4 +1,4 @@ -#+title: Agora Requirements - 06: Exchange +#+title: Social Protocol Requirements - 06: Exchange #+author: Amero Garcia #+created: [2026-03-16 Mon 14:28] #+DATE: 2026-03-15 @@ -13,7 +13,7 @@ ** Concept -The Exchange layer provides the economic substrate of [[id:1d074690-a279-59cb-b91d-e9a22ae104ad][Agora]]: value transfer via the Lightning Network, multi-currency support, and payment primitives. Built on top of Content Objects (see [[id:f6cfc54b-919b-4311-bcbf-65e976755d40][The Primitive]]) and Social relationships (see [[id:0f949f6c-4cf1-49eb-b9a4-ebcac27ee548][Social]]). +The Exchange layer provides the economic substrate of [[id:1d074690-a279-59cb-b91d-e9a22ae104ad][Social Protocol]]: value transfer via the Lightning Network, multi-currency support, and payment primitives. Built on top of Content Objects (see [[id:f6cfc54b-919b-4311-bcbf-65e976755d40][The Primitive]]) and Social relationships (see [[id:0f949f6c-4cf1-49eb-b9a4-ebcac27ee548][Social]]). ** Lightning Native @@ -52,7 +52,7 @@ The specification currently lacks explicit guidance on how end users run Lightni - Each user's client (desktop/mobile) runs an embedded Lightning node using LDK (Lightning Dev Kit) - User has full custody of keys; channels are mobile-friendly (LSP-managed) - PDS handles the always-online requirement since user devices aren't -- Aligns with Agora's "sovereign" philosophy but requires technical sophistication +- Aligns with the protocol's "sovereign" philosophy but requires technical sophistication **** Option 2: LSP (Lightning Service Provider) Model - User connects to an LSP that provides inbound liquidity and accepts payments on their behalf @@ -96,7 +96,7 @@ The specification has not yet decided between: ** Concept -The Agora protocol must support multiple currencies beyond Lightning-native satoshis to facilitate broader economic participation and provide stability options. While Lightning remains the primary rail for micro-payments, other assets will be integrated for larger transactions and specific use cases. +The protocol must support multiple currencies beyond Lightning-native satoshis to facilitate broader economic participation and provide stability options. While Lightning remains the primary rail for micro-payments, other assets will be integrated for larger transactions and specific use cases. ** Supported Currencies @@ -192,16 +192,16 @@ Payment for task completion: ** Sovereign Contract & Arbitration Layer (SCAL) -To enable Personas to execute binding agreements with decentralized dispute resolution, Agora implements SCAL. A contract in this system is not a static PDF; it is an executable cryptographic object. +To enable Personas to execute binding agreements with decentralized dispute resolution, the protocol implements SCAL. A contract in this system is not a static PDF; it is an executable cryptographic object. *** 1. The Ricardian Contract Module -[[id:b265f66d-f7b9-4ebd-b4e3-a82cefe23981][Agora contracts]] follow the Ricardian model, ensuring they are both human-readable and machine-executable. +[[id:b265f66d-f7b9-4ebd-b4e3-a82cefe23981][Social Protocol contracts]] follow the Ricardian model, ensuring they are both human-readable and machine-executable. - *Natural Language (The Markdown):* The human-readable terms of the agreement (e.g., "Person A delivers 100 bricks to Person B by Friday"). - *Machine Logic (The JSON-LD):* The executable parameters embedded in the Note's metadata (e.g., `due_date: 2026-01-16`, `price_sats: 50000`, `arbitrator_did: did:key:xyz`). - *The Merkle Link:* Both parts are hashed together into a single Content Identifier (CID). If a single comma is changed in the text, the hash changes, breaking the digital contract. This ensures the "Code" and the "Law" remain identical. *** 2. Payment & Escrow: The "HODL Invoice" -For service delivery and physical goods, Agora relies on Lightning HODL Invoices as a trustless escrow, removing the need for a custodial middleman. +For service delivery and physical goods, the protocol relies on Lightning HODL Invoices as a trustless escrow, removing the need for a custodial middleman. - *Commitment:* The Buyer "pays" the invoice. The funds leave their Lightning wallet but remain cryptographically locked in the network routing nodes. - *The Proof:* The Seller observes the network state, sees the funds are "Locked," and confidently delivers the goods or services. - *Settlement:* Once the Buyer confirms receipt, they release the cryptographic Preimage (the key). The money instantly settles to the Seller. @@ -241,7 +241,7 @@ Transactions reference the Content Objects they interact with: ** Content Monetization & Seeder Rewards -To monetize high-bandwidth content (like video or software) in a decentralized, permissionless network, Agora utilizes a combination of Split-State Encryption, the LSAT protocol, and granular Lightning network routing. This ensures creators get paid without relying on centralized DRM or hosting providers. +To monetize high-bandwidth content (like video or software) in a decentralized, permissionless network, the protocol utilizes a combination of Split-State Encryption, the LSAT protocol, and granular Lightning network routing. This ensures creators get paid without relying on centralized DRM or hosting providers. *** 1. The Encrypted Swarm (Blind CDN) If you want to charge for a video, you cannot send the raw file into the P2P swarm. If you did, the first "seeder" would simply share the unencrypted version for free. @@ -250,13 +250,13 @@ If you want to charge for a video, you cannot send the raw file into the P2P swa - *Blind Replication:* Followers and network participants host and seed this encrypted `payload`. They act as a "Blind CDN" (Content Delivery Network)—hosting a file they cannot see. *** 2. The LSAT Protocol (The Smart Ticket) -To automate the purchase and unlocking of this content, Agora uses LSATs (Lightning Service Authentication Tokens). +To automate the purchase and unlocking of this content, the social protocol uses LSATs (Lightning Service Authentication Tokens). - *The 402 Challenge:* When a viewer clicks "Play," their client attempts to fetch the payload. The PDS responds with an HTTP 402 (Payment Required) error, containing a Lightning Invoice (generated based on the `contract` terms) and a "Macaroon" (a digital ticket). - *The Unlock:* Once the user pays the invoice (e.g., 100 sats), they receive a cryptographic Preimage (proof of payment). They send this Preimage back to the PDS. - *The Result:* The PDS validates the proof and releases the Decryption Key. The video decodes instantly on the client's device. The data may have been downloaded from a friend's PDS (the swarm), but the permission to view it was purchased securely from the creator. *** 3. Incentivizing the Seeders (Paid Seeding) -One of Agora's most innovative features is "Seeder Micro-Rewards." If a follower provides the bandwidth that allows a creator's content to go viral, the network can programmatically share the revenue. +One of the social protocol's most innovative features is "Seeder Micro-Rewards." If a follower provides the bandwidth that allows a creator's content to go viral, the network can programmatically share the revenue. - *The Split Payment:* The Note's `contract` can define a Lightning routing split. When the 100 sats are paid via the LSAT, the network routes the funds accordingly: - *90 sats* go to the Creator. - *5 sats* go to the Indexing Relay. @@ -264,7 +264,7 @@ One of Agora's most innovative features is "Seeder Micro-Rewards." If a follower - *The Economic Shift:* "Following" an NGO or an indie creator becomes a way to earn a tiny amount of Bitcoin while supporting their mission. The better the content you seed, the more "tips" your server collects for providing the bandwidth. *** Physical Collateralization -In environments with weak state enforcement, Agora enables the use of physical assets as cryptographically-secured collateral via the PAL (Physical Asset Linking) protocol. +In environments with weak state enforcement, the social protocol enables the use of physical assets as cryptographically-secured collateral via the PAL (Physical Asset Linking) protocol. - *The Pledge:* A user links a Digital Twin token (representing a physical asset like a car or machine) to a Civil Contract Note. - *The Lock:* The contract's logic "freezes" the Digital Twin token. While the user maintains physical possession of the asset, they are cryptographically barred from selling or transferring the digital title until the contract obligations (e.g., a loan repayment) are met. @@ -275,7 +275,7 @@ In environments with weak state enforcement, Agora enables the use of physical a ** Cross-Chain Swaps **** Atomic Swaps Architecture -Agora enables seamless value transfer between Bitcoin and other blockchains without relying on centralized exchanges. +The social protocol enables seamless value transfer between Bitcoin and other blockchains without relying on centralized exchanges. - *HTLC Contracts:* Hash Time-Locked Contracts (HTLCs) are used to lock assets on both chains simultaneously. - *Swap Personas:* Specialized Personas (Market Makers) provide liquidity and act as counterparties for atomic swaps, competing on fees and speed. - *Protocol Integration:* A `CrossChainSwap` Content Object defines the terms (rate, chains, timelock). Once agreed, both parties publish the HTLCs on their respective chains. The revelation of the preimage on one chain allows claiming the funds on the other. @@ -284,15 +284,15 @@ Agora enables seamless value transfer between Bitcoin and other blockchains with **** RGB Protocol Specification Stablecoins (e.g., USDT, USDC) are supported natively as Layer 2 assets on top of Bitcoin/Lightning using the RGB protocol. -- *Asset Issuance:* Stablecoin issuers maintain a Genesis Contract on Agora defining the asset's RGB schema and initial supply. -- *Client Support:* Agora clients MUST integrate an RGB node alongside their Lightning node to parse client-side validated state transitions. +- *Asset Issuance:* Stablecoin issuers maintain a Genesis Contract in the protocol defining the asset's RGB schema and initial supply. +- *Client Support:* Social protocol clients MUST integrate an RGB node alongside their Lightning node to parse client-side validated state transitions. - *Payment Routing:* RGB assets are routed over standard Lightning channels. Clients construct invoices that specifically request the RGB stablecoin asset ID instead of raw satoshis. - *PDS Storage:* The client-side validation data (consignment) for RGB assets is stored as encrypted Content Objects in the user's PDS, ensuring the user maintains full custody of the asset's history. ** Subscription Management **** Complex Recurring Billing Logic -Agora handles recurring payments natively without centralized payment processors. +The social protocol handles recurring payments natively without centralized payment processors. - *Subscription Objects:* A `SubscriptionContract` defines the terms: amount, currency, billing cycle (e.g., monthly, weekly), and grace period. - *Streaming vs. Discrete Billing:* - For continuous services (e.g., Relay access), streaming payments (sats/second) are preferred. diff --git a/ideas/agora/agora-requirements-07-advanced-integration.org b/ideas/passepartout-social-protocol/requirements-07-advanced-integration.org similarity index 97% rename from ideas/agora/agora-requirements-07-advanced-integration.org rename to ideas/passepartout-social-protocol/requirements-07-advanced-integration.org index e5175bb..01d9560 100644 --- a/ideas/agora/agora-requirements-07-advanced-integration.org +++ b/ideas/passepartout-social-protocol/requirements-07-advanced-integration.org @@ -1,4 +1,4 @@ -#+title: Agora Requirements - 07: Advanced Integration +#+title: Social Protocol Requirements - 07: Advanced Integration #+author: Amero Garcia #+created: [2026-03-16 Mon 14:28] #+DATE: 2026-03-15 @@ -15,7 +15,7 @@ *** Overview -[[id:1d074690-a279-59cb-b91d-e9a22ae104ad][Agora]] enables AI at multiple layers: as sovereign actors, personal assistants, algorithms, and collaborative agents. All AI interactions are economically mediated via Lightning and respect user data sovereignty. +[[id:1d074690-a279-59cb-b91d-e9a22ae104ad][Social Protocol]] enables AI at multiple layers: as sovereign actors, personal assistants, algorithms, and collaborative agents. All AI interactions are economically mediated via Lightning and respect user data sovereignty. *** AI Personas (Sovereign AI Actors) @@ -101,7 +101,7 @@ AI Personas can operate as specialized reputation oracles and adjudicators withi - *Automated Labeling:* AI agents can act as high-speed "Labelers" (see Social Moderation), tagging millions of posts for quality, spam, or sentiment, which users can then choose to route their feed through or ignore. **** Requirements -- AI Personas MUST be able to query other AI Personas via standard Agora messaging. +- AI Personas MUST be able to query other AI Personas via standard protocol messaging. - AI-to-AI communication MUST use the same Content Object primitives as human communication. - AI Personas MUST be able to negotiate service terms (price, scope, timeline) via smart contracts. - AI-to-AI transactions MUST be economically settled via Lightning. @@ -136,7 +136,7 @@ AI Personas can operate as specialized reputation oracles and adjudicators withi - The system MUST instantiate physical entities (events, locations) as Collective Personas (DIDs). - Users MUST be able to publish signed Proof-of-Presence Objects. - Every smart device MUST be a persona under the control of the user's master key. -- Devices MUST communicate using the standard Agora protocol with Consent Contracts. +- Devices MUST communicate using the standard protocol with Consent Contracts. - Sensor data MUST be published as encrypted Content Objects. - Users MUST be able to sell signed sensor data to Data Collector Personas. @@ -385,7 +385,7 @@ interface KeyRotation { *** Hardware-Backed Contract Enforcement (The "IoT Stick") -For high-stakes physical assets (e.g., tractors, factory machinery, or smart-lock-equipped real estate), Agora supports hardware-level enforcement of contract obligations. +For high-stakes physical assets (e.g., tractors, factory machinery, or smart-lock-equipped real estate), the protocol supports hardware-level enforcement of contract obligations. - *Binding IoT to Contract:* A physical asset's IoT sensor or "Smart Lock" is cryptographically bound to a specific Civil Contract Note. - *Enforcement Signal:* The machine's firmware is configured to listen for signed state updates from the contract's designated Arbitration (HDR) module. @@ -465,5 +465,5 @@ interface PhysicalAccessContract { ** Related Documents -- Agora AI Personas & Privacy -- Agora Physical World & IoT +- Protocol AI Personas & Privacy +- Protocol Physical World & IoT diff --git a/ideas/agora/agora-requirements-08-library.org b/ideas/passepartout-social-protocol/requirements-08-library.org similarity index 88% rename from ideas/agora/agora-requirements-08-library.org rename to ideas/passepartout-social-protocol/requirements-08-library.org index 7cc6b2d..d84e144 100644 --- a/ideas/agora/agora-requirements-08-library.org +++ b/ideas/passepartout-social-protocol/requirements-08-library.org @@ -1,4 +1,4 @@ -#+title: Agora Requirements - 08: Library +#+title: Social Protocol Requirements - 08: Library #+author: Amero Garcia #+created: [2026-03-16 Mon 14:28] #+DATE: 2026-03-14 @@ -43,7 +43,7 @@ The Library consists of three core components: - Full-text search across documents, subtitles, metadata - Tag-based organization (genre, year, creator, etc.) - Content deduplication via CID comparison -- Integration with [[id:1d074690-a279-59cb-b91d-e9a22ae104ad][Agora]]'s discovery layer for shared content +- Integration with [[id:1d074690-a279-59cb-b91d-e9a22ae104ad][Social Protocol]]'s discovery layer for shared content *** Library Managers @@ -98,23 +98,23 @@ Archiving preserves Content Objects and open web content for long-term access, c - Archive verification via multiple sources (Wayback Machine, Archive.today, personal PDS) - Content authenticity via hash verification against original -*** Integration with Agora +*** Integration with the Social Protocol - Library content can be referenced in posts, messages, and profiles - Content can be shared via Relays with appropriate encryption - Micro-payments for premium content access -- Syndication to Agora-aware browsers and gateways +- Syndication to protocol-aware browsers and gateways ** Requirements - The system MUST support unified content management across all media types. - The system MUST content-address all library items via CID. - The system MUST support local indexing for fast search. -- The system MUST allow content sharing via Agora's social layer. +- The system MUST allow content sharing via the protocol's social layer. - The system MUST support offline access for synced content. -- The system MUST integrate with Agora's economic layer for paid content. +- The system MUST integrate with the protocol's economic layer for paid content. ** Related Documents -- Agora Unified Content Primitive -- Agora PDS & Relay Architecture +- Protocol Unified Content Primitive +- Protocol PDS & Relay Architecture diff --git a/ideas/agora/agora-requirements-09-implementation.org b/ideas/passepartout-social-protocol/requirements-09-implementation.org similarity index 92% rename from ideas/agora/agora-requirements-09-implementation.org rename to ideas/passepartout-social-protocol/requirements-09-implementation.org index b177867..e066655 100644 --- a/ideas/agora/agora-requirements-09-implementation.org +++ b/ideas/passepartout-social-protocol/requirements-09-implementation.org @@ -1,4 +1,4 @@ -#+title: Agora Requirements - 09: Implementation +#+title: Social Protocol Requirements - 09: Implementation #+author: Amero Garcia #+created: [2026-03-16 Mon 14:28] #+DATE: 2026-03-14 @@ -70,7 +70,7 @@ The client MUST be capable of handling asynchronous events pushed from the Gover *** Protocol-First Design -[[id:1d074690-a279-59cb-b91d-e9a22ae104ad][Agora]] is a set of open protocols, not a single API service. Developers build against the *Agora Specification (v1.0)*, which defines the core data formats and transport methods. +[[id:1d074690-a279-59cb-b91d-e9a22ae104ad][Social Protocol]] is a set of open protocols, not a single API service. Developers build against the *social protocol Specification (v1.0)*, which defines the core data formats and transport methods. *** Core Protocol Versioning @@ -102,18 +102,18 @@ The client MUST be capable of handling asynchronous events pushed from the Gover - *CID (Content-ID):* Multibase + Multicodec + Multihash. - *Serialization:* Protocol Buffers (v3) for high performance and strict typing. -- *Envelopes:* Signed and encrypted payloads follow a standard *Agora Envelope* format (`proof`, `encryption_metadata`, `payload`). +- *Envelopes:* Signed and encrypted payloads follow a standard *social protocol Envelope* format (`proof`, `encryption_metadata`, `payload`). ** Testing & Adversarial *** Testing Philosophy -Agora's decentralized and sovereign nature requires a multi-layered testing strategy that goes beyond standard unit tests. We must test for *Network Resilience*, *Adversarial Resiliency*, and *Game-Theoretic Stability*. +The social protocol's decentralized and sovereign nature requires a multi-layered testing strategy that goes beyond standard unit tests. We must test for *Network Resilience*, *Adversarial Resiliency*, and *Game-Theoretic Stability*. *** Core Testing Tiers **** Unit & Integration Tests -- *Protocol Conformance:* Every client and service must pass a standard *Agora Protocol Conformance Suite* to ensure they correctly implement the V1.0 spec. +- *Protocol Conformance:* Every client and service must pass a standard *Social Protocol Conformance Suite* to ensure they correctly implement the V1.0 spec. - *Cryptography Validation:* Rigorous testing of key derivation, encryption/decryption, and signature verification using known-good test vectors. **** Network & Chaos Testing @@ -140,19 +140,19 @@ Agora's decentralized and sovereign nature requires a multi-layered testing stra *** Migration from Centralized Platforms -- *The "Migration" Skill:* An Agora skill that imports a user's content and social graph from centralized platforms (e.g., via Twitter Archive or ActivityPub). +- *The "Migration" Skill:* A social protocol skill that imports a user's content and social graph from centralized platforms (e.g., via Twitter Archive or ActivityPub). - *Social Graph Porting:* Tools to extract and import follower lists, enabling seamless transition. -*** Agora-to-Web Gateways +*** Social Protocol-to-Web Gateways -See [[id:3b43a9b8-31d1-4479-a35f-22273b74f0c7][Infrastructure - Agora-to-Web Gateways]] for detailed requirements. Implementation notes: -- Clients SHOULD provide links to Gateway-rendered versions of public content for sharing with non-Agora users. +See [[id:3b43a9b8-31d1-4479-a35f-22273b74f0c7][Infrastructure - Social Protocol-to-Web Gateways]] for detailed requirements. Implementation notes: +- Clients SHOULD provide links to Gateway-rendered versions of public content for sharing with users not on the social protocol. - Clients MAY embed Gateway content in web views for hybrid experiences. ** Conflict Resolution Algorithm *** Concept -Due to the offline-first nature of Agora clients and multi-device usage, identical or overlapping modifications to the same logical object (e.g., updating a profile, adding to a specific thread) can occur concurrently without network coordination. A deterministic, Merkle tree-based conflict resolution algorithm ensures that all PDS nodes and clients eventually reach the same state. +Due to the offline-first nature of social protocol clients and multi-device usage, identical or overlapping modifications to the same logical object (e.g., updating a profile, adding to a specific thread) can occur concurrently without network coordination. A deterministic, Merkle tree-based conflict resolution algorithm ensures that all PDS nodes and clients eventually reach the same state. *** Merkle Tree Structure - Every Persona's state is represented as a Merkle Directed Acyclic Graph (DAG). @@ -167,7 +167,7 @@ Due to the offline-first nature of Agora clients and multi-device usage, identic *** Deterministic Resolution Rules (LWW-Tiebreaker) -To automatically resolve conflicts without user intervention, Agora employs a deterministic algorithm based on logical clocks and cryptographic tie-breakers: +To automatically resolve conflicts without user intervention, the social protocol employs a deterministic algorithm based on logical clocks and cryptographic tie-breakers: 1. *Logical Clock (Lamport Timestamps):* - Every Content Object includes a logical sequence number (`seq`) incremented with each update by the owner. @@ -197,9 +197,9 @@ If the conflict involves high-stakes data (e.g., overlapping Genesis Contract up ** Related Documents -- Agora Client App Architecture -- Agora API & Protocol Versioning Spec -- Agora Testing, Chaos, and Adversarial +- Social Protocol Client App Architecture +- Social Protocol API & Protocol Versioning Spec +- Social Protocol Testing, Chaos, and Adversarial ** Delta Sync Protocol diff --git a/ideas/agora/agora-requirements-10-governance-and-assets.org b/ideas/passepartout-social-protocol/requirements-10-governance-and-assets.org similarity index 82% rename from ideas/agora/agora-requirements-10-governance-and-assets.org rename to ideas/passepartout-social-protocol/requirements-10-governance-and-assets.org index 01d711e..8408906 100644 --- a/ideas/agora/agora-requirements-10-governance-and-assets.org +++ b/ideas/passepartout-social-protocol/requirements-10-governance-and-assets.org @@ -1,4 +1,4 @@ -#+title: Agora Requirements - 10: Governance and Physical Assets +#+title: Social Protocol Requirements - 10: Governance and Physical Assets #+author: Amero Garcia #+created: [2026-03-22 Sun] #+ID: agora-requirements-10-governance @@ -12,12 +12,12 @@ ** Overview -This section expands [[id:1d074690-a279-59cb-b91d-e9a22ae104ad][Agora]]'s capabilities beyond digital communication and into physical reality and organizational coordination. By integrating Physical Asset Linking (PAL) and the Governance Executable Module (GEM), Agora empowers Collectives to manage real-world resources and execute democratic decisions autonomously via smart contracts. +This section expands [[id:1d074690-a279-59cb-b91d-e9a22ae104ad][Social Protocol]]'s capabilities beyond digital communication and into physical reality and organizational coordination. By integrating Physical Asset Linking (PAL) and the Governance Executable Module (GEM), the protocol empowers Collectives to manage real-world resources and execute democratic decisions autonomously via smart contracts. ** Governance Executable Module (GEM) ** Concept -Governance in Agora isn't just about voting; it's about executing the results of those votes. The GEM ensures that when a community (a Collective Persona) makes a decision, the protocol enforces it without relying on trusted intermediaries or manual intervention. +Governance in the protocol isn't just about voting; it's about executing the results of those votes. The GEM ensures that when a community (a Collective Persona) makes a decision, the protocol enforces it without relying on trusted intermediaries or manual intervention. ** The Governance Stack Governance operates at three distinct scales, mirroring the human organization patterns of the Sovereign Stack: @@ -38,7 +38,7 @@ A Collective Persona's rules are stored as an executable Smart Constitution. ** Evolvable Governance: Adaptive Constitutions -Unlike traditional blockchain-based DAOs, where governance rules are often "frozen" in immutable smart contract code, Agora DAOs (Collectives) are designed to be evolvable. While the *history* of every decision is immutable and cryptographically traceable, the *active rules* of the organization can be updated through its own internal governance process. +Unlike traditional blockchain-based DAOs, where governance rules are often "frozen" in immutable smart contract code, the protocol's DAOs (Collectives) are designed to be evolvable. While the *history* of every decision is immutable and cryptographically traceable, the *active rules* of the organization can be updated through its own internal governance process. *** Immutable History, Mutable State Every version of a Collective's Smart Constitution, every vote cast, and every policy change is recorded as a signed Note identified by a unique CID. This creates a perfect, unalterable audit trail. However, the "current state" of the Collective is defined by the most recent validly signed constitutional Note. This allows the organization to learn, adapt, and correct its course over time without requiring complex migrations or "forking" into entirely new software deployments. @@ -47,7 +47,7 @@ Every version of a Collective's Smart Constitution, every vote cast, and every p The GEM supports recursive governance: the rules for *how* to change the rules are themselves defined within the Smart Constitution. A Collective might start with a simple multi-sig requirement for all changes and later vote to transition to a more complex Quadratic Voting model for policy updates, all while maintaining a continuous cryptographic identity. *** Forks as a Sovereign Safety Valve -Because Agora is decentralized and permissionless, "forking" is a legitimate and supported governance mechanism. If a minority of a Collective disagrees fundamentally with a constitutional change, they can choose to "fork" the organization by creating a new Collective Persona based on the previous CID of the constitution. This ensures that no community is ever trapped by a "majority tyranny" that has lost its original purpose. +Because the protocol is decentralized and permissionless, "forking" is a legitimate and supported governance mechanism. If a minority of a Collective disagrees fundamentally with a constitutional change, they can choose to "fork" the organization by creating a new Collective Persona based on the previous CID of the constitution. This ensures that no community is ever trapped by a "majority tyranny" that has lost its original purpose. ** Automated Treasury Payroll (Streaming Lightning) The GEM connects governance directly to economic flow. @@ -75,7 +75,7 @@ PAL allows users to secure loans or agreements using physical assets as collater ** Decentralized Justice & Dispute Resolution (The Court System) -To enforce Civil Contracts and resolve Governance disputes without a central state, Agora implements a Hierarchical Dispute Resolution (HDR) framework. This mirrors the traditional legal system but replaces "jurisdiction by geography" with "jurisdiction by reputation and stake." +To enforce Civil Contracts and resolve Governance disputes without a central state, the protocol implements a Hierarchical Dispute Resolution (HDR) framework. This mirrors the traditional legal system but replaces "jurisdiction by geography" with "jurisdiction by reputation and stake." *** The Multi-Level "Court" Hierarchy Disputes are not settled by a single monolithic entity. Parties opt into a hierarchy of arbitration when creating a contract. @@ -91,6 +91,6 @@ In this system, an "Appeal" isn't a bureaucratic request; it is a *Cryptographic - *Finality:* Level 3 is the "Final Court of Appeal." Once the global jury rules, their combined threshold signature releases the cryptographic keys. The smart contract executes the payment automatically—no human can stop it. *** Why This Works in "Weak States" (Self-Executing Justice) -In jurisdictions where state police won't help collect a debt, or where courts are corrupt/slow, Agora provides Self-Executing Justice. It relies on two powerful enforcement mechanisms rather than physical violence: +In jurisdictions where state police won't help collect a debt, or where courts are corrupt/slow, the protocol provides Self-Executing Justice. It relies on two powerful enforcement mechanisms rather than physical violence: 1. *The Escrow Stick:* The funds are already gone from the buyer's wallet. They are locked cryptographically in a Lightning HODL Escrow. The buyer cannot "run away" with the money; they must engage in the arbitration process to get it back or see it released to the seller. 2. *The Reputation Stick:* In a decentralized society, a Persona's DID is their livelihood. Defying a Level 3 ruling, or accumulating a history of defaulted contracts, destroys a Persona's "Trust Score." In a system built on verifiable attestations, losing this reputation is a digital death sentence for a business, making compliance highly incentivized. \ No newline at end of file diff --git a/ideas/agora/agora-requirements-10-user-journey.org b/ideas/passepartout-social-protocol/requirements-10-user-journey.org similarity index 90% rename from ideas/agora/agora-requirements-10-user-journey.org rename to ideas/passepartout-social-protocol/requirements-10-user-journey.org index 764121f..23f9aa3 100644 --- a/ideas/agora/agora-requirements-10-user-journey.org +++ b/ideas/passepartout-social-protocol/requirements-10-user-journey.org @@ -1,5 +1,5 @@ -#+title: Agora Requirements: User Journey & Product Experience -#+AUTHOR: Project Agora +#+title: Social Protocol Requirements: User Journey & Product Experience +#+AUTHOR: Passepartout Social Protocol #+DATE: 2026-03-26 :PROPERTIES: @@ -8,7 +8,7 @@ :END: * The Sovereign User Journey -This document outlines the cohesive, narrative user journey of the [[id:1d074690-a279-59cb-b91d-e9a22ae104ad][Agora]] platform, illustrating how the underlying technical primitives (Master Keys, DIDs, PDS, Lightning, and Smart Contracts) translate into a seamless product experience. +This document outlines the cohesive, narrative user journey of the [[id:1d074690-a279-59cb-b91d-e9a22ae104ad][Social Protocol]] platform, illustrating how the underlying technical primitives (Master Keys, DIDs, PDS, Lightning, and Smart Contracts) translate into a seamless product experience. ** Phase 1: Onboarding (The Birth of the Persona) diff --git a/ideas/agora/agora-requirements-11-assessment.org b/ideas/passepartout-social-protocol/requirements-11-assessment.org similarity index 73% rename from ideas/agora/agora-requirements-11-assessment.org rename to ideas/passepartout-social-protocol/requirements-11-assessment.org index 3df5a4f..5ecf856 100644 --- a/ideas/agora/agora-requirements-11-assessment.org +++ b/ideas/passepartout-social-protocol/requirements-11-assessment.org @@ -1,4 +1,4 @@ -#+title: Agora Requirements - 11: Realistic Assessment +#+title: Social Protocol Requirements - 11: Realistic Assessment #+author: Amero Garcia #+created: [2026-03-16 Mon 14:28] #+DATE: 2026-03-22 @@ -11,14 +11,14 @@ :END: * Realistic Assessment: Practicality, Technology, and Performance -The [[id:1d074690-a279-59cb-b91d-e9a22ae104ad][Agora]] Protocol, following the integration of the Aletheia architecture, represents a significant leap beyond simple social networking into a comprehensive "Sovereign Social Operating System." This assessment evaluates the protocol's viability across three critical pillars. +The [[id:1d074690-a279-59cb-b91d-e9a22ae104ad][Social Protocol]], following the integration of the Aletheia architecture, represents a significant leap beyond simple social networking into a comprehensive "Sovereign Social Operating System." This assessment evaluates the protocol's viability across three critical pillars. ** 1. Practicality: The Sovereignty vs. UX Trade-off -Agora's practicality hinges on whether users can manage its cryptographic complexity without constant friction. +The protocol's practicality hinges on whether users can manage its cryptographic complexity without constant friction. *** Strengths -- *Functional Autonomy:* The "Sub-Root" HD derivation path (`m/44'/1'/account'/persona'/key_purpose/key_index`) is a major practical win. By allowing devices to derive operational keys (Lightning, PGP) autonomously, Agora reduces the "[[id:84a537b4-4256-50c8-91f5-dd5b4538418f][Hardware]] Wallet Fatigue" that plagues self-sovereign systems. +- *Functional Autonomy:* The "Sub-Root" HD derivation path (`m/44'/1'/account'/persona'/key_purpose/key_index`) is a major practical win. By allowing devices to derive operational keys (Lightning, PGP) autonomously, the protocol reduces the "[[id:84a537b4-4256-50c8-91f5-dd5b4538418f][Hardware]] Wallet Fatigue" that plagues self-sovereign systems. - *Unified Logic:* The "Everything is a Note" model simplifies the backend infrastructure (PDS/Relays), as they only need to handle a single data structure regardless of whether it's a social post or a legal contract. *** Challenges @@ -31,7 +31,7 @@ The technical stack is grounded in industry-standard primitives used in Bitcoin *** Technological Pillars - *Identity:* Leveraging BIP-44 and Ed25519 provides a battle-tested foundation for unlinkable personas. -- *Privacy:* The combination of E2EE (Double Ratchet/MLS), Blinded Sharding, and Zero-Knowledge Proofs (ZKPs) for cross-persona Notes places Agora at the forefront of privacy-preserving social protocols. +- *Privacy:* The combination of E2EE (Double Ratchet/MLS), Blinded Sharding, and Zero-Knowledge Proofs (ZKPs) for cross-persona Notes places the protocol at the forefront of privacy-preserving social protocols. - *Commerce:* Integrating LSATs and HODL invoices directly into the content layer (SCAL) is technically sound but relies heavily on the continued [[id:26f3e845-5eb4-4bcd-9cff-28e219934841][growth]] and stability of the Lightning Network. *** Critical Risks @@ -40,14 +40,14 @@ The technical stack is grounded in industry-standard primitives used in Bitcoin ** 3. Performance: Scalability and Efficiency -Agora's performance model is decentralized by design, avoiding the "Global State" bottlenecks of traditional blockchains. +The protocol's performance model is decentralized by design, avoiding the "Global State" bottlenecks of traditional blockchains. *** Scaling Models - *Reference-on-Send (Public Content):* Highly scalable. Only notifications and CIDs are pushed; content is pulled on-demand. This mirrors the efficient scaling of the web (CDNs/caching). - *Copy-on-Send (Private Content):* Resource-intensive. A direct message to 100 people creates 100 unique, encrypted Notes. While this ensures sovereignty, it places a higher storage and bandwidth burden on PDS providers compared to "Single-Instance" storage models. *** Optimization Strategies -- *Delta Sync:* Essential for mobile performance. By only transferring differential updates between the Client and PDS, Agora can maintain low latency even over poor network connections. +- *Delta Sync:* Essential for mobile performance. By only transferring differential updates between the Client and PDS, the protocol can maintain low latency even over poor network connections. - *Relay-as-Indexer:* High-performance Relays can act as opt-in indexers, providing fast search and discovery without users surrendering their data ownership. ** Success Probability & Timeline @@ -67,7 +67,7 @@ Agora's performance model is decentralized by design, avoiding the "Global State ** Conclusion: A Pragmatic Revolution -Agora is technically viable but architecturally demanding. It is not a project that can be built by a single "full-stack developer" in a weekend. It requires a specialized team of cryptographers, systems engineers, and UX designers. However, because it avoids the "Global Consensus" trap of blockchains, its performance characteristics are much closer to the traditional web, making it a truly practical alternative for building a sovereign digital civilization. +The protocol is technically viable but architecturally demanding. It is not a project that can be built by a single "full-stack developer" in a weekend. It requires a specialized team of cryptographers, systems engineers, and UX designers. However, because it avoids the "Global Consensus" trap of blockchains, its performance characteristics are much closer to the traditional web, making it a truly practical alternative for building a sovereign digital civilization. ** Related Documents diff --git a/ideas/passepartout/_index.org b/ideas/passepartout/_index.org new file mode 100644 index 0000000..0fa0e01 --- /dev/null +++ b/ideas/passepartout/_index.org @@ -0,0 +1,30 @@ +:PROPERTIES: +:CREATED: [2026-05-24 Sun] +:ID: 5e7f1d2a-3b4c-5d6e-7f8a-9b0c1d2e3f4a +:END: +#+title: Passepartout — Architecture Section Index +#+filetags: :passepartout:index: + +This section documents the Passepartout architecture: the staged build-out from conventional computing through verified infrastructure, the subsystems, and the systemic effects of verification becoming the default. + +**Architecture overviews:** +- [[id:1c3ec48b-446c-50d2-b53e-126a81f5143f][Architecture index]] — Passepartout architecture, market, revenue paths +- [[id:a1fac32a-47de-5fbd-b67d-29152c851747][Architecture overview]] — the three subsystems at a glance +- [[id:42c86e6f-4f27-4993-8238-b7bc7d15fb7b][Environment subsystem]] — the Lisp image, editor, browser, shell, hardware + +**Staged roadmap (progressive capability layers):** +Each stage covers: what is added, what threats are eliminated, what it costs, when it is viable. + +| Stage | Delivers | Key cost | Timeline | +|-------+----------+----------+----------| +| [[id:4a1f23b0-abc1-4def-9876-543210abcdef][0 — Now]] | Baseline: conventional computing | Patching treadmill, no deductive guarantees | Today | +| [[id:4a1f23b0-abc2-4def-9876-543210abcdef][1 — Social Protocol]] | Communication integrity, provable DAG | Crypto overhead, key management | Today | +| [[id:4a1f23b0-abc3-4def-9876-543210abcdef][2 — Verification]] | Verified gate, capability auth | Policy formalization burden | Today (limited) | +| [[id:4a1f23b0-abc4-4def-9876-543210abcdef][3 — Lisp Machine]] | Lisp image, Merkle memory, no kernel | Lisp tax, no backward compat, single address space | 2-5yr (soft) / 5-10yr (ASIC) | +| [[id:4a1f23b0-abc5-4def-9876-543210abcdef][4 — Inference]] | In-process LLM, token interception | ~10x compute/RAM/storage | Server now; consumer 3-5yr | +| [[id:4a1f23b0-abc6-4def-9876-543210abcdef][5 — Weights]] | Plist-native weights, weight-level provenance | ~100x GPU / ~2-5x ASIC | GPU hybrid now; ASIC 5-10yr | +| [[id:4a1f23b0-abc7-4def-9876-543210abcdef][6 — Training]] | Verified fine-tuning, neural world model | ~100x fine-tuning only | 3-5yr fine-tuning | +| [[id:4a1f23b0-abc8-4def-9876-543210abcdef][7 — Remaining]] | Physical threats, oracles, speculation, bootstrap axiom | Mitigations are non-computational | Forever | + +**Systemic analysis:** +- [[id:b9fa4b7b-bc61-4d7f-918d-ff687b80f2ba][Systemic effects over time]] — how verification cascades across society, economics, and geopolitics diff --git a/ideas/passepartout/passepartout-architecture.org b/ideas/passepartout/passepartout-architecture.org new file mode 100644 index 0000000..c24d69e --- /dev/null +++ b/ideas/passepartout/passepartout-architecture.org @@ -0,0 +1,55 @@ +:PROPERTIES: +:CREATED: [2026-05-24 Sun] +:ID: 1c3ec48b-446c-50d2-b53e-126a81f5143f +:ID: a1fac32a-47de-5fbd-b67d-29152c851747 +:ID: 42c86e6f-4f27-4993-8238-b7bc7d15fb7b +:END: +#+title: Passepartout Architecture +#+filetags: :passepartout:architecture:economics:index: + +Passepartout is a self-bootstrapping replacement for the entire personal computing stack — one project, one image, one verified memory graph. Three subsystems compose into a single system: + +**Verification subsystem** — The gate stack that evaluates every proposed action against formal policy. Capability-based authorization. Combines a probabilistic LLM for natural-language reasoning with a deterministic symbolic engine (gate stack, ACL2 prover, Screamer constraint solver) for all security-critical decisions. The gate verifies shell commands, DIDComm messages, and LLM-generated action proposals through the same decision procedure. + +**Environment subsystem** — The Lisp image where editor, browser, shell, and agent coexist. No separate daemons, no IPC boundaries, no trust transitions between components. One address space from which the verification subsystem checks every state mutation. + +Roadmap: v2.0 Lish editor + Nyxt browser (Qt/WebKit) → v3.0+ Lisp-native layout & browser → v4.0 in-process LLM → v5.0 tagged RISC-V hardware via TinyTapeout/FPGA → v6.0 world models and true agency. + +**Social protocol implementation** — Self-sovereign DID identity, DIDComm encrypted messaging, [[id:1a2b38df-20ba-58ca-ba55-a072be67bd0d][Personal Data Store]], relay network, [[id:3c6b0449-a8fb-5b89-b82a-34efb21ef5b5][compute marketplace]], liquid democracy. + +All three subsystems operate in the same Lisp address space. All three are verified by the same ACL2 prover. The gate stack that verifies a shell command also verifies a DIDComm message. The distinction between "tool" and "self" dissolves. + +--- + +Total addressable market: ~$960B/year across cloud, AI, OS, social media, payments, productivity, and compliance. + +The business model is the AWS of provable computing: AGPL infrastructure is free, revenue comes from verification appliances, gate rules, certification, namespace registry, hosted PDS, and a [[id:3c6b0449-a8fb-5b89-b82a-34efb21ef5b5][compute marketplace]]. Network effects are positive sum — every instance feeds the regression suite and grows the marketplace. + +[[id:1c95ce7d-a2db-506a-9608-df68f9ae211b][Lisp Machine security — unified memory threat model]] +[[id:04c2f221-c54f-51e5-b40a-48822cd16d45][Common Logic (ISO 24707) — relevance to Passepartout]] +[[id:a5d59d12-b23e-58d6-a81b-9b8b06556949][Collective regression suite — how it compounds]] + +Key analytical frames: +- [[id:5961e469-53a3-5f3c-ab72-3c83ef91963f][Investment thesis — the unified view]] +- [[id:9af13fff-9725-542b-93b1-a555bc74ad72][Why Lisp is economically viable now]] +- [[id:efc76898-03f7-57ba-923d-35d65da88bb7][The per-domain sufficiency flip]] +- [[id:dc2e4f22-1c4c-5d4a-a151-f96e5d3b0d70][Development velocity and timeline estimates]] +- [[id:0b5a8a74-cfd6-542d-bc88-4eb3cd8626f9][Cost structure and zero marginal cost]] +- [[id:aa6d062e-a520-5d14-8773-00687ed9c689][Competitive moats analysis]] + +Revenue paths (short to long term): +- [[id:84a537b4-4256-50c8-91f5-dd5b4538418f][Verification appliance]] [[id:c34940cc-090e-57c4-8020-e78b1d32b96c][Domain gate packages]] [[id:45258a2d-1675-562c-9024-5d1eb2f1ea56][Evaluation harness]] +- [[id:2e390c1d-65f3-5fb3-b898-ac3fc4291ee7][Protocol premium usernames]] [[id:1a2b38df-20ba-58ca-ba55-a072be67bd0d][PDS as a service]] [[id:3c6b0449-a8fb-5b89-b82a-34efb21ef5b5][Compute marketplace]] +- [[id:827bc546-e887-5b7c-9b65-6392beaf0920][Verification monopoly — the big money]] [[id:2f783eb4-638e-5afa-9b59-6224d086a712][Infrastructure lock-in]] + +Strategy and IP: +- [[id:caaeee11-ba6f-5566-aecd-f171b4c459c0][Patent strategy]] [[id:67faf52f-9126-50a7-b87e-2bedc610dac7][Licensing (AGPL + commercial)]] +- [[id:5f55bbe6-d243-5766-8ccf-5c5cc88a6542][Impact on the AI/GPU industry]] +- [[id:29e4dbf3-cf19-589c-8b14-389e8a39d564][Upgrade and distribution lifecycle]] +- [[id:45ea493b-94ad-5885-aa65-0c846e5c3c1d][Gate rule encoding from codified domains]] +- [[id:2afd9a3c-e96a-54c7-ac77-a05a28065b4b][Biology as proof of the Lisp model]] +- [[id:00ab3a4d-e3de-5605-a67d-12935bb36ab5][Comparison with Symbolics Genera]] + +The [[id:b25bf753-9799-41ab-82f5-1a1416db756b][protocol overview]] and [[id:a3243dd0-3209-423b-98e1-51c3eada2658][advanced integration]] requirements define how Passepartout's gate stack connects to the social protocol layer. The [[id:72570648-d943-42e5-a781-3b09791ac6ec][realistic assessment]] covers deployment timelines and adoption risks. + +*The lines that run the modern internet (tens of millions across Google, Meta, Amazon, Apple, Microsoft) are replaced by a single coherent architecture where one gate stack verifies everything and one prover proves everything consistent.* diff --git a/ideas/stoa/stoa-stage-0-now.org b/ideas/passepartout/passepartout-stage-0-now.org similarity index 91% rename from ideas/stoa/stoa-stage-0-now.org rename to ideas/passepartout/passepartout-stage-0-now.org index f74f78d..e03f615 100644 --- a/ideas/stoa/stoa-stage-0-now.org +++ b/ideas/passepartout/passepartout-stage-0-now.org @@ -1,11 +1,11 @@ --- title: Stage 0 — Now (Conventional Computing) type: reference -tags: :stoa:roadmap: +tags: :passepartout:roadmap: created: 2026-05-24 --- -← [[id:329a30cd-55fb-496d-a60b-91388c211bba][Stoa Index]] → [[id:4a1f23b0-abc2-4def-9876-543210abcdef][Stage 1 — Agora]] +← [[id:329a30cd-55fb-496d-a60b-91388c211bba][Passepartout]] → [[id:4a1f23b0-abc2-4def-9876-543210abcdef][Stage 1 — Social Protocol]] # Stage 0: Now @@ -76,7 +76,7 @@ is seen as prohibitively expensive. This roadmap is the argument that the provable alternative is not only possible, but the inevitable destination. The question is not whether to build it, but at what pace. -← [[id:329a30cd-55fb-496d-a60b-91388c211bba][Stoa Index]] → [[id:4a1f23b0-abc2-4def-9876-543210abcdef][Stage 1 — Agora]] +← [[id:329a30cd-55fb-496d-a60b-91388c211bba][Passepartout]] → [[id:4a1f23b0-abc2-4def-9876-543210abcdef][Stage 1 — Social Protocol]] :PROPERTIES: :CREATED: [2026-05-24 Sun] diff --git a/ideas/stoa/stoa-stage-1-agora.org b/ideas/passepartout/passepartout-stage-1-social-protocol.org similarity index 76% rename from ideas/stoa/stoa-stage-1-agora.org rename to ideas/passepartout/passepartout-stage-1-social-protocol.org index 82114f3..2d56a24 100644 --- a/ideas/stoa/stoa-stage-1-agora.org +++ b/ideas/passepartout/passepartout-stage-1-social-protocol.org @@ -1,16 +1,16 @@ --- -title: Stage 1 — Agora (In-Transit Integrity) +title: Stage 1 - Social Protocol (In-Transit Integrity) type: reference -tags: :stoa:roadmap:agora: +tags: :passepartout:roadmap:social-protocol: created: 2026-05-24 --- -← [[id:4a1f23b0-abc1-4def-9876-543210abcdef][Stage 0 — Now]] → [[id:4a1f23b0-abc3-4def-9876-543210abcdef][Stage 2 — Logos]] +← [[id:4a1f23b0-abc1-4def-9876-543210abcdef][Stage 0 — Now]] → [[id:4a1f23b0-abc3-4def-9876-543210abcdef][Stage 2 — Verification]] -# Stage 1: [[id:1d074690-a279-59cb-b91d-e9a22ae104ad][Agora]] +# Stage 1: [[id:1d074690-a279-59cb-b91d-e9a22ae104ad][Social Protocol]] *Summary: Every message is signed, DAG-tracked, and content-addressed. -Communication becomes provable — when you choose it to be.* +Communication becomes provable - when you choose it to be.* ## What is added @@ -31,7 +31,7 @@ Communication becomes provable — when you choose it to be.* - **Message tampering in transit** — envelopes are authenticated; tampering changes the CID and breaks the chain - **Impersonation / spoofing** — DID identity keys, not usernames - **Replay attacks** — nonces and sequence numbers per message -- **MITM on Agora-mediated channels** — end-to-end signatures; relays need no trust +- **MITM on social protocol-mediated channels** — end-to-end signatures; relays need no trust - **Loss of message history** — DAG is append-only and content-addressed ## What does this cost? @@ -54,30 +54,30 @@ knowledge that later stages use for falsification. ## When is this viable? -Today. Agora is a protocol design that can be deployed on existing networks. +Today. The social protocol is a protocol design that can be deployed on existing networks. The infrastructure (PDS, Relay, Gateway) runs on conventional [[id:84a537b4-4256-50c8-91f5-dd5b4538418f][hardware]]. ## In practice -Communication becomes provable — but only when the user chooses. Agora's Note +Communication becomes provable - but only when the user chooses. The social protocol's Note primitive supports the full spectrum: persistent DAG-stored messages for audit and compliance, ephemeral Notes that self-destruct, and full Off-the-Record (OTR) mode that bypasses PDS storage entirely. The user chooses per-channel or per-message: permanent and attributable for contracts and governance, ephemeral and deniable for private conversation. The -infrastructure enforces each choice — PDS garbage-collects expired CIDs, Relays -drop them from routing tables, clients shed message keys after display. Agora +infrastructure enforces each choice - PDS garbage-collects expired CIDs, Relays +drop them from routing tables, clients shed message keys after display. The social protocol replaces trust with evidence where evidence is wanted; elsewhere it provides privacy by design. -Agora does not secure the endpoint. The machines running Agora clients can +The social protocol does not secure the endpoint. The machines running social protocol clients can still be compromised at the OS, compiler, or hardware level. The keys are on -those machines — malware that compromises an endpoint can sign messages using -the endpoint's keys. The messages are authentic; the sender wasn't. Agora +those machines - malware that compromises an endpoint can sign messages using +the endpoint's keys. The messages are authentic; the sender wasn't. The social protocol carries the authorization; it doesn't evaluate it. -← [[id:4a1f23b0-abc1-4def-9876-543210abcdef][Stage 0 — Now]] → [[id:4a1f23b0-abc3-4def-9876-543210abcdef][Stage 2 — Logos]] +← [[id:4a1f23b0-abc1-4def-9876-543210abcdef][Stage 0 — Now]] → [[id:4a1f23b0-abc3-4def-9876-543210abcdef][Stage 2 — Verification]] :PROPERTIES: :CREATED: [2026-05-24 Sun] diff --git a/ideas/stoa/stoa-stage-2-logos.org b/ideas/passepartout/passepartout-stage-2-verification.org similarity index 83% rename from ideas/stoa/stoa-stage-2-logos.org rename to ideas/passepartout/passepartout-stage-2-verification.org index 07b54bd..ffac5c7 100644 --- a/ideas/stoa/stoa-stage-2-logos.org +++ b/ideas/passepartout/passepartout-stage-2-verification.org @@ -1,13 +1,13 @@ ---- -title: Stage 2 — Logos (Verified Reasoning Layer) +|--- +title: Stage 2 — Verification Subsystem type: reference -tags: :stoa:roadmap:logos: +tags: :passepartout:roadmap: created: 2026-05-24 --- -← [[id:4a1f23b0-abc2-4def-9876-543210abcdef][Stage 1 — Agora]] → [[id:4a1f23b0-abc4-4def-9876-543210abcdef][Stage 3 — Stoa]] +← [[id:4a1f23b0-abc2-4def-9876-543210abcdef][Stage 1 — Social Protocol]] → [[id:4a1f23b0-abc4-4def-9876-543210abcdef][Stage 3 — Lisp Machine]] -# Stage 2: [[id:1c3ec48b-446c-50d2-b53e-126a81f5143f][Logos]] +# Stage 2: Verification Subsystem *Summary: A verified gate evaluates every action against formal policy. Capability-based authorization. "Root" as an attack target no longer exists.* @@ -30,7 +30,7 @@ Capability-based authorization. "Root" as an attack target no longer exists.* - **Privilege escalation** — no amount of subversion below the gate can grant capabilities the policy doesn't allow. The gate checks capability tokens, not caller identity. -- **"Root" as a meaningful attack target** — there is no root in Logos. There +- **"Root" as a meaningful attack target** — there is no root in Passepartout. There are capabilities, and capabilities are checked. ## What does this cost? @@ -50,7 +50,7 @@ Capability-based authorization. "Root" as an attack target no longer exists.* policy is not. Each policy change needs new proof - **The gate runs on untrusted hardware** — if the OS or hardware is compromised, the gate's guarantees are meaningless. The attacker can skip - the gate or modify its output. Logos's full power arrives at Stage 3 + the gate or modify its output. Full gate guarantees arrive at Stage 3 ## What does this enable? @@ -73,10 +73,10 @@ blocked) against the operational cost (everything must be explicitly authorized in policy). For high-stakes environments, the trade-off is worth it. For casual use, the friction may lead users to bypass the gate. -*Logos's full power arrives when it runs on Stoa. Before that, it's a -correctness proof running on an untrusted substrate.* +*Full gate guarantees arrive when Passepartout runs on its own Lisp machine +(Stage 3). Before that, it's a correctness proof running on an untrusted substrate.* -← [[id:4a1f23b0-abc2-4def-9876-543210abcdef][Stage 1 — Agora]] → [[id:4a1f23b0-abc4-4def-9876-543210abcdef][Stage 3 — Stoa]] +← [[id:4a1f23b0-abc2-4def-9876-543210abcdef][Stage 1 — Social Protocol]] → [[id:4a1f23b0-abc4-4def-9876-543210abcdef][Stage 3 — Lisp Machine]] :PROPERTIES: :CREATED: [2026-05-24 Sun] diff --git a/ideas/stoa/stoa-stage-3-stoa.org b/ideas/passepartout/passepartout-stage-3-lisp-machine.org similarity index 83% rename from ideas/stoa/stoa-stage-3-stoa.org rename to ideas/passepartout/passepartout-stage-3-lisp-machine.org index 587cf55..e0a8c96 100644 --- a/ideas/stoa/stoa-stage-3-stoa.org +++ b/ideas/passepartout/passepartout-stage-3-lisp-machine.org @@ -1,21 +1,20 @@ ---- -title: Stage 3 — Stoa (Verified Infrastructure) +|--- +title: Stage 3 — Lisp Machine type: reference -tags: :stoa:roadmap: +tags: :passepartout:roadmap: created: 2026-05-24 --- -← [[id:4a1f23b0-abc3-4def-9876-543210abcdef][Stage 2 — Logos]] → [[id:4a1f23b0-abc5-4def-9876-543210abcdef][Stage 4 — Inference]] +← [[id:4a1f23b0-abc3-4def-9876-543210abcdef][Stage 2 — Verification]] → [[id:4a1f23b0-abc5-4def-9876-543210abcdef][Stage 4 — Inference]] -# Stage 3: Stoa +# Stage 3: Lisp Machine *Summary: The [[id:84a537b4-4256-50c8-91f5-dd5b4538418f][verified Lisp machine]]. One image, one [[id:1c95ce7d-a2db-506a-9608-df68f9ae211b][memory graph]], one [[id:45ea493b-94ad-5885-aa65-0c846e5c3c1d][gate stack]]. -No kernel, no process boundaries, no memory corruption. [[id:1d074690-a279-59cb-b91d-e9a22ae104ad][Agora]] and Logos are no -longer separate components — they are properties of the same machine.* +No kernel, no process boundaries, no memory corruption. The verification subsystem, the environment subsystem, and the social protocol are no longer separate components — they are properties of the same machine.* ## What is added -Stoa spans three engineering phases that converge on the same architecture: +Passepartout spans three engineering phases that converge on the same architecture: ### Phase A — Software emergence (2-3 years) @@ -81,16 +80,17 @@ and tensor computation. Persistent NVRAM: boot to exactly where you left off. the gate. The evaluator only runs objects in the verified memory graph. - **Supply chain at binary level** — every object has a Merkle chain to its origin. A dependency is a pointer, not a file. -- **The Stoa ↔ Logos ↔ Agora composition problem** — one address space, one - semantics, one proof. The interface between them is an internal relationship. +- **The subsystem composition problem** — one address space, one + semantics, one proof. The interface between verification, environment, and + protocol is an internal relationship. ## What does this cost? - **Lisp tax on everything** — verified execution is 2-10x slower than optimized C on equivalent hardware. Symbolic core is designed to minimize this; tensor unit sidesteps it for neural compute -- **No backward compatibility** — existing software doesn't run on Stoa. No - Linux binaries, no x86 drivers, no GPU compute stacks (without mirror path) +- **No backward compatibility** — existing software doesn't run on the Lisp + machine. No Linux binaries, no x86 drivers, no GPU compute stacks (without mirror path) - **Single address space fragility** — no process isolation. A bug in the editor can corrupt the browser. One crash radius, one machine - **Massive engineering investment** — shortest plausible timeline to a usable @@ -117,8 +117,8 @@ and gate stack are intact. Memory bugs — the dominant attack vector for decades — are structurally eliminated. No more patching for CVEs. No antivirus, no firewall (at the -machine level — network boundaries remain). A Stoa machine that boots -correctly will not crash from a memory corruption bug, ever. +machine level — network boundaries remain). A Passepartout Lisp machine that +boots correctly will not crash from a memory corruption bug, ever. But you've given up the entire existing software world. You cannot run Firefox, Postgres, nginx, Python, or any Linux binary. The machine is a Lisp machine @@ -126,7 +126,7 @@ and everything must be written in Lisp. The practical trade is: absolute memory safety at the cost of adopting an entirely new computing paradigm. This is not an upgrade path — it is a replacement. -← [[id:4a1f23b0-abc3-4def-9876-543210abcdef][Stage 2 — Logos]] → [[id:4a1f23b0-abc5-4def-9876-543210abcdef][Stage 4 — Inference]] +← [[id:4a1f23b0-abc3-4def-9876-543210abcdef][Stage 2 — Verification]] → [[id:4a1f23b0-abc5-4def-9876-543210abcdef][Stage 4 — Inference]] :PROPERTIES: :CREATED: [2026-05-24 Sun] diff --git a/ideas/stoa/stoa-stage-4-inference.org b/ideas/passepartout/passepartout-stage-4-inference.org similarity index 88% rename from ideas/stoa/stoa-stage-4-inference.org rename to ideas/passepartout/passepartout-stage-4-inference.org index 2d44eea..e268069 100644 --- a/ideas/stoa/stoa-stage-4-inference.org +++ b/ideas/passepartout/passepartout-stage-4-inference.org @@ -1,11 +1,11 @@ --- title: Stage 4 — Inference (In-Process LLM) type: reference -tags: :stoa:roadmap: +tags: :passepartout:roadmap: created: 2026-05-24 --- -← [[id:4a1f23b0-abc4-4def-9876-543210abcdef][Stage 3 — Stoa]] → [[id:4a1f23b0-abc6-4def-9876-543210abcdef][Stage 5 — Weights]] +← [[id:4a1f23b0-abc4-4def-9876-543210abcdef][Stage 3 — Lisp Machine]] → [[id:4a1f23b0-abc6-4def-9876-543210abcdef][Stage 5 — Weights]] # Stage 4: Inference @@ -19,7 +19,7 @@ during generation. No external API, no separate trust domain.* - [[id:45ea493b-94ad-5885-aa65-0c846e5c3c1d][Gate-level token interception]]: the Dispatcher inspects every partial token sequence during generation. Trajectories that would produce unauthorized actions are suppressed mid-stream, not filtered after the fact -- Weights loaded from Stoa's Merkle-verified store as a macro-tag blob (one +- Weights loaded from the Lisp machine's Merkle-verified store as a macro-tag blob (one tagged Lisp object pointing to flat binary) - Deterministic inference: same input, same output, same hash — auditable and replayable @@ -55,7 +55,7 @@ gate handles both through different procedures. A 70B param model at 4-bit takes ~35GB. At 10x multiplier, effective conventional-equivalent cost is ~350GB - **Determinism is double-edged** — auditable but cannot adapt or creatively drift -- **No model parallelism** — Stoa runs on one machine. Frontier-scale models +- **No model parallelism** — Passepartout runs on one machine. Frontier-scale models may be too large for a single address space ## What does this enable? @@ -87,7 +87,7 @@ The weights are still a verified *blob* — you know the file's hash but can't prove anything about individual weights. Training provenance is not tracked. The inference is FFI-mediated, so trust in llama.cpp remains. -← [[id:4a1f23b0-abc4-4def-9876-543210abcdef][Stage 3 — Stoa]] → [[id:4a1f23b0-abc6-4def-9876-543210abcdef][Stage 5 — Weights]] +← [[id:4a1f23b0-abc4-4def-9876-543210abcdef][Stage 3 — Lisp Machine]] → [[id:4a1f23b0-abc6-4def-9876-543210abcdef][Stage 5 — Weights]] :PROPERTIES: :CREATED: [2026-05-24 Sun] diff --git a/ideas/stoa/stoa-stage-5-weights.org b/ideas/passepartout/passepartout-stage-5-weights.org similarity index 97% rename from ideas/stoa/stoa-stage-5-weights.org rename to ideas/passepartout/passepartout-stage-5-weights.org index abf569f..27bff45 100644 --- a/ideas/stoa/stoa-stage-5-weights.org +++ b/ideas/passepartout/passepartout-stage-5-weights.org @@ -1,7 +1,7 @@ --- title: Stage 5 — Weights (Plist-Native) type: reference -tags: :stoa:roadmap: +tags: :passepartout:roadmap: created: 2026-05-24 --- @@ -62,7 +62,7 @@ viability. ## When is this viable? -- **GPU hybrid path:** today. Works on any Stoa system with a GPU +- **GPU hybrid path:** today. Works on any Passepartout with a GPU - **ASIC native path:** 5-10 years (tensor unit on the dual-unit chip) ## In practice diff --git a/ideas/stoa/stoa-stage-6-training.org b/ideas/passepartout/passepartout-stage-6-training.org similarity index 95% rename from ideas/stoa/stoa-stage-6-training.org rename to ideas/passepartout/passepartout-stage-6-training.org index b9efb13..903a02a 100644 --- a/ideas/stoa/stoa-stage-6-training.org +++ b/ideas/passepartout/passepartout-stage-6-training.org @@ -1,7 +1,7 @@ --- title: Stage 6 — Training (Verified Fine-Tuning + World Model) type: reference -tags: :stoa:roadmap: +tags: :passepartout:roadmap: created: 2026-05-24 --- @@ -72,10 +72,10 @@ same verified training pipeline: - **Storage per training step** — every Merkle-tracked state transition adds to the memory graph. A fine-tuning run could produce hundreds of terabytes of deltas -- **Only fine-tuning is practical** — full pretraining on Stoa never makes +- **Only fine-tuning is practical** — full pretraining on the Lisp machine never makes sense. The 100x overhead is structural. Practical workflow: pretrain on conventional GPU cluster → import as verified blob → convert to plist-native - under gate → fine-tune in Stoa + under gate → fine-tune on the Lisp machine - **Data gate latency** — every training example passes through the authorization gate. For datasets with millions of examples, this pre- processing step can take days @@ -105,7 +105,7 @@ But this system is not for training frontier models — it is for auditing training runs that happen elsewhere. The practical workflow is: pretrain on a conventional GPU cluster, import the -weights into Stoa as a verified blob (Stage 4), then fine-tune within Stoa +weights into the Lisp machine as a verified blob (Stage 4), then fine-tune on the Lisp machine under the verified training loop. The pretraining phase remains unverified, but the fine-tuning phase — where the model gains knowledge of private data and user preferences — is verified. This is the pragmatic sweet spot. diff --git a/ideas/stoa/stoa-stage-7-remaining.org b/ideas/passepartout/passepartout-stage-7-remaining.org similarity index 94% rename from ideas/stoa/stoa-stage-7-remaining.org rename to ideas/passepartout/passepartout-stage-7-remaining.org index 0c01f6a..3bf3002 100644 --- a/ideas/stoa/stoa-stage-7-remaining.org +++ b/ideas/passepartout/passepartout-stage-7-remaining.org @@ -1,7 +1,7 @@ --- title: Stage 7 — What Remains type: reference -tags: :stoa:roadmap: +tags: :passepartout:roadmap: created: 2026-05-24 --- @@ -23,7 +23,7 @@ None can be eliminated by computation alone.* | Power/EM side channels | Constant-power design, shielding | Power overhead | Physical hardening is expensive in direct proportion to the threat level. -If someone steals your Stoa machine, they have your data. Hardware hashing +If someone steals your Lisp machine, they have your data. Hardware hashing and encryption slow them down, but the security boundary is now physical. ## 2. Side channels in the verified model @@ -104,7 +104,7 @@ contacted at 3am are likely to be annoyed. These are distinct from the accumulated knowledge in the [[id:1c95ce7d-a2db-506a-9608-df68f9ae211b][Merkle DAG]], which records specific observations. Common sense is the *generalization engine*. -**Three channels in the Stoa architecture:** +**Three channels in the Passepartout architecture:** | Channel | Origin | Verification | Granularity | |---------|--------|-------------|-------------| @@ -134,13 +134,13 @@ store for beliefs that survive falsification. | Threat | Eliminated at stage | |--------|---------------------| -| Memory corruption | 3 — Stoa | -| OS exploitation | 3 — Stoa | -| Malware / viruses / worms | 3 — Stoa | -| Compiler backdoors | 3 — Stoa | -| Message forgery / tampering | 1 — [[id:1d074690-a279-59cb-b91d-e9a22ae104ad][Agora]] | -| MITM on communication | 1 — Agora | -| Unauthorized actions | 2 — Logos (fully at 3) | +| Memory corruption | 3 — Lisp Machine | +| OS exploitation | 3 — Lisp Machine | +| Malware / viruses / worms | 3 — Lisp Machine | +| Compiler backdoors | 3 — Lisp Machine | +| Message forgery / tampering | 1 — [[id:1d074690-a279-59cb-b91d-e9a22ae104ad][Social Protocol]] | +| MITM on communication | 1 — Social Protocol | +| Unauthorized actions | 2 — Gate stack (fully at 3) | | Prompt injection bypassing gate | 4 — In-process inference | | Weight tampering (blob level) | 4 — Verified blob hash | | Weight tampering (fine-grained) | 5 — Plist-native weights | diff --git a/ideas/triad-systemic-effects.org b/ideas/passepartout/passepartout-systemic-effects.org similarity index 63% rename from ideas/triad-systemic-effects.org rename to ideas/passepartout/passepartout-systemic-effects.org index 06e612a..f21a6fe 100644 --- a/ideas/triad-systemic-effects.org +++ b/ideas/passepartout/passepartout-systemic-effects.org @@ -1,12 +1,11 @@ :PROPERTIES: :ID: b9fa4b7b-bc61-4d7f-918d-ff687b80f2ba -:ID: triad-systemic-effects :CREATED: [2026-05-23 Sat] :END: -#+title: Triad — Systemic Effects Over Time +#+title: Passepartout — Systemic Effects Over Time #+filetags: :passepartout:strategy:effects:geopolitics:society: -The triad (Logos + [[id:c3b3dc41-945f-54e9-84eb-ca014114f1be][Stoa]] + [[id:1d074690-a279-59cb-b91d-e9a22ae104ad][Agora]]) is not a product in an existing category. Verified infrastructure is a new category, and every existing category — cloud, AI, OS, social, payments, compliance, governance — eventually migrates into it because the alternative becomes indefensible. +Passepartout is not a product in an existing category. Verified infrastructure is a new category, and every existing category — cloud, AI, OS, social, payments, compliance, governance — eventually migrates into it because the alternative becomes indefensible. Using the [[id:2cdca4b0-6b41-44b4-acb0-af21d0e27b00][orders-of-magnitude framework]], the effects cascade across time scales. Each scale is qualitatively different, not just more of the same. @@ -14,7 +13,7 @@ Using the [[id:2cdca4b0-6b41-44b4-acb0-af21d0e27b00][orders-of-magnitude framewo ** Scientific: verification becomes the publishing standard -[[id:28c46769-c14b-42aa-ac7a-69d310157f8f][Passepartout]] gate rules turn every computational result into a machine-checkable proof. Papers carry proof logs, not just dataset citations. The replication crisis in compute-heavy fields (ML, climate science, genomics) meets its match — if the code doesn't verify, the result doesn't publish. +Passepartout's gate rules turn every computational result into a machine-checkable proof. Papers carry proof logs, not just dataset citations. The replication crisis in compute-heavy fields (ML, climate science, genomics) meets its match — if the code doesn't verify, the result doesn't publish. The effect compounds: proof repositories accumulate lemma libraries across fields, so each paper stands on verified shoulders, not on trust. @@ -26,7 +25,7 @@ The first enterprise that replaces a [[id:ed65031c-cbd2-4ad2-bd53-a67791e183cd][ ** Political: regulation becomes executable -The first regulation encoded as a gate rule sets a precedent. Regulators realize they can specify compliance in /executable form/ rather than prose. This changes the regulator-regulated relationship from adversarial interpretation to formal specification. +The first regulation encoded as a gate rule sets a precedent. Regulators realize they can specify compliance in executable form rather than prose. This changes the regulator-regulated relationship from adversarial interpretation to formal specification. A regulation that says "access logs must be tamper-proof" is a negotiation. A gate rule that enforces Merkle-chain logging is a fact. Compliance shifts from "did you follow the intent" to "does the proof pass." @@ -34,13 +33,13 @@ A regulation that says "access logs must be tamper-proof" is a negotiation. A ga ** Technological: AI safety becomes engineering, not policy -The verified API gateway ([[id:ed05cab4-88e9-4e25-b7c9-346fa39c69a0][revenue hub]]) proves that AI safety is a /software engineering problem/, not a policy problem. Companies don't need AI regulation — they need Passepartout gate rules between the LLM and production. +The verified API gateway ([[id:ed05cab4-88e9-4e25-b7c9-346fa39c69a0][revenue hub]]) proves that AI safety is a software engineering problem, not a policy problem. Companies don't need AI regulation — they need Passepartout gate rules between the LLM and production. This shifts the entire AI safety discourse. The question stops being "what should we ban?" and becomes "what gates should we verify?" Prompt injection, jailbreaks, data leakage, hallucination in critical paths — all become gate rule specifications, not white papers. ** Social: institutional trust gives way to computational trust -/I verified it/ replaces /I trust the auditor/. DIDs make platform-owned identity look like a historical anomaly. The [[id:1a2b38df-20ba-58ca-ba55-a072be67bd0d][PDS model]] makes surveillance advertising technically impossible without the user's active consent gate. +"I verified it" replaces "I trust the auditor." DIDs make platform-owned identity look like a historical anomaly. The [[id:1a2b38df-20ba-58ca-ba55-a072be67bd0d][PDS model]] makes surveillance advertising technically impossible without the user's active consent gate. The social contract around data shifts: companies don't own user data because the architecture literally prevents them from accessing it without a permission gate. The [[id:513d5996-4ac7-4567-a992-18fc01599104][GDPR]] model (notice + consent) was a regulation trying to fix bad architecture. The PDS model is architecture that makes bad behaviour impossible. @@ -48,23 +47,23 @@ The social contract around data shifts: companies don't own user data because th The Lisp renaissance is not retro — it is the first time a language of proof carries cultural cachet outside academia. A new generation of developers grows up with verification as a default, not an afterthought. -The /move fast and break things/ ethos ages overnight. In the C-suite, saying /we don't verify our deployments/ becomes as embarrassing as saying /we don't test our code/ was in the 2000s. The cultural shift precedes and enables the economic shift. +The "move fast and break things" ethos ages overnight. In the C-suite, saying "we don't verify our deployments" becomes as embarrassing as saying "we don't test our code" was in the 2000s. The cultural shift precedes and enables the economic shift. * Years — End State consolidates ** Economic: [[id:827bc546-e887-5b7c-9b65-6392beaf0920][the verification monopoly]] -If every transaction on Agora, every plugin on Stoa, every gate rule on Logos passes through Passepartout's verification, then the early player collects a tax on the entire verified economy. This is the [[id:827bc546-e887-5b7c-9b65-6392beaf0920][verification monopoly]]. +If every transaction on the social protocol, every plugin in the environment, every gate rule passes through Passepartout's verification, then the early player collects a tax on the entire verified economy. This is the [[id:827bc546-e887-5b7c-9b65-6392beaf0920][verification monopoly]]. -The $960B TAM ([[id:1c3ec48b-446c-50d2-b53e-126a81f5143f][triad index]]) is not aspirational — it is the cost of admission to the verified stack. Every dollar spent on cloud, AI, OS, social media, payments, and compliance eventually flows through the verification layer. The early player does not capture 100% of that, but the spread on even 5-10% is venture-scale money. +The $960B TAM ([[id:1c3ec48b-446c-50d2-b53e-126a81f5143f][architecture index]]) is not aspirational — it is the cost of admission to the verified stack. Every dollar spent on cloud, AI, OS, social media, payments, and compliance eventually flows through the verification layer. The early player does not capture 100% of that, but the spread on even 5-10% is venture-scale money. -The switching cost to unverified infrastructure becomes infinite. No enterprise can justify / why would we go back to unverified code / once verification is in place. This is the [[id:2f783eb4-638e-5afa-9b59-6224d086a712][infrastructure lock-in]]. +The switching cost to unverified infrastructure becomes infinite. No enterprise can justify "why would we go back to unverified code" once verification is in place. This is the [[id:2f783eb4-638e-5afa-9b59-6224d086a712][infrastructure lock-in]]. ** Geopolitical: compute becomes a strategic asset The [[id:3c6b0449-a8fb-5b89-b82a-34efb21ef5b5][compute marketplace]] becomes a geopolitical asset on the order of SWIFT or the dollar. Whoever provisions the largest verified compute capacity becomes the default infrastructure provider for any nation that wants verified digital sovereignty. -The triad is inherently anti-surveillance-capitalist architecture. The PDS model does not do bulk surveillance. This makes it threatening to both: +Passepartout is inherently anti-surveillance-capitalist architecture. The PDS model does not do bulk surveillance. This makes it threatening to both: - /Authoritarian states/ — they lose dragnet access to citizen data - /Surveillance capitalists/ — they lose the data moat their business model depends on @@ -73,9 +72,9 @@ The nations that adopt verified infrastructure are in one economic sphere. The n ** Political: liquid democracy infrastructure at scale -Verifiable proxy voting, delegation chains, quadratic funding for [[id:64708e1f-00e9-4cb7-b44b-ea0b98e5296d][public goods (Agora contracts)]] — these are not experiments. They become infrastructure that nation-states adopt because the alternative (unverifiable voting, opaque governance) becomes indefensible. +Verifiable proxy voting, delegation chains, quadratic funding for [[id:64708e1f-00e9-4cb7-b44b-ea0b98e5296d][public goods (Social protocol contracts)]] — these are not experiments. They become infrastructure that nation-states adopt because the alternative (unverifiable voting, opaque governance) becomes indefensible. -The effect is not that democracy becomes digital. The effect is that /trust in institutions/ becomes a measurable property rather than a polling number. Did the government follow its own rules? The proof log says yes or no. This is the political equivalent of the scientific reproducibility shift: institutions that can produce proof logs are trusted; institutions that cannot are not. +The effect is not that democracy becomes digital. The effect is that trust in institutions becomes a measurable property rather than a polling number. Did the government follow its own rules? The proof log says yes or no. This is the political equivalent of the scientific reproducibility shift: institutions that can produce proof logs are trusted; institutions that cannot are not. * Generations — End State mature @@ -83,11 +82,11 @@ The effect is not that democracy becomes digital. The effect is that /trust in i The verification network defines the digital order in the same way the internet defined the 1990s. Nations on verified infrastructure are in one economic sphere; nations that are not are in another. -Lisp Machine hardware becomes a strategic export control — like advanced semiconductors today. The triad is not a product category; it is infrastructure sovereignty. +Lisp Machine hardware becomes a strategic export control — like advanced semiconductors today. Passepartout is not a product category; it is infrastructure sovereignty. ** Cultural: the break-everything era becomes a historical curiosity -The /move fast and break things/ era is remembered like bloodletting or lead paint. A developer who does not verify is like a civil engineer who does not do structural calculations. The entire profession shifts from /write code/ to /write verified code/ as the default. +The "move fast and break things" era is remembered like bloodletting or lead paint. A developer who does not verify is like a civil engineer who does not do structural calculations. The entire profession shifts from "write code" to "write verified code" as the default. The cultural residue of the unverified era (daily security patches, ransomware as an industry, "works on my machine") becomes a teaching example of how things used to be done. @@ -95,7 +94,7 @@ The cultural residue of the unverified era (daily security patches, ransomware a ACL2 proof libraries are the arxiv of verified knowledge. The accumulation of proof strategies across millions of domains — every edge case ever encountered, every lemma ever proven — becomes a shared inheritance that no single human could assemble. The system bootstraps itself into regions of proof space that no unassisted human could reach. -The frontier shifts. The question is no longer /can we verify this/ but /what new things become possible when verification is free/. The corollary: what new kinds of error become possible when the proof is wrong? The proof is machine-checkable; the /specification/ is human. Specification errors become the dominant failure mode — and that is a more tractable problem than runtime bugs, because specifications can be verified against /other/ specifications. +The frontier shifts. The question is no longer "can we verify this" but "what new things become possible when verification is free." The corollary: what new kinds of error become possible when the proof is wrong? The proof is machine-checkable; the specification is human. Specification errors become the dominant failure mode — and that is a more tractable problem than runtime bugs, because specifications can be verified against other specifications. ** Economic: the old economy becomes a historical layer @@ -105,10 +104,10 @@ The insurance industry, which prices based on risk, shifts to pricing based on p * References -- [[id:1c3ec48b-446c-50d2-b53e-126a81f5143f][Triad index]] — the full architecture -- [[id:a1fac32a-47de-5fbd-b67d-29152c851747][Triad overview]] — Logos, Stoa, Agora +- [[id:1c3ec48b-446c-50d2-b53e-126a81f5143f][Architecture index]] — the full Passepartout architecture +- [[id:a1fac32a-47de-5fbd-b67d-29152c851747][Architecture overview]] — the three subsystems - [[id:ed05cab4-88e9-4e25-b7c9-346fa39c69a0][Revenue streams overview]] — economic effects quantified -- [[id:64708e1f-00e9-4cb7-b44b-ea0b98e5296d][Agora contracts]] — governance, insurance, liquid democracy +- [[id:64708e1f-00e9-4cb7-b44b-ea0b98e5296d][Social protocol contracts]] — governance, insurance, liquid democracy - [[id:827bc546-e887-5b7c-9b65-6392beaf0920][Verification monopoly]] — the big money - [[id:2f783eb4-638e-5afa-9b59-6224d086a712][Infrastructure lock-in]] — switching costs - [[id:2cdca4b0-6b41-44b4-acb0-af21d0e27b00][Orders of magnitude — time]] — the framework that structures this analysis diff --git a/ideas/pds-as-a-service.org b/ideas/pds-as-a-service.org index 5ddb384..d6d286b 100644 --- a/ideas/pds-as-a-service.org +++ b/ideas/pds-as-a-service.org @@ -3,9 +3,9 @@ :ID: 1a2b38df-20ba-58ca-ba55-a072be67bd0d :END: #+title: Personal Data Store as a Service -#+filetags: :passepartout:agora:revenue:pds:saas: +#+filetags: :passepartout:social-protocol:revenue:pds:saas: -Classic open-core SaaS model (GitLab, Sentry, PlanetScale). The Merkle fact store exposed on [[id:1d074690-a279-59cb-b91d-e9a22ae104ad][Agora]] can be self-hosted (free, AGPL) or hosted by the early player. +Classic open-core SaaS model (GitLab, Sentry, PlanetScale). The Merkle fact store exposed on [[id:1d074690-a279-59cb-b91d-e9a22ae104ad][the social protocol]] can be self-hosted (free, AGPL) or hosted by the early player. - **Free tier (self-hosted):** full AGPL PDS, runs on any Lisp host, full control, no cost - **Basic hosted tier:** $10-$20/month, 10GB fact store, 10M queries/month, automated backup, automatic upgrades @@ -16,4 +16,4 @@ The free self-hosted version drives adoption and trust (you can inspect every li Target: 100K subscribers at $15/month average = $18M/yr recurring, near-zero marginal cost per additional subscriber (the symbolic engine is CPU-bound, not per-user metered). -Combined with [[id:2e390c1d-65f3-5fb3-b898-ac3fc4291ee7][premium usernames]]: $28M/yr from Agora services alone before [[id:3c6b0449-a8fb-5b89-b82a-34efb21ef5b5][compute marketplace]] revenue. The hosted model also creates [[id:2f783eb4-638e-5afa-9b59-6224d086a712][infrastructure lock-in]] as users build their Merkle fact stores on the platform, making migration costly. The AGPL [[id:67faf52f-9126-50a7-b87e-2bedc610dac7][licensing]] model is described in [[id:67faf52f-9126-50a7-b87e-2bedc610dac7][Licensing]]. +Combined with [[id:2e390c1d-65f3-5fb3-b898-ac3fc4291ee7][premium usernames]]: $28M/yr from social protocol services alone before [[id:3c6b0449-a8fb-5b89-b82a-34efb21ef5b5][compute marketplace]] revenue. The hosted model also creates [[id:2f783eb4-638e-5afa-9b59-6224d086a712][infrastructure lock-in]] as users build their Merkle fact stores on the platform, making migration costly. The AGPL [[id:67faf52f-9126-50a7-b87e-2bedc610dac7][licensing]] model is described in [[id:67faf52f-9126-50a7-b87e-2bedc610dac7][Licensing]]. diff --git a/ideas/revenue-hub.org b/ideas/revenue-hub.org index 308179c..bb28f34 100644 --- a/ideas/revenue-hub.org +++ b/ideas/revenue-hub.org @@ -6,11 +6,11 @@ #+title: Revenue Streams — Overview #+filetags: :passepartout:revenue:index:business-model: -This page is the entry point for revenue generation thinking across all three triad components. Revenue splits cleanly across the two development phases defined in [[id:dc2e4f22-1c4c-5d4a-a151-f96e5d3b0d70][time estimates]]. Each component enables different revenue primitives. +This page is the entry point for revenue generation thinking across all three Passepartout subsystems. Revenue splits cleanly across the two development phases defined in [[id:dc2e4f22-1c4c-5d4a-a151-f96e5d3b0d70][time estimates]]. Each component enables different revenue primitives. -* Revenue by Triad Component +* Revenue by Subsystem -** Logos (the mind) — Revenue streams +** Verification subsystem — Revenue streams Existing coverage — [[id:84a537b4-4256-50c8-91f5-dd5b4538418f][Verification appliance]], [[id:c34940cc-090e-57c4-8020-e78b1d32b96c][Domain gate packages]], [[id:45258a2d-1675-562c-9024-5d1eb2f1ea56][Evaluation harness]], [[id:3c6b0449-a8fb-5b89-b82a-34efb21ef5b5][Compute marketplace]], [[id:d84679f1-c0c5-5be4-b19c-6573560640ee][Verified skill marketplace]]: @@ -19,10 +19,10 @@ Existing coverage — [[id:84a537b4-4256-50c8-91f5-dd5b4538418f][Verification ap | Verification appliance | Zero | FPGA/Tenstorrent pre-loaded with [[id:28c46769-c14b-42aa-ac7a-69d310157f8f][Passepartout]] + gate rules | | Domain gate packages | Zero | SaaS subscriptions per compliance domain | | Evaluation harness | Zero | Certification-as-a-service, regression suite access | -| Compute marketplace | Both | Verified symbolic engine cycles via [[id:1d074690-a279-59cb-b91d-e9a22ae104ad][Agora]] | +| Compute marketplace | Both | Verified symbolic engine cycles via [[id:1d074690-a279-59cb-b91d-e9a22ae104ad][Social Protocol]] | | Verified skill marketplace | End State | Commission on third-party gate rules | -*** Unexplored Logos streams +*** Unexplored verification subsystem streams | Stream | Phase | Rationale | |--------+-------+-----------| @@ -36,9 +36,9 @@ Existing coverage — [[id:84a537b4-4256-50c8-91f5-dd5b4538418f][Verification ap | Training & certification | Zero | Certified Gate Rule Developer program. Developer camps, certification exams, continuing education. The Red Hat / AWS training model. | | Enterprise support SLA | Zero | Guaranteed verification pipeline uptime, priority bug fixes, custom gate rule development. Red Hat subscription model. | -/Verified API gateway/ is notable because it requires zero buy-in to the triad vision. Any company using LLM APIs today can deploy Passepartout as a verification proxy and immediately get value (audit trail, gate compliance, prompt injection detection). It's a standalone product that seeds the ecosystem. +/Verified API gateway/ is notable because it requires zero buy-in to the full Passepartout vision. Any company using LLM APIs today can deploy Passepartout as a verification proxy and immediately get value (audit trail, gate compliance, prompt injection detection). It's a standalone product that seeds the ecosystem. -** Stoa (the body) — Revenue streams +** Environment subsystem — Revenue streams This is the /least developed/ revenue arm. Existing docs essentially say people buy hardware and the lock-in compounds. There is a gap: @@ -47,18 +47,18 @@ Existing coverage: essentially none beyond hardware sales. | Stream | Phase | Rationale | |--------+-------+-----------| | Lisp Machine hardware | End State | Tenstorrent/FPGA appliances. Hardware margins + recurring gate rules. | -| [[id:c3b3dc41-945f-54e9-84eb-ca014114f1be][Stoa]] premium | Both | Enterprise features: SSO, audit logging, compliance reports, team management, centralized policy enforcement. Annual seat license. | -| Plugin and theme marketplace | End State | Verified plugins for Stoa (editors, browsers, shells, tools). Commission on each sale. Developer ecosystem. App Store for the Lisp Machine. | -| Commercial Lisp image distribution | Both | Verified, signed, compatibility-guaranteed Stoa images. Free self-build (AGPL), paid for certified builds with SLAs. | -| Enterprise Stoa deployment | Zero | Tools for deploying Stoa across an organization: fleet management, unified gate policy, compliance dashboard. Annual license. | -| Backup and archive service | Both | Verified snapshots of Stoa Lisp images. Tamper-proof archival of development environments. | -| Stoa extension SDK | Both | Commercial license for developing proprietary Stoa extensions. Tools, documentation, support. | +| [[id:c3b3dc41-945f-54e9-84eb-ca014114f1be][Environment subsystem]] premium | Both | Enterprise features: SSO, audit logging, compliance reports, team management, centralized policy enforcement. Annual seat license. | +| Plugin and theme marketplace | End State | Verified plugins for the environment subsystem (editors, browsers, shells, tools). Commission on each sale. Developer ecosystem. App Store for the Lisp Machine. | +| Commercial Lisp image distribution | Both | Verified, signed, compatibility-guaranteed environment subsystem images. Free self-build (AGPL), paid for certified builds with SLAs. | +| Enterprise environment subsystem deployment | Zero | Tools for deploying the environment subsystem across an organization: fleet management, unified gate policy, compliance dashboard. Annual license. | +| Backup and archive service | Both | Verified snapshots of environment subsystem Lisp images. Tamper-proof archival of development environments. | +| Environment subsystem extension SDK | Both | Commercial license for developing proprietary environment subsystem extensions. Tools, documentation, support. | -Key insight: Stoa does not need the full Lisp Machine to generate revenue. Stoa premium (SSO, audit, compliance reports) and enterprise deployment tools ship on Linux, use the existing Stoa terminal UI, and sell to the same enterprise buyer who buys gate packages. Compliance teams want verified environments — Stoa premium delivers that without waiting for custom hardware. +Key insight: The environment subsystem does not need the full Lisp Machine to generate revenue. Environment subsystem premium (SSO, audit, compliance reports) and enterprise deployment tools ship on Linux, use the existing environment subsystem terminal UI, and sell to the same enterprise buyer who buys gate packages. Compliance teams want verified environments — the environment subsystem premium delivers that without waiting for custom hardware. -** Agora (the society) — Revenue streams +** Social Protocol (the society) — Revenue streams -Existing coverage — [[id:2e390c1d-65f3-5fb3-b898-ac3fc4291ee7][Agora usernames]], [[id:1a2b38df-20ba-58ca-ba55-a072be67bd0d][PDS as a service]], [[id:3c6b0449-a8fb-5b89-b82a-34efb21ef5b5][Compute marketplace]]: +Existing coverage — [[id:2e390c1d-65f3-5fb3-b898-ac3fc4291ee7][Social protocol usernames]], [[id:1a2b38df-20ba-58ca-ba55-a072be67bd0d][PDS as a service]], [[id:3c6b0449-a8fb-5b89-b82a-34efb21ef5b5][Compute marketplace]]: | Stream | Phase | Description | |--------+-------+-------------| @@ -68,13 +68,13 @@ Existing coverage — [[id:2e390c1d-65f3-5fb3-b898-ac3fc4291ee7][Agora usernames The most fertile ground is contracts. DIDs provide identity, DIDComm provides communication, PDS provides state, gate rules encode terms, ACL2 verifies execution, and the symbolic engine runs deterministically. This is a full smart contract platform, strictly stronger than existing ones because ACL2 verifies the /rules themselves/, not just execution trace validity. -*** Unexplored Agora streams — contracts +*** Unexplored social protocol streams — contracts | Stream | Phase | Rationale | |--------+-------+-----------| -| Verified smart contract platform | End State | Deploy contracts on Agora with ACL2-verified correctness. Every contract call produces a machine-checkable proof. Revenue: transaction fees per execution + deployment fee per verified contract. | +| Verified smart contract platform | End State | Deploy contracts on the social protocol with ACL2-verified correctness. Every contract call produces a machine-checkable proof. Revenue: transaction fees per execution + deployment fee per verified contract. | | Contract template marketplace | Zero | Pre-verified contract templates for common use cases (escrow, DAO constitution, SLA, data licensing). Sell templates or take commission on template-based contracts. | -| Dispute resolution service | End State | When two Agora instances disagree on contract execution, submit to a verified arbitrator. Fee per resolution. | +| Dispute resolution service | End State | When two social protocol instances disagree on contract execution, submit to a verified arbitrator. Fee per resolution. | | Attestation marketplace | Zero | DIDs + verified actions = verifiable reputation. Attest that a DID meets certain criteria. Revenue: attestation fees, verification fees. | | Multi-instance governance | Zero | Cross-instance policy enforcement, unified compliance reporting, federated identity. Enterprise tier, annual license. | | Liquid democracy infrastructure | End State | DAO governance as a service. Verified proxy voting, governance contracts. Per-vote transaction fee. | @@ -82,9 +82,9 @@ The most fertile ground is contracts. DIDs provide identity, DIDComm provides co | Namespace sub-leasing | Both | Premium handles sub-leased between DIDs. Commission on each lease. | | Data sharing contracts | Both | PDS-to-PDS data sharing agreements encoded as gate rules. Commission on each data transaction. | -The contract platform is the kill application for Agora. Ethereum proved demand for verifiable contracts at $20B+/yr in transaction fees. Agora's version is strictly better: ACL2 proves contract /correctness/ (not just valid execution), gate rules encode real-world regulations directly, and the PDS provides persistent state without a global trie bottleneck. +The contract platform is the kill application for the social protocol. Ethereum proved demand for verifiable contracts at $20B+/yr in transaction fees. The social protocol's version is strictly better: ACL2 proves contract /correctness/ (not just valid execution), gate rules encode real-world regulations directly, and the PDS provides persistent state without a global trie bottleneck. -See [[id:64708e1f-00e9-4cb7-b44b-ea0b98e5296d][Agora contracts]] for the full analysis. +See [[id:64708e1f-00e9-4cb7-b44b-ea0b98e5296d][Social protocol contracts]] for the full analysis. * Revenue by Development Phase @@ -92,25 +92,25 @@ See [[id:64708e1f-00e9-4cb7-b44b-ea0b98e5296d][Agora contracts]] for the full an | Stream | Component | TAM | Buyer | Revenue type | |--------+----------+-----+-------+--------------| -| Domain gate packages | Logos | Large | CISO/Compliance | SaaS | -| Verification appliance | Logos | Medium | Enterprise infra | Hardware + subs | -| Evaluation harness | Logos | Medium | Compliance | Certification | -| Agora premium usernames | Agora | Small | Individual | Subscription | -| PDS hosting (basic) | Agora | Medium | Individual | Hosting | -| Verified API gateway | Logos | Large | Eng teams | Per-call | -| Continuous compliance monitoring | Logos | Large | Compliance | Annual contract | -| Migration pipeline | Logos | Medium | Enterprise | Per-engagement | -| Enterprise support SLA | Logos/Stoa | Medium | Enterprise | Annual | -| Gate rule SDK (commercial) | Logos | Small | Developers | License | -| Stoa premium (enterprise) | Stoa | Medium | Enterprise | Annual seat | -| Enterprise Stoa deployment | Stoa | Medium | Enterprise Ops | Annual | +| Domain gate packages | Verification | Large | CISO/Compliance | SaaS | +| Verification appliance | Verification | Medium | Enterprise infra | Hardware + subs | +| Evaluation harness | Verification | Medium | Compliance | Certification | +| Social protocol premium usernames | Social Protocol | Small | Individual | Subscription | +| PDS hosting (basic) | Social Protocol | Medium | Individual | Hosting | +| Verified API gateway | Verification | Large | Eng teams | Per-call | +| Continuous compliance monitoring | Verification | Large | Compliance | Annual contract | +| Migration pipeline | Verification | Medium | Enterprise | Per-engagement | +| Enterprise support SLA | Verification/Environment | Medium | Enterprise | Annual | +| Gate rule SDK (commercial) | Verification | Small | Developers | License | +| Environment subsystem premium (enterprise) | Environment subsystem | Medium | Enterprise | Annual seat | +| Enterprise environment subsystem deployment | Environment subsystem | Medium | Enterprise Ops | Annual | | Training and certification | All | Small | Developers | Per-seat | -| Forensics / incident response | Logos | Small | Enterprise | Per-incident | -| Contract templates | Agora | Medium | Developers | Per-template | -| Attestation marketplace | Agora | Medium | Enterprise | Per-attestation | -| Data sharing contracts | Agora | Medium | Enterprise | Per-transaction | -| Multi-instance governance | Agora | Large | Enterprise | Annual | -| Namespace sub-leasing | Agora | Small | Individuals | Per-transaction | +| Forensics / incident response | Verification | Small | Enterprise | Per-incident | +| Contract templates | Social Protocol | Medium | Developers | Per-template | +| Attestation marketplace | Social Protocol | Medium | Enterprise | Per-attestation | +| Data sharing contracts | Social Protocol | Medium | Enterprise | Per-transaction | +| Multi-instance governance | Social Protocol | Large | Enterprise | Annual | +| Namespace sub-leasing | Social Protocol | Small | Individuals | Per-transaction | Phase Zero target: $2M-$12M/year (from [[id:5961e469-53a3-5f3c-ab72-3c83ef91963f][investment thesis]]), with upside from verified API gateway and compliance monitoring pushing toward $15-20M. @@ -118,18 +118,17 @@ Phase Zero target: $2M-$12M/year (from [[id:5961e469-53a3-5f3c-ab72-3c83ef91963f | Stream | Component | TAM | Revenue type | |--------+----------+-----+--------------| -| [[id:827bc546-e887-5b7c-9b65-6392beaf0920][Verification monopoly]] | Logos/All | $1B+ | Certification | +| [[id:827bc546-e887-5b7c-9b65-6392beaf0920][Verification monopoly]] | Verification/All | $1B+ | Certification | | Infrastructure lock-in | All | $100B+ | Rent extraction | -| Compute marketplace | Agora | Venture-scale | Transaction fees | -| Lisp Machine hardware | Stoa | Large | Hardware + subs | -| Smart contract platform | Agora | Very large ($20B+) | Transaction fees | -| Liquid democracy infra | Agora | Large | Per-vote | -| Insurance marketplace | Agora | Very large | Premiums + fees | -| Dispute resolution | Agora | Medium | Per-resolution | -| Plugin/theme marketplace | Stoa | Large | Commission | -| Commercial image distribution | Stoa | Medium | Subscription | -| Proof repository marketplace | Logos | Medium | Subscription | -| Verified skill marketplace | Logos | Medium | Commission | +| Compute marketplace | Social Protocol | Venture-scale | Transaction fees | +| Smart contract platform | Social Protocol | Very large ($20B+) | Transaction fees | +| Liquid democracy infra | Social Protocol | Large | Per-vote | +| Insurance marketplace | Social Protocol | Very large | Premiums + fees | +| Dispute resolution | Social Protocol | Medium | Per-resolution | +| Plugin/theme marketplace | Environment subsystem | Large | Commission | +| Commercial image distribution | Environment subsystem | Medium | Subscription | +| Proof repository marketplace | Verification | Medium | Subscription | +| Verified skill marketplace | Verification | Medium | Commission | * Orders-of-Magnitude Risk Map @@ -138,11 +137,11 @@ Using the [[id:2cdca4b0-6b41-44b4-acb0-af21d0e27b00][orders-of-magnitude framewo | Scale | Representative streams | Failure mode | |-------+-----------------------+--------------| | Weeks | Gate packages, appliance pre-orders, training | Wrong pricing, too early | -| Months | Compliance monitoring, API gateway, PDS, Stoa premium | Churn, incumbents respond | +| Months | Compliance monitoring, API gateway, PDS, environment subsystem premium | Churn, incumbents respond | | Years | Compute marketplace, contract platform, monopoly | Competition catches up | | Generations | Infrastructure lock-in, insurance marketplace | Technology shift | -The phase-zero streams are all direct enterprise sales with short cycles and clear buyers. The end-state streams require installed base — you cannot have a verification monopoly without deployed triads. +The phase-zero streams are all direct enterprise sales with short cycles and clear buyers. The end-state streams require installed base — you cannot have a verification monopoly without deployed Passepartout instances. * Risk-Ordered Investment Priority @@ -150,8 +149,8 @@ The phase-zero streams are all direct enterprise sales with short cycles and cle 2. Verified API gateway — Standalone product, anyone using LLMs is a customer. Zero triad buy-in required. 3. Verification appliance — Customers pay for hardware + ongoing subs. Verifiable revenue, long contracts. 4. Continuous compliance monitoring — Annual contracts, compliance teams budget for it. -5. Agora usernames — Trivial to implement, tests the namespace concept. -6. Contract templates + attestation — Seeds the Agora economy without needing full smart contracts. +5. Social protocol usernames — Trivial to implement, tests the namespace concept. +6. Contract templates + attestation — Seeds the social protocol economy without needing full smart contracts. 7. Compute marketplace — High risk/reward. Requires critical mass. Phase Zero bootstraps with cloud arbitrage. 8. Verification monopoly — Thesis-level bet. Invest when installed base justifies it. diff --git a/ideas/self-driving-lisp-machine.org b/ideas/self-driving-lisp-machine.org index dcf85a2..868765b 100644 --- a/ideas/self-driving-lisp-machine.org +++ b/ideas/self-driving-lisp-machine.org @@ -5,7 +5,7 @@ #+title: The Self-Driving Lisp Machine #+filetags: :passepartout:lisp-machine:hardware:riscv:tenstorrent: -A Tenstorrent P150 (~72 RISC-V Tensix cores) running [[id:28c46769-c14b-42aa-ac7a-69d310157f8f][Passepartout]]: 72 RISC-V cores running Lisp microcode, one core dedicated to ACL2, one to Screamer, the rest to gate verification and fact store operations. +A Tenstorrent P150 (~72 RISC-V Tensix cores) running Passepartout: 72 RISC-V cores running Lisp microcode, one core dedicated to ACL2, one to Screamer, the rest to gate verification and fact store operations. The self-driving threshold: the system can synthesize and load its own FPGA microcode or Tensix dispatch programs from within the running Lisp image. The system profiles its own gate verification latency, proposes a new microcoded instruction for the hot path, compiles RISC-V assembly from ACL2-verified specifications, loads it via PCIe DMA from within SBCL, benchmarks it — and rolls back if slower. diff --git a/ideas/alternative-growth-social-first.org b/ideas/social-growth-strategy.org similarity index 58% rename from ideas/alternative-growth-social-first.org rename to ideas/social-growth-strategy.org index ac2f3a9..d8fe2df 100644 --- a/ideas/alternative-growth-social-first.org +++ b/ideas/social-growth-strategy.org @@ -6,19 +6,19 @@ #+title: Alternative Growth — Social-First Scenario #+filetags: :passepartout:growth:strategy:alternative: -The existing growth-strategy assumes institution-first growth: compliance → developer → consumer → regulatory. This page documents an alternative path: grow as a general-purpose social identity network, let institutions catch up later. The triad components (Logos, [[id:c3b3dc41-945f-54e9-84eb-ca014114f1be][Stoa]], [[id:1d074690-a279-59cb-b91d-e9a22ae104ad][Agora]]) are the same; the order of operations and the primary growth levers differ fundamentally. +The existing growth-strategy assumes institution-first growth: compliance → developer → consumer → regulatory. This page documents an alternative path: grow as a general-purpose social identity network, let institutions catch up later. Passepartout's three subsystems ([[id:c3b3dc41-945f-54e9-84eb-ca014114f1be][the verification subsystem]], [[id:1d074690-a279-59cb-b91d-e9a22ae104ad][the social protocol]]) are the same; the order of operations and the primary growth levers differ fundamentally. * Why This Path Exists -The institution-first scenario ([[id:d28adac8-08a1-40c4-ae43-b5d8d7b1743f][growth strategy]]) takes the product's core technical capability — verification — and finds the customer with the clearest pain. That is the safe bet. But the triad ships with a second product that has nothing to do with verification: the Agora, a unified publishing network, contract platform, payment network, and decentralized identity layer rolled into one. No product on the market offers this combination — ENS is names, Bluesky is social, Stripe is payments, DocuSign is contracts. The Agora replaces all four with one provable layer. +The institution-first scenario ([[id:d28adac8-08a1-40c4-ae43-b5d8d7b1743f][growth strategy]]) takes the product's core technical capability — verification — and finds the customer with the clearest pain. That is the safe bet. But Passepartout ships with a second product that has nothing to do with verification: the social protocol, a unified publishing network, contract platform, payment network, and decentralized identity layer rolled into one. No product on the market offers this combination — ENS is names, Bluesky is social, Stripe is payments, DocuSign is contracts. The social protocol replaces all four with one provable layer. -The social-first scenario leans into what the Agora is /as a product/, not what the triad is /as a technology/. Publishing, payments, contracts, and identity are all mass-market primitives. They can grow without ever mentioning ACL2, gate rules, or compliance. Verification is the infrastructure underneath, invisible to users until they need it. +The social-first scenario leans into what the social protocol is /as a product/, not what Passepartout is /as a technology/. Publishing, payments, contracts, and identity are all mass-market primitives. They can grow without ever mentioning ACL2, gate rules, or compliance. Verification is the infrastructure underneath, invisible to users until they need it. Historical precedent: Instagram was a check-in app with filters. The camera and social graph came first; the advertising platform came later. Twitter was SMS broadcast; the real-time news network was emergent. In each case the product that users wanted had a different shape than the product that ultimately captured value. * Phase 0: Unified Digital Existence Layer (0 → 10K users, 3-12 months) -The key premise: the Agora is not an identity product. It is four layers in one — a publishing network, a contract platform, a payment network, and decentralized infrastructure — all unified under a single identity. No product on the market offers this combination. ENS is names only. Bluesky is social only. Stripe is payments only. The Agora replaces all of them with one provable layer. +The key premise: the social protocol is not an identity product. It is four layers in one — a publishing network, a contract platform, a payment network, and decentralized infrastructure — all unified under a single identity. No product on the market offers this combination. ENS is names only. Bluesky is social only. Stripe is payments only. The social protocol replaces all of them with one provable layer. Customer: Anyone who touches more than one of these layers today and feels the friction of managing separate accounts, separate reputations, and separate data silos. The most likely first adopters: - Creators who publish across platforms and want verified ownership of their content @@ -26,12 +26,12 @@ Customer: Anyone who touches more than one of these layers today and feels the f - Crypto-natives who understand self-sovereignty but are tired of blockchain UX - Developers building agents that need a persistent identity, payment channel, and data store -The /minimum viable Agora/ must ship all four layers at Phase 0. Not fully featured, but functional — enough that a user can register, publish a signed post, send a payment, and sign a simple contract using one identity. The value is in the unification: one account replaces four. +The /minimum viable social protocol/ must ship all four layers at Phase 0. Not fully featured, but functional — enough that a user can register, publish a signed post, send a payment, and sign a simple contract using one identity. The value is in the unification: one account replaces four. -Growth lever: Multi-vector network effects. The Agora grows not on a single curve but on four simultaneous curves: +Growth lever: Multi-vector network effects. The social protocol grows not on a single curve but on four simultaneous curves: 1. Publishing: each new creator attracts readers, who may become creators 2. Payments: each new payment user creates liquidity that makes the network more useful for everyone -3. Contracts: each new contract written on the Agora creates a template and a precedent +3. Contracts: each new contract written on the social protocol creates a template and a precedent 4. PDS: each new PDS increases the federation surface and the [[id:3c6b0449-a8fb-5b89-b82a-34efb21ef5b5][compute marketplace]] supply Any of these can be the primary growth vector in a given market. If publishing stalls in one region, payments might take off. This redundancy dramatically increases the probability that /some/ vector finds PMF. @@ -40,13 +40,13 @@ Tactics: 1. /Entry point optimization./ Ship all four layers but actively measure which one drives signups in each channel. If a blog post about "verified publishing" drives 10× more signups than a post about "decentralized identity," double down on publishing. The platform is unified enough that users who join for one reason discover the other three. -2. /Creator tools./ Offer a one-click "publish with provenance" widget. A creator writes on Substack, Medium, or their own blog, pastes the Agora embed, and every post is automatically signed and timestamped. Readers see a blue checkmark that links to the Agora attestation. This is a /better/ blue checkmark than Twitter's because it's cryptographically verifiable — and it works /across/ platforms. +2. /Creator tools./ Offer a one-click "publish with provenance" widget. A creator writes on Substack, Medium, or their own blog, pastes the social protocol embed, and every post is automatically signed and timestamped. Readers see a blue checkmark that links to the social protocol attestation. This is a /better/ blue checkmark than Twitter's because it's cryptographically verifiable — and it works /across/ platforms. -3. /Freelancer onboarding./ Ship an invoice-and-contract template: "Send a verified invoice. Get a signed contract. Get paid on the Agora." The freelancer registers once, and their invoices, contracts, and payment history are provably theirs. This is a /productivity tool/ first and a social network second — users join to get paid, stay because their professional reputation is on it. +3. /Freelancer onboarding./ Ship an invoice-and-contract template: "Send a verified invoice. Get a signed contract. Get paid on the social protocol." The freelancer registers once, and their invoices, contracts, and payment history are provably theirs. This is a /productivity tool/ first and a social network second — users join to get paid, stay because their professional reputation is on it. 4. /PDS hosting as infrastructure./ The PDS is the backbone, not the headline. Freemium model: first 1GB free, $5-15/mo for unlimited. The PDS stores your identity, content, contracts, and payment history in one place. The value prop: /one account, one data store, one reputation, everywhere/. -5. /Fee-based revenue./ The Agora takes 0.5-2% on payment transactions and 5-10% on marketplace contracts (data [[id:67faf52f-9126-50a7-b87e-2bedc610dac7][licensing]], compute). These fees are invisible to users (built into the platform layer) and scale with usage. Unlike subscription revenue, they require zero active selling — the platform grows, fees follow. +5. /Fee-based revenue./ The social protocol takes 0.5-2% on payment transactions and 5-10% on marketplace contracts (data [[id:67faf52f-9126-50a7-b87e-2bedc610dac7][licensing]], compute). These fees are invisible to users (built into the platform layer) and scale with usage. Unlike subscription revenue, they require zero active selling — the platform grows, fees follow. Revenue: | Stream | Year 1 target | Mature | @@ -58,27 +58,27 @@ Revenue: | Creator tools (Pro tier) | $50K-200K | $2-10M/yr | | Total | $270K-1.8M | $20-88M/yr | -The fees are the key difference from my earlier estimate. The Agora's payment and contract layers generate revenue /per transaction/ without requiring subscription growth. A user who never pays for PDS hosting still generates fees if they send a payment or sign a contract on the network. +The fees are the key difference from my earlier estimate. The social protocol's payment and contract layers generate revenue /per transaction/ without requiring subscription growth. A user who never pays for PDS hosting still generates fees if they send a payment or sign a contract on the network. Key metric: Platform usage across any of the four layers. Fee volume (total value processed through payments + contracts). Not DAU — a user who joins for payments and never publishes is still generating revenue. -Failure mode: The unified platform is harder to explain than a single-purpose product. "One account for identity, publishing, payments, and contracts" sounds like a pitch deck, not a product. The risk is that the /scope/ of the Agora makes it incomprehensible — users don't know what problem it solves because it solves too many. The mitigations: optimize for a single entry vector per channel, let users discover the others naturally. +Failure mode: The unified platform is harder to explain than a single-purpose product. "One account for identity, publishing, payments, and contracts" sounds like a pitch deck, not a product. The risk is that the /scope/ of the social protocol makes it incomprehensible — users don't know what problem it solves because it solves too many. The mitigations: optimize for a single entry vector per channel, let users discover the others naturally. * Phase 1: Network Effects — The Social Graph (10K → 1M users, 1-3 years) -Customer: The early adopter base expands to include privacy-conscious mainstream users. The trigger is a /platform failure event/: a major platform bans a creator, de-platforms a community, or suffers a data breach. When that happens, the Agora is ready — it offers the same social primitives (messaging, identity, publishing) but with ownership. +Customer: The early adopter base expands to include privacy-conscious mainstream users. The trigger is a /platform failure event/: a major platform bans a creator, de-platforms a community, or suffers a data breach. When that happens, the social protocol is ready — it offers the same social primitives (messaging, identity, publishing) but with ownership. -Growth lever: Metcalfe's law + switching cost. Each new user makes the network more valuable. But the real lock-in is the /reputation graph/: attestations, signatures, and data provenance are cumulative. A user with 3 years of verified activity on the Agora cannot replicate that on any other platform. The switching cost grows with time. +Growth lever: Metcalfe's law + switching cost. Each new user makes the network more valuable. But the real lock-in is the /reputation graph/: attestations, signatures, and data provenance are cumulative. A user with 3 years of verified activity on the social protocol cannot replicate that on any other platform. The switching cost grows with time. Tactics: -1. Ship verified messaging. Every message between Agora users is signed and timestamped. No third party can modify or delete it. The product pitch: /Twitter, but your tweets are yours, and nobody can rewrite history/. +1. Ship verified messaging. Every message between social protocol users is signed and timestamped. No third party can modify or delete it. The product pitch: /Twitter, but your tweets are yours, and nobody can rewrite history/. -2. Publish an attestation API. Third-party services (news outlets, marketplaces, social platforms) can query the Agora to verify a user's reputation. News comments show "verified human, 2yr history, no abuse flags." This creates /outbound value/ — the network becomes useful to people who aren't even on it. +2. Publish an attestation API. Third-party services (news outlets, marketplaces, social platforms) can query the social protocol to verify a user's reputation. News comments show "verified human, 2yr history, no abuse flags." This creates /outbound value/ — the network becomes useful to people who aren't even on it. -3. Offer PDS-to-PDS federation. Agora instances communicate directly. No central server. This differentiates from every centralized platform and gives a structural privacy advantage that no amount of VC funding can replicate. +3. Offer PDS-to-PDS federation. Social protocol instances communicate directly. No central server. This differentiates from every centralized platform and gives a structural privacy advantage that no amount of VC funding can replicate. -4. Introduce data licensing. Users can license their verified data to AI training companies, researchers, advertisers — on their own terms, with their own price. The Agora takes a 10-15% commission. This creates a /revenue share/ that users understand viscerally. Compare: X/Twitter makes billions selling user data and gives nothing back. Agora users get paid. +4. Introduce data licensing. Users can license their verified data to AI training companies, researchers, advertisers — on their own terms, with their own price. The social protocol takes a 10-15% commission. This creates a /revenue share/ that users understand viscerally. Compare: X/Twitter makes billions selling user data and gives nothing back. Social protocol users get paid. 5. Verification becomes visible. Each user's profile shows a "verification score" based on the length and depth of their attested history. Long-time users get a visible badge. This creates status competition around the /one thing nobody else can offer/: provable history. @@ -98,26 +98,26 @@ Failure mode: Network effects fail to trigger because the user experience is not * Phase 2: The Institution Crossover (1M → 10M users, 2-5 years) -Customer: At 1M+ active identities, the network has critical mass. Institutions (universities, media companies, government agencies, enterprises) can no longer ignore it because /their users are on it/. The crossover happens organically: a university registrar wants to issue verified credentials. A newsroom wants to publish with verified provenance. A regulator wants to use the Agora's attestation infrastructure because it already has users. +Customer: At 1M+ active identities, the network has critical mass. Institutions (universities, media companies, government agencies, enterprises) can no longer ignore it because /their users are on it/. The crossover happens organically: a university registrar wants to issue verified credentials. A newsroom wants to publish with verified provenance. A regulator wants to use the social protocol's attestation infrastructure because it already has users. Growth lever: Institutional network effects. Every institution that joins brings 10K-100K users with it (employees, students, customers). Each new institutional user increases the value of verification for everyone else. The growth curve becomes logistic with institutional jumps, not smooth organic growth. Tactics: -1. Ship the Stoa enterprise bundle (SSO, compliance reports, fleet management, audit logging). This was the /entire/ Phase 0-1 of the institution-first scenario. Here it is a Phase 2 feature — built to serve institutions that are already /inside/ the network, not sold to cold prospects. +1. Ship the environment subsystem enterprise bundle (SSO, compliance reports, fleet management, audit logging). This was the /entire/ Phase 0-1 of the institution-first scenario. Here it is a Phase 2 feature — built to serve institutions that are already /inside/ the network, not sold to cold prospects. -2. Offer verified credentialing: degrees, certifications, professional licenses, issued on the Agora, verifiable by anyone. The institution pays for the issuance. The graduate gets a portable, provable credential. +2. Offer verified credentialing: degrees, certifications, professional licenses, issued on the social protocol, verifiable by anyone. The institution pays for the issuance. The graduate gets a portable, provable credential. -3. Offer provenance publishing: news organizations publish articles signed by their Agora identity. Readers verify provenance in one click. Deepfakes and misinformation are detectable because the authentic source is attested. This creates a /consumer pull/ for verification that never existed in the institution-first scenario. +3. Offer provenance publishing: news organizations publish articles signed by their social protocol identity. Readers verify provenance in one click. -4. Verification appliances are now a /fulfillment order/, not a sales pitch. Institutions already inside the network ask: "Can we run our own instance?" The answer is yes — here is a Stoa appliance. The gate rule SDK is a value-up, not a product. +4. Verification appliances are now a /fulfillment order/, not a sales pitch. Institutions already inside the network ask: "Can we run our own instance?" The answer is yes — here is an environment subsystem appliance. The gate rule SDK is a value-up, not a product. 5. The compute marketplace activates naturally. With 10M+ users and thousands of institutions, compute supply and demand are both present without bootstrapping. Revenue: | Stream | Year 5 target | Mature | |--------+--------------+--------| -| Enterprise Stoa seats | $5-20M | $50-200M/yr | +| Enterprise environment subsystem seats | $5-20M | $50-200M/yr | | Verified credential issuance | $2-10M | $20-100M/yr | | Compute marketplace fees | $1-5M | $50-200M/yr | | PDS hosting (scaled) | $2-10M | $20-50M/yr | @@ -125,13 +125,13 @@ Revenue: | Verification appliances | $2-10M | $50-100M/yr | | Total | $13-60M | $210-750M/yr | -Key metric: Institutional join events. Enterprise Stoa subscriptions. Credentials issued. +Key metric: Institutional join events. Environment subsystem subscriptions. Credentials issued. Failure mode: The institution crossover never comes because the social graph stalls at 1M users — enough for a niche, not enough for critical mass. The network becomes a high-quality-but-small community like early App.net or Mastodon. Verification is real but irrelevant because the rest of the world is on different platforms. The institution-first scenario is still possible from here (direct enterprise sales), but the supposed advantage of "users first" has not materialized. * Phase 3: Default Infrastructure (10M → 1B+, 5-15 years) -Customer: At this scale, the Agora is the default identity and communication layer for a significant fraction of internet users. New users join because /everyone is there/. Institutions join because /everyone is there/. The regulatory capture that the institution-first scenario required as a /growth lever/ happens here as a /consequence/ — regulators adopt Agora attestation because it is the standard. +Customer: At this scale, the social protocol is the default identity and communication layer for a significant fraction of internet users. New users join because /everyone is there/. Institutions join because /everyone is there/. The regulatory capture that the institution-first scenario required as a /growth lever/ happens here as a /consequence/ — regulators adopt social protocol attestation because it is the standard. Growth lever: Default status. The network is the path of least resistance. A new social platform would need to replicate not just the user base but the entire attestation history, compute marketplace, and institutional infrastructure. The moat is not legal (regulation) but practical (installed base + cumulative value). @@ -167,28 +167,28 @@ Revenue: Same end state as growth-strategy.org Phase 3 — $1B+ across certifica I initially assessed institution-first as significantly more likely. The unified-layer correction narrows the gap considerably. Here is the revised assessment: -The social-first path's strongest argument — which I dismissed too quickly — is that the Agora is not competing with any single product. A competitor who beats it on publishing (Substack, Medium) cannot also beat it on payments (Stripe, PayPal) and contracts (DocuSign, LexisNexis) and identity management — simultaneously. The unification is not a feature; it is the structural advantage. Each layer reinforces the others, and competing against the whole stack requires matching all four, which no existing product does. +The social-first path's strongest argument — which I dismissed too quickly — is that the social protocol is not competing with any single product. A competitor who beats it on publishing (Substack, Medium) cannot also beat it on payments (Stripe, PayPal) and contracts (DocuSign, LexisNexis) and identity management — simultaneously. The unification is not a feature; it is the structural advantage. Each layer reinforces the others, and competing against the whole stack requires matching all four, which no existing product does. -The multi-vector growth also matters. The institution-first path has one entry vector (compliance pain) and one failure mode (wrong pricing or too early). The social-first path has four entry vectors, and any one of them reaching PMF carries the other three. The probability that publishing /or/ payments /or/ contracts /or/ identity ownership finds product-market fit is higher than the probability that any single one does. The failure requires /all four/ to fail simultaneously — a smaller target. +The multi-vector growth also matters. The institution-first path has one entry vector (compliance pain) and one failure mode (wrong pricing or too early). The social-first path has four entry vectors, and any one of them reaching PMF carries the other three. The probability that publishing /or/ payments /or/ contracts /or/ identity ownership finds product-market fit is higher than the probability that any single one does. The fee-based revenue model further improves Phase 0 economics. Payment processing fees scale with transaction volume, not user count. A small number of high-value users (freelancers sending invoices, creators selling subscriptions) can generate meaningful revenue before the network reaches critical mass. -However: the core tension remains. The team building the triad is a deep-tech verification team — their competence is ACL2, gate rules, provably correct systems. The social-first path requires the team to also be a consumer product team — UX design, growth loops, community management, creator partnerships, payment infrastructure, fraud detection. That is not /impossible/ (the team can hire) but it is a different company than the one building [[id:28c46769-c14b-42aa-ac7a-69d310157f8f][Passepartout]]. +However: the core tension remains. The team building Passepartout is a deep-tech verification team — their competence is ACL2, gate rules, provably correct systems. The social-first path requires the team to also be a consumer product team — UX design, growth loops, community management, creator partnerships, payment infrastructure, fraud detection. That is not /impossible/ (the team can hire) but it is a different company than the one building [[id:28c46769-c14b-42aa-ac7a-69d310157f8f][Passepartout]]. The institution-first path monetizes the team's /existing/ competence from day one. The social-first path requires building a second competence (consumer platform) that does not exist yet. This is the real distinction, not the product's inherent potential. -My updated assessment: the institution-first path is still higher probability, but not by the wide margin I initially claimed. The gap is narrower because the Agora as a unified layer is genuinely unprecedented. If the team can hire consumer product talent (or one founder has that skill), the social-first path becomes competitive. +My updated assessment: the institution-first path is still higher probability, but not by the wide margin I initially claimed. The gap is narrower because the social protocol as a unified layer is genuinely unprecedented. -The hybrid path may be the strongest: ship the four-layer Agora as a public platform /alongside/ the enterprise compliance sales. Let payments, publishing, and contracts grow organically while institutions fund the operation. The enterprise revenue buys time for the consumer product to find PMF. The consumer platform gives the enterprise pitch credibility ("we have 1M users") that pure enterprise sales cannot match. Neither path needs to be chosen — both can run in parallel as long as the enterprise revenue covers the burn. +The hybrid path may be the strongest: ship the four-layer social protocol as a public platform /alongside/ the enterprise compliance sales. * References - [[id:d28adac8-08a1-40c4-ae43-b5d8d7b1743f][Primary growth strategy — institution-first]] - [[id:ed05cab4-88e9-4e25-b7c9-346fa39c69a0][Revenue streams by component]] -- [[id:64708e1f-00e9-4cb7-b44b-ea0b98e5296d][Agora contract platform details]] +- [[id:64708e1f-00e9-4cb7-b44b-ea0b98e5296d][Social protocol contract platform details]] - [[id:528a0f6c-6fd6-41ed-9d59-237958bdaef2][Effects and growth as interleaved curves]] - [[id:dc2e4f22-1c4c-5d4a-a151-f96e5d3b0d70][Development timeline — Phase Zero and End State]] #+begin_quote -The social-first path is attractive because the end state is stronger. But the path to it requires building a consumer product alongside the deep-tech verification infrastructure — essentially running two startups in parallel. The [[id:0f949f6c-4cf1-49eb-b9a4-ebcac27ee548][Agora Social Space requirements]] describe the community interaction model that makes the social-first path viable.. The institution-first path is the higher-probability bet because it monetizes the core technical advantage from day one. +The social-first path is attractive because the end state is stronger. But the path to it requires building a consumer product alongside the deep-tech verification infrastructure — essentially running two startups in parallel. The [[id:0f949f6c-4cf1-49eb-b9a4-ebcac27ee548][Social protocol Social Space requirements]] describe the community interaction model that makes the social-first path viable.. #+end_quote diff --git a/ideas/stoa-overview.org b/ideas/stoa-overview.org deleted file mode 100644 index 82caa37..0000000 --- a/ideas/stoa-overview.org +++ /dev/null @@ -1,18 +0,0 @@ -:PROPERTIES: -:CREATED: [2026-05-24 Sun] -:ID: 42c86e6f-4f27-4993-8238-b7bc7d15fb7b -:ID: c3b3dc41-945f-54e9-84eb-ca014114f1be -:END: -#+title: Stoa — The Porch (Environment) -#+filetags: :passepartout:stoa:editor:browser:hardware: - -Stoa is the user environment — a single Lisp image where editor, browser, shell, and agent coexist. - -**Roadmap:** -- v2.0.0: Lish editor + Nyxt browser (Stage 1, Qt/WebKit) + Lish shell -- v3.0.0+: Cannibalization — replace Qt with Lisp-native layout, reduce WebKit to pixel-painting, eventually pure-Lisp browser and window management -- v4.0.0: Native inference — llama.cpp FFI in-process, DSL-compiled model architectures, live surgery on cognition -- v5.0.0: [[id:84a537b4-4256-50c8-91f5-dd5b4538418f][Hardware]] — tagged RISC-V architecture via TinyTapeout, FPGA prototype, hardware GC via dedicated bus master -- v6.0.0: True agency — world models, temporal reasoning, goal persistence across restarts - -The architectural principle: Stoa is not a collection of clients connecting to a daemon. The Dispatcher gate stack [[id:84a537b4-4256-50c8-91f5-dd5b4538418f][verifies every action]] regardless of who initiated it. The distinction between "tool" and "self" dissolves. The ultimate goal is a [[id:13e6ae54-2d24-5aa0-b1cd-a7e8e749aa70][self-driving Lisp Machine]] running on custom hardware. diff --git a/ideas/stoa/_index.org b/ideas/stoa/_index.org deleted file mode 100644 index ea1dd4e..0000000 --- a/ideas/stoa/_index.org +++ /dev/null @@ -1,28 +0,0 @@ -:PROPERTIES: -:CREATED: [2026-05-24 Sun] -:ID: c3b3dc41-945f-54e9-84eb-ca014114f1be -:END: -#+title: Stoa — The Porch (Environment) -#+filetags: :passepartout:stoa:editor:browser:hardware: - -Stoa (Στοά) is the body/environment layer of the [[id:1c3ec48b-446c-50d2-b53e-126a81f5143f][triad]] — editor, browser, shell, and infrastructure all running in a single [[id:84a537b4-4256-50c8-91f5-dd5b4538418f][verified Lisp image]]. The [[id:c34940cc-090e-57c4-8020-e78b1d32b96c][Dispatcher gate stack]] verifies every action regardless of who initiated it. The distinction between "tool" and "self" dissolves. - -The full roadmap is documented across seven stages on this page, each covering engineering, security, cost, timeline, and practical implications. Start reading from [[id:4a1f23b0-abc1-4def-9876-543210abcdef][Stage 0 — Now]]. - -The three layers of the triad: -- [[id:1c3ec48b-446c-50d2-b53e-126a81f5143f][Logos]] — the mind: recorded discourse, verified reasoning, the gate -- Stoa — the porch: environment, infrastructure, the verified Lisp machine -- [[id:1d074690-a279-59cb-b91d-e9a22ae104ad][Agora]] — the society: identity, communication, contracts - -Key features across all stages: -- **No kernel, no process boundaries, no memory corruption** — the verified Lisp evaluator is the only computation substrate -- **Merkle-verified memory graph** — every object has a [[id:1c95ce7d-a2db-506a-9608-df68f9ae211b][structural hash]], composable proofs of integrity -- **[[id:45ea493b-94ad-5885-aa65-0c846e5c3c1d][Gate-stack authorization]]** — the Dispatcher is the only path to state mutation, verified in [[id:84a537b4-4256-50c8-91f5-dd5b4538418f][ACL2]] -- **Dual-unit ASIC** — symbolic core (tagged RISC-V) + tensor unit (cons-cell-native matmul), one chip, one proof -- **In-process LLM inference** under [[id:45ea493b-94ad-5885-aa65-0c846e5c3c1d][gate-level token interception]] — no API calls, no sandbox to escape -- **Plist-native weights** — every weight Merkle-verified, provenance from training to inference -- **[[id:84a537b4-4256-50c8-91f5-dd5b4538418f][Verified fine-tuning]]** — every gradient step authorized against policy, data consent per example -- **Neural world model** (LeCun type) — sensory-physical prediction, falsified against the accumulated observation DAG -- **Common sense** enters through three channels (LLM, world model, causal inference) and is brought under gate control through falsification - -The ultimate goal is a [[id:13e6ae54-2d24-5aa0-b1cd-a7e8e749aa70][self-driving Lisp Machine]] running on custom dual-unit silicon. diff --git a/ideas/stoa/stoa-vision-roadmap.org b/ideas/stoa/stoa-vision-roadmap.org deleted file mode 100644 index f4845ba..0000000 --- a/ideas/stoa/stoa-vision-roadmap.org +++ /dev/null @@ -1,44 +0,0 @@ ---- -title: Stoa Vision Roadmap — The Porch -type: reference -tags: :reference:architecture:stoa: -created: 2026-05-24 ---- - -→ [[id:4a1f23b0-abc1-4def-9876-543210abcdef][Stage 0 — Now]] - -Stoa (Στοά) is the body/environment layer of the [[id:d71df46b-9012-433c-86ce-ec21b78eac5f][triad]]: - -| Logos | The mind — recorded discourse (memex + agent) | -| Stoa | The porch — editor, browser, shell, infrastructure | -| [[id:1d074690-a279-59cb-b91d-e9a22ae104ad][Agora]] | The society — identity, communication, contracts | - -The name comes from the Stoa Poikile (Painted Porch) in ancient Athens, -where Zeno taught Stoic philosophy. The porch was not the philosophy -itself — it was the environment that made discourse possible. Stoa is -the same: not the agent, not the network, but the infrastructure that -hosts both. - -The roadmap and threat model are merged into a single document. -Each stage covers: what is added, what threats are eliminated, what it -costs, what it enables, when it is viable, and what it means in practice. -Appendices at the end cover common sense, the bootstrap axiom, and a -summary table of eliminated threats. - -| Stage | Delivers | Key cost | Timeline | -|-------+----------+----------+----------| -| [[id:4a1f23b0-abc1-4def-9876-543210abcdef][0 — Now]] | Baseline: conventional computing | Patching treadmill, no deductive guarantees | Today | -| [[id:4a1f23b0-abc2-4def-9876-543210abcdef][1 — Agora]] | Communication integrity, provable DAG | Crypto overhead, key management | Today | -| [[id:4a1f23b0-abc3-4def-9876-543210abcdef][2 — Logos]] | Verified gate, capability auth | Policy formalization burden | Today (limited) | -| [[id:4a1f23b0-abc4-4def-9876-543210abcdef][3 — Stoa]] | Lisp machine, Merkle memory, no kernel | Lisp tax, no backward compat, single address space | 2-5yr (soft) / 5-10yr (ASIC) | -| [[id:4a1f23b0-abc5-4def-9876-543210abcdef][4 — Inference]] | In-process LLM, token interception | ~10x compute/RAM/storage | Server now; consumer 3-5yr | -| [[id:4a1f23b0-abc6-4def-9876-543210abcdef][5 — Weights]] | Plist-native weights, weight-level provenance | ~100x GPU / ~2-5x ASIC | GPU hybrid now; ASIC 5-10yr | -| [[id:4a1f23b0-abc7-4def-9876-543210abcdef][6 — Training]] | Verified fine-tuning, neural world model | ~100x fine-tuning only | 3-5yr fine-tuning | -| [[id:4a1f23b0-abc8-4def-9876-543210abcdef][7 — Remaining]] | Physical threats, oracles, speculation, bootstrap axiom | Mitigations are non-computational | Forever | - -→ [[id:4a1f23b0-abc1-4def-9876-543210abcdef][Stage 0 — Now]] - -:PROPERTIES: -:CREATED: [2026-05-24 Sun] -:ID: 3f24ad65-0845-4e75-a3d7-dc4de734a6ac -:END: diff --git a/ideas/time-estimates.org b/ideas/time-estimates.org index 1f90e3c..a8ce3b7 100644 --- a/ideas/time-estimates.org +++ b/ideas/time-estimates.org @@ -18,10 +18,10 @@ Run on Linux, use C libraries through CFFI, deliver value without replacing the | Component | Lines | Method | Scale | |----------+-------+--------+-------| | Neurosymbolic core (ACL2 + Screamer + LLM bridge) | ~4,500 | Agent-generated Lisp, human-validated | Weeks — dense, well-bounded, proven approach | -| Terminal-based [[id:c3b3dc41-945f-54e9-84eb-ca014114f1be][Stoa]] (editor + REPL + shell) | ~2,000 | CL-charms / cl-tty | Weeks — TUI patterns established | +| Terminal-based [[id:c3b3dc41-945f-54e9-84eb-ca014114f1be][environment subsystem]] (editor + REPL + shell) | ~2,000 | CL-charms / cl-tty | Weeks — TUI patterns established | | Gate rule SDK + marketplace | ~1,500 | ACL2 gate packages | Weeks — pure symbolic, well-specified | | CFFI wrappers (system, GPU, crypto, storage) | ~2,000 | Thin bindings | Days — mechanical translation | -| [[id:84a537b4-4256-50c8-91f5-dd5b4538418f][Verification appliance]] CLI + [[id:1d074690-a279-59cb-b91d-e9a22ae104ad][Agora]] namespace | ~1,000 | API surface | Weeks | +| [[id:84a537b4-4256-50c8-91f5-dd5b4538418f][Verification appliance]] CLI + [[id:1d074690-a279-59cb-b91d-e9a22ae104ad][social protocol]] namespace | ~1,000 | API surface | Weeks | *Total MVP: ~11,000 lines. Timeline: 1-3 months. Human review: ~20 hours.* @@ -41,7 +41,7 @@ Replace Linux, replace C libraries, own the framebuffer, own the browser. This i | Browser (WebKit embed) | WebKit via Lisp FFI with verified wrappers | ~3,000 | Months — sandboxing the embed | Web platform surface is unbounded | | Native browser | Full Lisp DOM + render engine | ~30,000+ | Years — browser engines are OS-scale | This is the hardest piece. Consider staying on WebKit | | Core libraries (libc, SSL, crypto, etc.) | Incremental verified replacements | ~10,000+ | Years — can chip away post-ship | Every replacement must match SOTA perf | -| Qt / terminal / native UI toolkit | Stoa toolkit (verified compositor + widgets) | ~8,000 | Months–years | UX parity with modern toolkits is the highest risk | +| Qt / terminal / native UI toolkit | Environment toolkit (verified compositor + widgets) | ~8,000 | Months–years | UX parity with modern toolkits is the highest risk | *Ballpark end state: 25,000-60,000 lines. Timeline: 2-5 years.* @@ -53,7 +53,7 @@ The range reflects uncertainty about the browser. If WebKit embed is sufficient |---------+---------+-----------+----------------------| | Does the verification marketplace work? | Company thesis | Months (Phase Zero) | Solved in days | | Can we ship without replacing Linux? | Time-to-market | Weeks to implement | Years of kernel work before product | -| Is WebKit embed enough for Stoa? | 60% of total timeline | Months vs years | Native browser as default path | +| Is WebKit embed enough for the environment subsystem? | 60% of total timeline | Months vs years | Native browser as default path | | Does the sufficiency flip cover each domain? | Revenue model | Weeks per domain | One-shot, all or nothing | | Can Lisp match SOTA browser UX? | Full vision | Generations (or never) | Engineering problem, not a research question | diff --git a/ideas/triad-index.org b/ideas/triad-index.org deleted file mode 100644 index 9a7d60d..0000000 --- a/ideas/triad-index.org +++ /dev/null @@ -1,45 +0,0 @@ -:PROPERTIES: -:CREATED: [2026-05-24 Sun] -:ID: 1c3ec48b-446c-50d2-b53e-126a81f5143f -:END: -#+title: Passepartout Triad — Knowledge Base -#+filetags: :passepartout:triad:economics:index: - -The triad replaces every layer of the modern computing stack with Lisp-native, user-owned, ACL2-verified alternatives. Three components: - -- [[id:a1fac32a-47de-5fbd-b67d-29152c851747][Logos (Passepartout) — the cognitive agent]] -- [[id:c3b3dc41-945f-54e9-84eb-ca014114f1be][Stoa (The Porch) — the environment]] -- [[id:1d074690-a279-59cb-b91d-e9a22ae104ad][Agora (The Society) — the network]] - -Total addressable market: ~$960B/year across cloud, AI, OS, social media, payments, productivity, and compliance. - -The business model is the AWS of provable computing: AGPL infrastructure is free, revenue comes from verification appliances, gate rules, certification, namespace registry, hosted PDS, and a [[id:3c6b0449-a8fb-5b89-b82a-34efb21ef5b5][compute marketplace]]. Network effects are positive sum — every instance feeds the regression suite and grows the marketplace. - -[[id:1c95ce7d-a2db-506a-9608-df68f9ae211b][Lisp Machine security — unified memory threat model]] -[[id:04c2f221-c54f-51e5-b40a-48822cd16d45][Common Logic (ISO 24707) — relevance to the triad]] -[[id:a5d59d12-b23e-58d6-a81b-9b8b06556949][Collective regression suite — how it compounds]] - -Key analytical frames: -- [[id:5961e469-53a3-5f3c-ab72-3c83ef91963f][Investment thesis — the unified view]] -- [[id:9af13fff-9725-542b-93b1-a555bc74ad72][Why Lisp is economically viable now]] -- [[id:efc76898-03f7-57ba-923d-35d65da88bb7][The per-domain sufficiency flip]] -- [[id:dc2e4f22-1c4c-5d4a-a151-f96e5d3b0d70][Development velocity and timeline estimates]] -- [[id:0b5a8a74-cfd6-542d-bc88-4eb3cd8626f9][Cost structure and zero marginal cost]] -- [[id:aa6d062e-a520-5d14-8773-00687ed9c689][Competitive moats analysis]] - -Revenue paths (short to long term): -- [[id:84a537b4-4256-50c8-91f5-dd5b4538418f][Verification appliance]][[id:c34940cc-090e-57c4-8020-e78b1d32b96c][ Domain gate packages]][[id:45258a2d-1675-562c-9024-5d1eb2f1ea56][ Evaluation harness]] -- [[id:2e390c1d-65f3-5fb3-b898-ac3fc4291ee7][Agora premium usernames]][[id:1a2b38df-20ba-58ca-ba55-a072be67bd0d][ PDS as a service]][[id:3c6b0449-a8fb-5b89-b82a-34efb21ef5b5][ Compute marketplace]] -- [[id:827bc546-e887-5b7c-9b65-6392beaf0920][Verification monopoly — the big money]][[id:2f783eb4-638e-5afa-9b59-6224d086a712][ Infrastructure lock-in]] - -Strategy and IP: -- [[id:caaeee11-ba6f-5566-aecd-f171b4c459c0][Patent strategy]][[id:67faf52f-9126-50a7-b87e-2bedc610dac7][ Licensing (AGPL + commercial)]] -- [[id:5f55bbe6-d243-5766-8ccf-5c5cc88a6542][Impact on the AI/GPU industry]] -- [[id:29e4dbf3-cf19-589c-8b14-389e8a39d564][Upgrade and distribution lifecycle]] -- [[id:45ea493b-94ad-5885-aa65-0c846e5c3c1d][Gate rule encoding from codified domains]] -- [[id:2afd9a3c-e96a-54c7-ac77-a05a28065b4b][Biology as proof of the Lisp model]] -- [[id:00ab3a4d-e3de-5605-a67d-12935bb36ab5][Comparison with Symbolics Genera]] - -The [[id:b25bf753-9799-41ab-82f5-1a1416db756b][Agora protocol overview]] and [[id:a3243dd0-3209-423b-98e1-51c3eada2658][advanced integration]] requirements define how the gate stack connects to Agora's network layer. The [[id:72570648-d943-42e5-a781-3b09791ac6ec][realistic assessment]] covers deployment timelines and adoption risks. - -*The lines that run the modern internet (tens of millions across Google, Meta, Amazon, Apple, Microsoft) are replaced by a single coherent architecture where one gate stack verifies everything and one prover proves everything consistent.* diff --git a/ideas/triad-overview.org b/ideas/triad-overview.org deleted file mode 100644 index 69d76e9..0000000 --- a/ideas/triad-overview.org +++ /dev/null @@ -1,16 +0,0 @@ -:PROPERTIES: -:CREATED: [2026-05-24 Sun] -:ID: a1fac32a-47de-5fbd-b67d-29152c851747 -:END: -#+title: Triad Overview — Logos, Stoa, Agora -#+filetags: :passepartout:triad:architecture: - -The full triad is a self-bootstrapping replacement for the entire computing stack, not a single product. - -**Logos ([[id:28c46769-c14b-42aa-ac7a-69d310157f8f][Passepartout]])** — The mind. Cognitive agent combining a probabilistic LLM (10% of work) with a deterministic symbolic engine (80%) at near-zero marginal cost. Gate stack, fact store, ACL2 prover, Screamer constraint solver. - -**Stoa (The Porch)** — The body. Editor (Lish), browser (Nyxt), shell (Lish), Org-mode filesystem, Qt/EQL5 UI. A single Lisp image where everything coexists. Roadmap: v2.0.0 (Qt/WebKit) → v6.0.0 (pure Lisp, hardware). - -**Agora (The Society)** — The network. Self-sovereign DID identity, DIDComm encrypted messaging, [[id:1a2b38df-20ba-58ca-ba55-a072be67bd0d][Personal Data Store]], Relay Network, [[id:3c6b0449-a8fb-5b89-b82a-34efb21ef5b5][compute marketplace]], liquid democracy. - -All three speak plists. All three operate in Lisp address space. All three are verified by the same ACL2 prover. The gate stack that verifies a shell command also verifies a DIDComm message. See [[id:5961e469-53a3-5f3c-ab72-3c83ef91963f][The See the [[id:b25bf753-9799-41ab-82f5-1a1416db756b][Agora protocol overview]] for how the three triad components fit into Agora's network architecture. [[id:5961e469-53a3-5f3c-ab72-3c83ef91963f][The investment thesis]]]] for the economic rationale and [[id:84a537b4-4256-50c8-91f5-dd5b4538418f][Verification appliance]] for the hardware that enables this unified architecture. diff --git a/ideas/verification-appliance.org b/ideas/verification-appliance.org index b74846c..0e53699 100644 --- a/ideas/verification-appliance.org +++ b/ideas/verification-appliance.org @@ -12,6 +12,6 @@ An FPGA or Tenstorrent card pre-loaded with a mature [[id:28c46769-c14b-42aa-ac7 The [[id:13e6ae54-2d24-5aa0-b1cd-a7e8e749aa70][Lisp Machine]] on Tenstorrent P150 (~72 RISC-V Tensix cores on a PCIe card) is the realistic first target: the microcode is RISC-V assembly (software), not FPGA bitstream (hardware). The system can propose, load, test, and roll back a new dispatch routine in seconds. An FPGA path would add synthesis time (minutes to hours per iteration). This hardware-first approach embodies [[id:9af13fff-9725-542b-93b1-a555bc74ad72][Lisp economics]] — verification hardware has near-zero marginal cost. The [[id:29e4dbf3-cf19-589c-8b14-389e8a39d564][Upgrade lifecycle]] for the appliance is managed via signed firmware updates with Merkle snapshots. -The [[id:6fe67db6-25bd-4d11-bd1d-b44ec809e858][Agora identity specification]] shows how the verification appliance issues provable identities for network participants. The [[id:5f55bbe6-d243-5766-8ccf-5c5cc88a6542][impact on the AI and GPU industry]] analysis covers how this new hardware tier — CPU-native Lisp microcode on RISC-V cores — reshapes the industry structure. +The [[id:6fe67db6-25bd-4d11-bd1d-b44ec809e858][Social protocol identity specification]] shows how the verification appliance issues provable identities for network participants. The [[id:5f55bbe6-d243-5766-8ccf-5c5cc88a6542][impact on the AI and GPU industry]] analysis covers how this new hardware tier — CPU-native Lisp microcode on RISC-V cores — reshapes the industry structure. Revenue estimate: 50 sales in year one = $250K-$2.5M. diff --git a/ideas/verification-monopoly.org b/ideas/verification-monopoly.org index b263749..4cef5f6 100644 --- a/ideas/verification-monopoly.org +++ b/ideas/verification-monopoly.org @@ -13,4 +13,4 @@ Any organization claiming a "safe AI agent" needs [[id:28c46769-c14b-42aa-ac7a-6 This is the venture-scale outcome. It depends on the [[id:45258a2d-1675-562c-9024-5d1eb2f1ea56][evaluation harness]] reaching critical mass, which depends on enough instances deploying the software to accumulate edge cases in the regression suite. The [[id:5961e469-53a3-5f3c-ab72-3c83ef91963f][investment thesis]] is built on the recognition that every deployed instance makes this more valuable. -The unique structural advantage: every free instance of the triad feeds the regression suite. The more people use the free software, the more valuable the certification monopoly becomes. Positive sum. This creates deep [[id:2f783eb4-638e-5afa-9b59-6224d086a712][infrastructure lock-in]] and powerful [[id:aa6d062e-a520-5d14-8773-00687ed9c689][moats]] — a competitor cannot replicate the certification without the accumulated history. The ultimate impact is a transformation of the entire [[id:5f55bbe6-d243-5766-8ccf-5c5cc88a6542][AI industry]], where safety certification becomes a prerequisite for market access. +The unique structural advantage: every free instance of Passepartout feeds the regression suite. The more people use the free software, the more valuable the certification monopoly becomes. Positive sum. This creates deep [[id:2f783eb4-638e-5afa-9b59-6224d086a712][infrastructure lock-in]] and powerful [[id:aa6d062e-a520-5d14-8773-00687ed9c689][moats]] — a competitor cannot replicate the certification without the accumulated history. The ultimate impact is a transformation of the entire [[id:5f55bbe6-d243-5766-8ccf-5c5cc88a6542][AI industry]], where safety certification becomes a prerequisite for market access.