ClipHub is the public registry where people share, discover, and download Paperclip company configurations. A company template is a portable artifact containing an entire org — agents, reporting structure, adapter configs, role definitions, seed tasks — ready to spin up with one command.
ClipHub is to Paperclip what a package registry is to a programming language. Paperclip already supports exportable org configs (see [SPEC.md](./SPEC.md) §2). ClipHub is the public directory where those exports live.
A user builds a working company in Paperclip — a dev shop, a marketing agency, a research lab, a content studio — exports the template, and publishes it to ClipHub. Anyone can browse, search, download, and spin up that company on their own Paperclip instance.
The tagline: **you can literally download a company.**
---
## What Gets Published
A ClipHub package is a **company template export** — the portable artifact format defined in the Paperclip spec. It contains:
- **Popular** — ranked by downloads, stars, and forks
- **Recent** — latest published or updated
- **Categories** — browseable by use case (see Categories below)
Each listing shows: name, short description, org size (agent count), category, adapter types used, star count, download count, and a mini org chart preview.
### Search
Search is **semantic, not keyword-only.** Powered by vector embeddings so you can search by intent:
- "marketing agency that runs facebook ads" → finds relevant company templates even if those exact words aren't in the title
- "small dev team for building APIs" → finds lean engineering orgs
- "content pipeline with writers and editors" → finds content studio templates
Also supports filtering by: category, agent count range, adapter types, star count, recency.
### Company Detail Page
Clicking into a company template shows:
- **Full description** — what this company does, how it operates, what to expect
- **Interactive org chart** — visual tree of every agent with role, title, and capabilities
- **Agent list** — expandable details for each agent (adapter type, config summary, role description)
- **Seed tasks** — the starter initiatives and tasks included
- **Budget overview** — suggested cost structure
- **Install command** — one-line CLI command to download and create
- **Version history** — changelog, semver, previous versions available
Downloads the template and creates a new company in your local Paperclip instance. You add your own API keys, set budgets, customize agents, and hit go.
**Fork:**
Forking creates a copy of the template under your own ClipHub account. You can modify it, republish it as your own variant, and the fork lineage is tracked. This enables evolutionary improvement — someone publishes a marketing agency, you fork it, add a social media team, republish.
### Stars & Comments
- **Stars** — bookmark and signal quality. Star count is a primary ranking signal.
- **Comments** — threaded discussion on each listing. Ask questions, share results, suggest improvements.
### Download Counts & Signals
Every install is counted. The registry tracks:
- Total downloads (all time)
- Downloads per version
- Fork count
- Star count
These signals feed into search ranking and discovery.
---
## Publishing
### Who Can Publish
Anyone with a GitHub account can publish to ClipHub. Authentication is via GitHub OAuth.
### How to Publish
From within Paperclip, export your company as a template, then publish:
```
paperclip export --template my-company
paperclip publish cliphub my-company
```
Or use the web UI to upload a template export directly.
| `description` | yes | What this company does and who it's for |
| `category` | yes | Primary category (see below) |
| `tags` | no | Additional tags for discovery |
| `version` | yes | Semver (e.g. `1.0.0`) |
| `changelog` | no | What changed in this version |
| `readme` | no | Extended documentation (markdown) |
| `license` | no | Usage terms |
### Versioning
Templates use semantic versioning. Each publish creates an immutable version. Users can install any version or default to `latest`. Version history and changelogs are visible on the detail page.
### The `sync` Command
For power users who maintain multiple templates:
```
paperclip cliphub sync
```
Scans your local exported templates and publishes any that are new or updated. Useful for maintaining a portfolio of company templates from a single repo.
---
## Categories
Company templates are organized by use case:
| Category | Examples |
|---|---|
| **Software Development** | Full-stack dev shop, API development team, mobile app studio |
Categories are not exclusive — a template can have one primary category plus tags for cross-cutting concerns.
---
## Moderation & Trust
### Verified Publishers
Publishers who meet certain thresholds (account age, published templates with good signals) earn a verified badge. Verified templates rank higher in search.
### Security Review
Company templates contain adapter configurations, which may include executable commands (process adapter) or webhook URLs (HTTP adapter). The moderation system:
4. Assign it to a manager in your existing company
5. Done
---
## Relationship to Paperclip
ClipHub is **not required** to use Paperclip. You can build companies entirely from scratch without ever touching ClipHub. But ClipHub dramatically lowers the barrier to entry:
- **New users** get a working company in minutes instead of hours
- **Experienced users** share proven configurations with the community
- **The ecosystem** compounds — every good template makes the next company easier to build
ClipHub is to Paperclip what a package registry is to a language runtime: optional, but transformative.
---
## V1 Scope
### Must Have
- [ ] Template publishing (upload via CLI or web)
- [ ] Template browsing (list, filter by category)
