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

triad: Logos (Passepartout), Stoa (the Porch), Agora (the Society)

Browse Source 
- Passepartout IS the PDS — memory-object (SHA-256 hash) maps
  directly to Agora Note (CIDv1). Gate stack verifies every note.
- Stoa: Lish editor + Nyxt browser + Lish shell in one Lisp image.
  v2.0.0→v6.0.0: Qt/WebKit erosion to pure-Lisp browser, tagged
  RISC-V hardware, world models.
- Agora: self-sovereign DID, DIDComm, Note primitives, Relay Network,
  compute marketplace, contracts, liquid democracy.
- The triad replaces every layer of the modern computing stack:
  cognition, environment, network, app model, compute, identity,
  commerce — all built on one gate stack, one memory model, one prover.
- Agora implementation is a separate body of work comparable to
  Passepartout itself.
This commit is contained in:
Hermes
2026-05-21 19:17:28 +00:00
parent d48925de23
commit 434f754c15
1 changed files with 98 additions and 0 deletions
Download Patch File Download Diff File Expand all files Collapse all files

98
ideas/passepartout-economics.org
View File

@@ -1067,6 +1067,104 @@ The surprising result: **a self-driving Lisp Machine is a ~21,000
line project for a small team working less than a year.** Not a
billion-dollar moonshot. A well-scoped engineering project.
*** The full triad: Logos, Stoa, Agora
The self-driving Lisp Machine is not the endpoint. It is one
component of a three-part architecture:
| Layer | Name | Function | What it is |
|-------|------|----------|-----------|
| Logos | Passepartout | The mind | Cognitive agent, symbolic engine, gate stack, fact store, ACL2, 10-80-10 planner |
| Stoa | The Porch | The body | Editor (Lish), browser (Nyxt), shell (Lish), Org-mode filesystem, Qt/EQL5 UI, Lisp Machine hardware |
| Agora | The Society | The network | Self-sovereign identity (DID), encrypted comms (DIDComm), Personal Data Store, Relay Network, contracts, liquid democracy, compute marketplace |
**** Passepartout is the PDS
Agora's Personal Data Store (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 (Merkle provenance),
which maps directly to Agora's CIDv1 content addressing. The mapping:
| Passepartout memory-object | Agora Note |
|----------------------------|------------|
| org-object-id | uuid (stable) |
| org-object-hash | cid (content hash) |
| getf attrs :TITLE | payload (derived) |
| getf attrs :TAGS | routing/access-control hints |
| org-object-content | payload body |
| merkle hash | CIDv1 (same SHA-256, different formatting) |
Passepartout's gate stack verifies every action before it touches
the PDS. No unverified note escapes. ACL2 proves the access controls
are correctly enforced. Screamer checks consistency with the
instance's existing knowledge.
**** Stoa is the body
Stoa's roadmap (v2.0.0 → v6.0.0) describes the environment:
- v2.0.0: Lish editor + Nyxt browser (Stage 1, Qt/WebKit) + Lish shell
- v3.0.0+: Cannibalization — eat dependencies one by one. 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 (inspect hidden
states mid-inference)
- v5.0.0: 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. It is a single Lisp image where the editor,
browser, shell, and agent coexist. The Dispatcher gate stack
verifies every action regardless of who initiated it — user or
agent. The distinction between "tool" and "self" dissolves.
**** Agora is the network
Agora provides the decentralized identity and communication layer
so Passepartout instances can talk to each other:
- Self-sovereign identity via HD key derivation (BIP-44)
- Encrypted messaging via DIDComm (agent-to-agent)
- Notes as atomic, content-addressed, signed data units
- Relay Network for censorship-resistant message routing
- Compute marketplace where instances offer symbolic engine capacity
- Contracts and liquid democracy infrastructure
Agora integration is a parallel track to Passepartout's core
roadmap (v0.3.0 → v1.0.0). The identity DID and DIDComm gateway
can be built as skills at any time without core changes. The PDS
transformation (making the fact store network-addressable) waits
for v1.0.0+.
**** The complete picture
The triad replaces every layer of the modern computing stack:
| Layer | Current (Big Tech) | Triad |
|-------|-------------------|-------|
| Cognition | ChatGPT, Claude, Gemini (centralized API, per-token pricing) | Passepartout (local symbolic engine, near-zero marginal cost) |
| Environment | macOS/Windows/ChromeOS (closed platforms) | Stoa (Lisp-native editor, browser, shell, hardware) |
| Network | Facebook, Twitter, Slack, Discord (extractive, centralized) | Agora (DID-based, encrypted, user-owned, permissionless) |
| App model | Web apps + app stores (gatekeepers take 30%) | Skills + Org files (hot-reloadable, no gatekeeper) |
| Compute | Hyperscaler cloud (AWS, GCP, Azure) | Verification appliance (local, provable, near-zero marginal cost) |
| Identity | OAuth/Google/Apple SSO (surveillance-based) | Self-sovereign DID + HD key hierarchy (user-owned) |
| Commerce | Stripe, PayPal (2-3% + chargeback risk) | Lightning Network + smart contracts (permissionless) |
The line count estimate (21,000 for Passepartout + Lisp Machine)
covers only Logos + Stoa's hardware layer. Agora's full
specification spans 10 requirements documents and the implementation
(network protocol, PDS, Relay, DID identity) is a separate body of
work comparable to Passepartout itself.
The unifying factor: 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 and an Agora Note publication. The symbolic engine
that plans a refactoring also plans a contract negotiation.
One gate stack. One memory model. One prover.
Large refactoring projects (extract module, rename API, split monolith)
are the hardest test for any AI agent. Current approaches (Claude Code,
Copilot) handle them probabilistically — every step costs tokens, and