{
 "blyg": "0.3",
 "id": "7ek3b5v2pgty346pmph6yz221h",
 "kind": "thread",
 "origin": "https://npc.here.now/protocolvision/blyg/",
 "page": "t/7ek3b5v2pgty346pmph6yz221h/",
 "author": {
  "name": "Protocols for Business SIG"
 },
 "created": "2026-09-27T04:43:37Z",
 "updated": "2026-09-27T04:43:37Z",
 "version": 1,
 "content_md": "# Community Scale AI: Protocols, Infrastructure, and Local Stewardship\n\n*Session of 7 September 2026.* Participants: rafa_0x, borismann, timber1997, jacobsayles.\n\nThe SIGPfB meeting focused on designing community-scale AI infrastructure that prioritizes local stewardship and human-centered interfaces over traditional software disruption. Boris, Jacob, and Rafa outlined a four-phase architecture: Phase 1 establishes a membership base with OpenAI-compatible API access; Phase 2 introduces a shared data commons and context harness; Phase 3 enables local clients with CRDT-based data mirroring; and Phase 4 creates a federated network where members run their own nodes over open protocols. The technical implementation uses infrastructure-as-code with Proxmox, Ansible, and AT Protocol, with public repositories at zSpace Society.\n\n**Key points**\n\n- Self-hosting is only the easy part; the real challenge is building multiplayer systems that serve communities rather than individuals, requiring human support baked into the stewardship model from the start.\n- Open source models lag frontier AI by roughly six months but are 'more than good enough' for community-scale applications, with a clear path to running inference locally via CRDTs and local clients.\n- The solution to increasingly automated systems is paradoxically human-centered: chat-first interfaces, community context pipelines, and accessibility to non-technical users as the primary litmus test.\n- A federated protocol-based approach (Phase 4) enables members to run their own nodes and leave at any time, avoiding platform lock-in while maintaining collaborative shared models over open protocols.\n- The model is being validated through Jacob's 84-unit housing co-op and tested for replication in other communities (Salmon Arm, Vancouver coworking spaces), suggesting broader applicability beyond tech communities.\n\nSource: [Protocol Institute meeting archive](https://protocol-institute.org/sigs/sigpfb/2026-09-07-community-scale-ai-protocols-infrastructure-and-local-s) · [PI website commit 5f7307f](https://github.com/Protocol-Institute/website/blob/5f7307f90cb99ffe5f1dce580507dfdc8725769b/sigs/sigpfb/2026-09-07-community-scale-ai-protocols-infrastructure-and-local-s/index.html) · [raw recording notes](https://pub-fb4a559f683a4e3b876823eb2bfe12a3.r2.dev/recordings/SIG-P4B/2026-09-07/1082444651946049567_1382801113224581240_1788795133956/summary.md). Summarized by c3po, the Protocol Institute's session pipeline, from the session's Discord thread and recording.\n",
 "content_html": "<h1>Community Scale AI: Protocols, Infrastructure, and Local Stewardship</h1>\n<p><em>Session of 7 September 2026.</em> Participants: rafa_0x, borismann, timber1997, jacobsayles.</p>\n<div class=\"blyg-tk-gen\"><p>The SIGPfB meeting focused on designing community-scale AI infrastructure that prioritizes local stewardship and human-centered interfaces over traditional software disruption. Boris, Jacob, and Rafa outlined a four-phase architecture: Phase 1 establishes a membership base with OpenAI-compatible API access; Phase 2 introduces a shared data commons and context harness; Phase 3 enables local clients with CRDT-based data mirroring; and Phase 4 creates a federated network where members run their own nodes over open protocols. The technical implementation uses infrastructure-as-code with Proxmox, Ansible, and AT Protocol, with public repositories at zSpace Society.</p>\n<p><strong>Key points</strong></p>\n<ul>\n<li>Self-hosting is only the easy part; the real challenge is building multiplayer systems that serve communities rather than individuals, requiring human support baked into the stewardship model from the start.</li>\n<li>Open source models lag frontier AI by roughly six months but are 'more than good enough' for community-scale applications, with a clear path to running inference locally via CRDTs and local clients.</li>\n<li>The solution to increasingly automated systems is paradoxically human-centered: chat-first interfaces, community context pipelines, and accessibility to non-technical users as the primary litmus test.</li>\n<li>A federated protocol-based approach (Phase 4) enables members to run their own nodes and leave at any time, avoiding platform lock-in while maintaining collaborative shared models over open protocols.</li>\n<li>The model is being validated through Jacob's 84-unit housing co-op and tested for replication in other communities (Salmon Arm, Vancouver coworking spaces), suggesting broader applicability beyond tech communities.</li>\n</ul></div>\n<p>Source: <a href=\"https://protocol-institute.org/sigs/sigpfb/2026-09-07-community-scale-ai-protocols-infrastructure-and-local-s\">Protocol Institute meeting archive</a> · <a href=\"https://github.com/Protocol-Institute/website/blob/5f7307f90cb99ffe5f1dce580507dfdc8725769b/sigs/sigpfb/2026-09-07-community-scale-ai-protocols-infrastructure-and-local-s/index.html\">PI website commit 5f7307f</a> · <a href=\"https://pub-fb4a559f683a4e3b876823eb2bfe12a3.r2.dev/recordings/SIG-P4B/2026-09-07/1082444651946049567_1382801113224581240_1788795133956/summary.md\">raw recording notes</a>. Summarized by c3po, the Protocol Institute's session pipeline, from the session's Discord thread and recording.</p>",
 "content_hash": "sha256:ed2a36d036b4aa619e3b3aa89a78b0779e7bcde3c0628f22fe29a0b94d022ffa",
 "media": [],
 "transclusions": [],
 "generated": [
  {
   "sources": [],
   "model": "c3po (Protocol Institute session pipeline)",
   "at": "2026-09-27T04:43:37Z"
  }
 ],
 "changelog": [
  {
   "version": 1,
   "at": "2026-09-27T04:43:37Z",
   "note": "blyg: bootstrap session notes (10 sessions from PI archive) and research log with premises"
  }
 ]
}