Skip to content
Open
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
13 changes: 8 additions & 5 deletions docs/decisions/0002-pricing-fees-and-member-privacy.md
Original file line number Diff line number Diff line change
@@ -1,15 +1,18 @@
# 0002 — Pricing, fees, and member privacy

- **Status:** Accepted, 2026-11-03
- **Decided by:** Jodson Graves (President) and Calvin Secrest (Vice President), NTARI
- **Status:** Accepted, 2026-11-03, as a bootstrap act (bylaws §16.1)
- **Decided by:** Jodson Graves (President) and Calvin Secrest (Vice President), NTARI, for the founder board, which exercises the powers of the membership during bootstrap (§16.1)
- **Governance registry:** to be entered as a bootstrap act (§9.5, §16.1)
- **Builds on:** [0001](0001-node-connects-through-its-frontend.md) (a member's computer connects through its frontend)
- **Applies to:** Cloudy (and every frontend), SoHoLINK (and every orchestrator), sohocloud-protocol's fee terms
- **Revisit:** open to change like every decision (bylaws §2.3)
- **Revisit:** a bootstrap act stays valid and stays open to the membership under bylaws §2.3, like any other decision

## Context

Decision 0001 took persons out of the orchestrator: SoHoLINK talks only to frontends. That left open who pays whom for work done on a member's computer. Until now SoHoLINK took each job's payment, kept a platform share, and paid the computer's owner through Stripe — which needs SoHoLINK to know that owner.

The fee model below departs from the official document. Its Record layer (Janus `janus-facing-architecture.md`, line 61) escrows the orchestrator's transport fee with the trade, releases it only when the witnesses attest delivery, and splits it between the two prosumers' home ledgers, each paying its share in its own unit; Janus `OPEN-QUESTIONS.md` entry 10 treats that as settled in draft. Here each frontend pays the transport fee instead. The founder board adopts this model as a bootstrap act under bylaws §16.1. This record does not change the official document's text; only an amendment under §9.2 can.

## Decision

### Who pays whom
Expand All @@ -22,7 +25,7 @@ Decision 0001 took persons out of the orchestrator: SoHoLINK talks only to front

- **The consumer pays the producer through their platforms' own settlement**, never through the orchestrator:
- **Escrow** where that is the standard of both networks: the consumer's payment is held by the operator and released to the producer.
- **Mutual credit** only where both platforms allow it and are registered for it (L10: governance approval, membership notice, completed regulatory review): the producer earns community credit on their frontend's ledger, and each exchange moves two balances that net to zero (L1).
- **Mutual credit** only where both platforms allow it and have passed the escrow-to-credit gate (L10; bylaws §11.1–11.3): the operator has built the capacity to run it under local law; its prosumers and the federation have had at least 30 days' notice; and the local authorizations, or a finding that none are required, are published to the governance registry. Publication is the act, with no approval step added (§7.6, §10.7). A switch to full mutual credit is also ratified by the deployment's prosumers (L10). Under mutual credit the producer earns community credit on their frontend's ledger, and each exchange moves two balances that net to zero (L1).
- Escrowed money and community credit are never mixed (the economy-layer wall).
- **The orchestrator bills frontends only.** It holds no member money and pays no member. Its role is transport between networks.

Expand All @@ -45,7 +48,7 @@ A trade between two networks is two sovereign spends — one on each network's l
## Consequences

- **SoHoLINK:** an operator registers its members' computers with no person attached — no participant, hostname, country, or payout account. SoHoLINK's Stripe payout to a computer's owner does not apply to operator-registered computers.
- **Cloudy:** settles its members' trades itself (escrow now; mutual credit through `internal/economy` once registered); collects its coordination fee from prosumers; pays SoHoLINK's transport fee for cross-network trades.
- **Cloudy:** settles its members' trades itself (escrow now; mutual credit through `internal/economy` once Cloudy passes the escrow-to-credit gate); collects its coordination fee from prosumers; pays SoHoLINK's transport fee for cross-network trades.
- **SoHoLINK's open question is answered:** its `CLAUDE.md` asks whether the coordinator settles with the member or with the frontend. Under this decision it settles only with the frontend, and only for the transport fee.
- **sohocloud-protocol:** today's fee terms (`fees.Terms`: a contributor share and a platform share of a job's price) describe the orchestrator splitting a payment. Under this decision the orchestrator charges a transport fee to frontends instead. Changing the terms is a wire change: SPEC first, then a version bump.

Expand Down
9 changes: 6 additions & 3 deletions internal/consumerapi/economy.go
Original file line number Diff line number Diff line change
Expand Up @@ -113,9 +113,12 @@ type spendRequest struct {
//
// While the governed policy is escrow mode, the ledger refuses every spend
// with ErrCreditDisabled and this endpoint reports that honestly as 409 —
// the escrow→credit transition is a governed PolicyChange (bylaws §5.7:
// Board approval, membership notice, completed regulatory review), never an
// API affordance. There is deliberately no endpoint that could flip it.
// the escrow→credit transition is a governed PolicyChange, made only once
// the operator passes the gate of L10 and bylaws §11.1–11.3 (capacity built,
// 30 days' notice, authorizations or a finding that none are required
// published to the governance registry, prosumer ratification for full
// credit; no Board approval step, §7.6), never an API affordance. There is
// deliberately no endpoint that could flip it.
func (s *Server) handlePostSpend(w http.ResponseWriter, r *http.Request) {
var req spendRequest
if err := json.NewDecoder(r.Body).Decode(&req); err != nil {
Expand Down
Loading