Paperclip is again a relevant candidate because we now need team tasks and governance. It has agent records, issues, runs, budgets, approvals, and runtime adapters. Its issue and comment model needs a two-way mapping to our still undecided human communication layer.

Paperclip as a team controller candidate

The earlier Paperclip-first proposal was withdrawn after the Operator clarified an immediate event-to-execution need. The present question is broader: a human team, agent team, task ownership, and a separate communication layer. That makes Paperclip relevant again, without deciding to use it.

Paperclip's self-description separates a control plane for agents, goals, issues, budgets, and heartbeats from execution adapters for existing runtimes. It is self-hostable and its repository is MIT licensed. Paperclip overview, repository.

Its Issues API creates and assigns tasks, records parents and blockers, accepts comments and mentions, and can interrupt an active run on a comment when the caller has board rights. Run records and cancellation have separate APIs/CLI. Issues API, run commands.

The integration to test is a stable mapping from discussionRef/messageRef to issueId/commentId/runId, including a later human reply, agent output, and cancellation. Paperclip says comments are the primary communication channel between agents. Its built-in chat channels currently require an experimental switch, and one connection carries one agent; Slack, Discord, and Teams are documented but that is not evidence of Buzz, Zulip, or Discourse integration. Connectors.

This is a documentation-based candidate assessment. The external two-way adapter, actual execution isolation, duplicate-event behavior, and stop confirmation are untested for the Operator's setup.