Concept

A pane store for the data browser — like WordPress plugins but for Solid panes. Pod owners browse, preview, and install panes. Premium panes are paid via the /pay/* API.

How it works

1. Discovery — GET /pay/.info returns available panes with pricing
2. Preview — free panes load directly; premium panes show description + price
3. Purchase — buy via /pay/.buy or deposit sats, pane unlocks
4. Install — pane JS module loads into the data browser (mashlib already supports dynamic pane loading)
5. Provenance — each pane is signed (did:nostr) and anchored via blocktrails (Skill provenance via blocktrails anchoring #183), so users know who wrote it and can verify the full version history

Analogy

Architecture

• Registry: JSON-LD listing at e.g. /.well-known/panes.json or federated across pods
• Pane format: ES module URL + metadata (name, author, version, price, description)
• Payment: existing pay API — deposit sats, buy access
• Trust: did:nostr authorship + blocktrails provenance (Skill provenance via blocktrails anchoring #183) + Nostr WoT ratings
• Distribution: panes served from author's pod, paid access via 402

Related

• Skill provenance via blocktrails anchoring #183 — Skill provenance via blocktrails (same pattern applies to panes)
• AAM (https://aam.wtf/) — agentic skill signing, same did:nostr identity model
• Mashlib already supports loading external pane modules via --mashlib-module