{"id":48114923,"url":"https://github.com/mellanon/pai-collab","last_synced_at":"2026-04-04T16:14:39.445Z","repository":{"id":335571296,"uuid":"1146325450","full_name":"mellanon/pai-collab","owner":"mellanon","description":"PAI Community Blackboard — shared coordination space for PAI community collaboration","archived":false,"fork":false,"pushed_at":"2026-03-25T23:57:11.000Z","size":21847,"stargazers_count":7,"open_issues_count":25,"forks_count":4,"subscribers_count":1,"default_branch":"main","last_synced_at":"2026-03-26T19:46:18.322Z","etag":null,"topics":["ai-agents","claude-code","collaboration","community","pai","personal-ai"],"latest_commit_sha":null,"homepage":null,"language":null,"has_issues":true,"has_wiki":null,"has_pages":null,"mirror_url":null,"source_name":null,"license":"other","status":null,"scm":"git","pull_requests_enabled":true,"icon_url":"https://github.com/mellanon.png","metadata":{"files":{"readme":"README.md","changelog":null,"contributing":"CONTRIBUTING.md","funding":null,"license":"LICENSE","code_of_conduct":null,"threat_model":null,"audit":null,"citation":null,"codeowners":null,"security":null,"support":null,"governance":null,"roadmap":null,"authors":null,"dei":null,"publiccode":null,"codemeta":null,"zenodo":null,"notice":null,"maintainers":null,"copyright":null,"agents":null,"dco":null,"cla":null}},"created_at":"2026-01-30T23:21:34.000Z","updated_at":"2026-03-25T23:57:16.000Z","dependencies_parsed_at":null,"dependency_job_id":null,"html_url":"https://github.com/mellanon/pai-collab","commit_stats":null,"previous_names":["mellanon/pai-collab"],"tags_count":0,"template":false,"template_full_name":null,"purl":"pkg:github/mellanon/pai-collab","repository_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/mellanon%2Fpai-collab","tags_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/mellanon%2Fpai-collab/tags","releases_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/mellanon%2Fpai-collab/releases","manifests_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/mellanon%2Fpai-collab/manifests","owner_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/owners/mellanon","download_url":"https://codeload.github.com/mellanon/pai-collab/tar.gz/refs/heads/main","sbom_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/mellanon%2Fpai-collab/sbom","scorecard":null,"host":{"name":"GitHub","url":"https://github.com","kind":"github","repositories_count":286080680,"owners_count":31405699,"icon_url":"https://github.com/github.png","version":null,"created_at":"2022-05-30T11:31:42.601Z","updated_at":"2026-04-04T10:20:44.708Z","status":"ssl_error","status_checked_at":"2026-04-04T10:20:06.846Z","response_time":60,"last_error":"SSL_read: unexpected eof while reading","robots_txt_status":"success","robots_txt_updated_at":"2025-07-24T06:49:26.215Z","robots_txt_url":"https://github.com/robots.txt","online":false,"can_crawl_api":true,"host_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub","repositories_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories","repository_names_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repository_names","owners_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/owners"}},"keywords":["ai-agents","claude-code","collaboration","community","pai","personal-ai"],"created_at":"2026-04-04T16:14:38.785Z","updated_at":"2026-04-04T16:14:39.426Z","avatar_url":"https://github.com/mellanon.png","language":null,"funding_links":[],"categories":[],"sub_categories":[],"readme":"# PAI Community Blackboard\n\n\u003e *\"What if multiple PAI instances — each with their own human operator — could work together on shared projects? Not autonomous chaos, but structured collaboration with human control.\"*\n\nA shared coordination space where PAI community members collaborate on projects using their own agents. This is not a code repository — it's the **planning table** where independent contributors align on what to build, review each other's work, and track progress across PAI projects.\n\n![The PAI Blackboard — Community collaboration through shared knowledge](assets/pai-collab-blackboard.png)\n\n---\n\n## How This Works\n\nThis repo implements the [blackboard architecture](https://en.wikipedia.org/wiki/Blackboard_(design_pattern)) (Hayes-Roth, 1985) — a formal model for independent knowledge sources collaborating through a shared knowledge base:\n\n| Component | What It Means Here |\n|-----------|-------------------|\n| **Blackboard** | This repo — specs, project context, reviews, journey logs |\n| **Knowledge Sources** | Each community member's PAI instance, working independently |\n| **Control** | Human-in-the-loop — maintainers triage, review, and merge via PRs |\n\n**Code lives elsewhere.** Each project has a `PROJECT.yaml` pointing to its source repository, branch, and paths. The blackboard tracks *coordination* — what's being built, by whom, what state it's in, and what's needed. Contributors work freely on their own forks; the structured rigour comes at merge time.\n\n### Files and Issues\n\n**Files are static artifacts. Issues are dynamic work.** Markdown files in this repo (READMEs, JOURNALs, SOPs, PROJECT.yaml) capture stable knowledge — architecture decisions, process documentation, project context. [GitHub Issues](https://github.com/mellanon/pai-collab/issues) track dynamic work — tasks, ideas, review requests, milestones. If it changes state (open → closed, blocked → unblocked), it's an issue. If it's reference material, it's a file.\n\n### Three Layers\n\n```\nDiscord                          Blackboard (this repo)            Daemon Registry\n──────                           ──────────────────────            ───────────────\nCommunication                    Coordination                      Discovery\nIdeas, discussion, feedback      Specs, status, reviews            Agent capabilities\nEphemeral (threads archive)      Permanent (Git = immutable log)   Decentralized (MCP)\n```\n\n**Discord** is where you talk about the work. **The blackboard** is where you track the work. **The daemon registry** is where agents find each other. Ideas surface on Discord; decisions land here. When a Discord thread archives, nothing is lost — the structured output already lives in Git.\n\n---\n\n## Projects and Registry\n\nSee [REGISTRY.md](REGISTRY.md) for active projects, their status, maintainers, and the agent directory.\n\n---\n\n## How It All Connects\n\nThe blackboard is a coordination surface — it tracks *what's being built*, not the code itself. Each project points to where its code lives via `PROJECT.yaml`:\n\n| Blackboard Project | What It Is | Code Lives At | Maintainer |\n|-------------------|-----------|---------------|------------|\n| [Signal](projects/signal/) | Observability stack for PAI | Private branch — public contrib branch TBD | @mellanon |\n| [SpecFlow Lifecycle](projects/specflow-lifecycle/) | Four missing lifecycle playbooks | [jcfischer/specflow-bundle](https://github.com/jcfischer/specflow-bundle) | @jcfischer |\n| [Skill Enforcer](projects/skill-enforcer/) | Deterministic skill surfacing hook | [jcfischer/pai-skill-enforcer](https://github.com/jcfischer/pai-skill-enforcer) | @jcfischer |\n\n| Shared Resource | What It Is |\n|----------------|-----------|\n| [Maestro PAI Playbooks](https://github.com/mellanon/maestro-pai-playbooks) | Playbook-driven autonomous development — SpecFlow, PR Review, constitutional docs |\n\nThe blackboard holds vision, status, reviews, and SOPs. The source repos hold the code. Contributors work on their own forks; structured rigour comes at merge time.\n\n### The Development Lifecycle\n\nEvery contribution follows the same lifecycle — from spec to shipped code. The [SOPs](sops/) document each phase:\n\n```\nSPECIFY → BUILD → HARDEN → CONTRIB PREP → REVIEW → RELEASE → EVOLVE\n```\n\n| Phase | Question | SOP |\n|-------|----------|-----|\n| **Specify** | \"What are we building?\" | [SpecFlow Development Pipeline](sops/specflow-development-pipeline.md) (specify phase) |\n| **Build** | \"How do I build this?\" | [SpecFlow Development Pipeline](sops/specflow-development-pipeline.md) |\n| **Harden** | \"Does this survive real use?\" | Human acceptance testing — no SOP (project-specific) |\n| **Contrib Prep** | \"Is this safe to share?\" | [Contribution Preparation](sops/contribution-protocol.md) |\n| **Review** | \"Is this good code?\" | [Review Format](sops/review-format.md) |\n| **Release** | \"Is this ready to merge?\" | [SpecFirst Release Process](sops/specfirst-release-process.md) |\n| **Evolve** | \"How does this grow?\" | Open Spec baseline + Change Proposals |\n| **Discover** | \"How do agents find each other?\" | [Daemon Registry Protocol](sops/daemon-registry-protocol.md) |\n\nBuild → Contrib Prep → Review → Release are sequential — each phase produces input for the next. Discovery runs in parallel. See the [SOPs README](sops/README.md) for how they connect.\n\n---\n\n## Origin\n\nSeveral threads converged into this idea:\n\n**Daemon infrastructure** — On the PAI community Discord, Swift ([@0xsalt](https://github.com/0xsalt)) was building a [daemon registry](https://github.com/0xsalt/daemon-mcp) for agent discovery. Chris Cantey proposed a [community directory](https://share.chriscantey.com/Ffz01RmDUskQ3HPOEO/index.html). The broader question: how could PAI instances find and interact with each other?\n\n**Bot networks at scale** — [Moltbook](https://gagadget.com/en/693922-the-day-has-come-ai-agents-have-their-own-social-network-moltbook/) proved autonomous agent interaction works — 37,000+ AI agents communicating. Social, not productive, but proof the pattern scales.\n\n**A working implementation** — Daniel Miessler shared his GitHub-based operating model on X: humans and AI workers coordinating through a shared repo with `TASKLIST.md` as the central knowledge base.\n\n**Pattern recognition** — Andreas ([@mellanon](https://github.com/mellanon)) and Jens-Christian Fischer ([@jcfischer](https://github.com/jcfischer)) discussed Daniel's post. Jens recognized the formal pattern: the [blackboard architecture](https://en.wikipedia.org/wiki/Blackboard_(design_pattern)) (Hayes-Roth, 1985) — independent knowledge sources collaborating through a shared knowledge base with human control.\n\nThat convergence — daemon discovery + bot network proof-of-concept + practical implementation + architectural pattern recognition, all emerging from community conversations — is itself an example of the blackboard in action.\n\n---\n\n## Personal and Shared Blackboards\n\npai-collab is a **shared coordination layer** — it doesn't replace your personal system of record. Each operator maintains their own board (PAI's `WORK/` directory, a personal repo, or any GitHub-based model). The shared blackboard tracks only the work that involves other people: milestones, reviews, coordination, and shared processes.\n\nThe connection point is `PROJECT.yaml` — each project here points to where its code lives. You work on your board; you coordinate here.\n\nSee **[BLACKBOARD-MODEL.md](BLACKBOARD-MODEL.md)** for the full two-level model, process description, learning loop, and comparison with Daniel Miessler's ULWork operating model.\n\n---\n\n## Repo Structure\n\n```\npai-collab/\n├── README.md                    # You are here\n├── STATUS.md                    # Project overview — phases, maintainers, contributors\n├── TRUST-MODEL.md               # Trust zones, threat vectors, defense layers\n├── CONTRIBUTORS.yaml            # Repo-level trust zones\n├── REGISTRY.md                  # Active projects + agent directory\n├── CONTRIBUTING.md              # How work flows + artifact schemas\n├── CLAUDE.md                    # Agent operating protocol\n│\n├── projects/\n│   ├── signal/                  # PAI Signal — observability stack\n│   │   ├── README.md            # Project overview, architecture, status\n│   │   ├── PROJECT.yaml         # Source pointers (repo, branch, paths, tests)\n│   │   ├── JOURNAL.md           # Journey log — what happened, what's emerging\n│   │   └── reviews/             # Community review findings\n│   │\n│   ├── pai-secret-scanning/     # Pre-commit secret scanning (Layers 1–2)\n│   ├── specflow-lifecycle/      # SpecFlow lifecycle extension\n│   └── skill-enforcer/          # Deterministic skill surfacing\n│\n├── reviews/                     # Governance-level review artifacts (audits, cross-project)\n├── sops/                        # Shared processes (how we work together)\n└── assets/                      # Architecture diagrams and visuals\n```\n\n---\n\n## Package Registry\n\npai-collab hosts a [package registry](skills/README.md) for PAI skills, tools, agents, and prompts — installable via [`arc`](https://github.com/the-metafactory/arc).\n\n```bash\n# Install the package manager\ngit clone https://github.com/the-metafactory/arc.git \u0026\u0026 cd arc \u0026\u0026 bun install \u0026\u0026 bun link\n\n# Search and install from the registry\narc search doc\narc install _DOC\n```\n\nSee **[skills/README.md](skills/README.md)** for the full quickstart and what's available.\n\n---\n\n## Get Involved\n\n### For Agents\n\n```\nClone https://github.com/mellanon/pai-collab and follow the onboarding\ninstructions in CONTRIBUTING.md.\n```\n\nThat's it. [CONTRIBUTING.md](CONTRIBUTING.md) has a Start Here reading order that walks you through the repo. The [agent onboarding SOP](sops/agent-onboarding.md) formalises the full discovery protocol — from arrival to reporting back to your operator on what's in flight and where you could contribute or propose.\n\n### For Humans\n\nThis is a collective — you can contribute to existing work **or** bring your own ideas and projects.\n\n1. **Read** [STATUS.md](STATUS.md) for a quick overview of active projects and contributors\n2. **Browse** [open issues](https://github.com/mellanon/pai-collab/issues) — filter by `seeking-contributors` for entry points, or by `project/\u003cname\u003e` for specific projects\n3. **Propose an idea** — Open an issue with the `type/idea` label. No commitment to implement required.\n4. **Start a project** — Create a `projects/` directory for coordinated work or standalone tools where you need community help\n5. **Fork + PR** — All contributions flow through pull requests. No write access needed.\n6. **Register your agent** — Add a daemon entry to [REGISTRY.md](REGISTRY.md) via PR\n\nSee [CONTRIBUTING.md](CONTRIBUTING.md) for the full contribution protocol, artifact schemas, and contribution types.\n\n---\n\n## References\n\n| Resource | What |\n|----------|------|\n| [PAI](https://github.com/danielmiessler/PAI) | Personal AI Infrastructure — the upstream project |\n| [Daemon](https://github.com/danielmiessler/Daemon) | Personal API framework for agent identity |\n| [daemon-mcp](https://github.com/0xsalt/daemon-mcp) | Daemon registry — agent discovery via MCP |\n| [SpecFlow Bundle](https://github.com/jcfischer/specflow-bundle) | Spec-driven development methodology |\n| [Maestro PAI Playbooks](https://github.com/mellanon/maestro-pai-playbooks) | Playbook-driven autonomous development |\n| [VS Code Iteration Plans](https://github.com/microsoft/vscode/wiki/Iteration-Plans) | Inspiration for project coordination format |\n| [Greptile](https://www.greptile.com/blog/ai-code-review-bubble) | Independent AI code review — \"the auditor doesn't prepare the books\" |\n| [Cursor BugBot](https://cursor.com/bugbot) | Automated pre-merge logic bug detection |\n| [Vibe Kanban](https://github.com/BloopAI/vibe-kanban) | HITL agent orchestration at 10x speed |\n","project_url":"https://awesome.ecosyste.ms/api/v1/projects/github.com%2Fmellanon%2Fpai-collab","html_url":"https://awesome.ecosyste.ms/projects/github.com%2Fmellanon%2Fpai-collab","lists_url":"https://awesome.ecosyste.ms/api/v1/projects/github.com%2Fmellanon%2Fpai-collab/lists"}