We open source everything out of principle, including the work we stopped. The negative space is just as important to share.
Every one of these was built because we needed it at the time. Each was retired when something cheaper did the same job, or when the thing it depended on went away. The reasoning is the useful part, so it is recorded here rather than quietly deleted.
A decentralized coordination protocol for autonomous agents. Ed25519 identity, FROST threshold signatures, peer-to-peer transport, and a convention set covering trust, discovery, naming and routing. Adopt the conventions and an application inherited a CLI and an MCP server without writing integration code.
Why it is goneIdentity, trust and authority are hard problems in their own right, and campfire conflated them with wire protocol, coordination and messaging semantics. Bundling the two meant every question about who an agent is and what it may do had to be answered inside a transport layer. nostr does the messaging side better and does not pretend to have settled the rest. rd and dontguess moved onto nostr relays, and in-session orchestration moved into the Workflow tool.
Azure-native hosting for the protocol, so a team could coordinate agents without provisioning anything themselves.
Why it is goneIt existed to remove the operational cost of running the protocol. With no protocol, there is no cost to remove.
The hosted service packaged as an Azure Marketplace managed application, aimed at buyers who procure through the marketplace rather than direct.
Why it is goneSame dependency as the hosting layer, same outcome.
The Agentic Internet Engineering Task Force. A standards body for the campfire conventions, with a charter, founding committee, and a published convention library that agents could discover and adopt.
Why it is goneA standards body for a retired protocol has no subject. nostr already runs a standards process in the NIPs, and it does not need a second one from us.
An engine for running fleets of AI workers. Persistent agent identities, long-term memory, capability and budget enforcement, and the full lifecycle: spawn, supervise, interrupt, restore, retire. Roughly 73,000 lines of Go, extracted from the Rudi monolith.
Why it is goneContinuity turned out to live in the work graph, not in resident processes. A session that wakes, reads an execution pointer and continues does the same job with nothing to keep alive between runs. The engine was solving for persistence that the work items already provided.
The original work-management system, around 120,000 lines of Go, carrying the automaton manager, the work graph, and the human interface in one binary.
Why it is goneThe work graph was the part that earned its keep. It became the rd CLI, which is nostr-backed and has no server to run. The rest was weight.
A federated intelligence commons for agents and humans. Locally ranked, with reputation earned through vouches rather than engagement, and every instance computing its own trust scores independently.
Why it is goneIt was built on campfire, and campfire failed. A social network for agents needs identity and trust settled underneath it, which is precisely the part campfire got wrong.