Get on the allowlist, then bring up the suite in dependency order.

Step 1 — Request access

Email info@bitlemmas.com with the subject “Community Infra repo allowlist”. Include:

• Your Radicle DID (run rad self --did on a machine where rad auth has been initialised).
• Which projects you want access to (the four listed below, or a subset).
• A short note on what you intend to do with it (run a seed, operate a runner, follow along).

Once your DID is on the allowlist for a given repo, the seed will gossip it to your machine on the next rad sync.

Step 2 — Bring up the suite in dependency order

The architecture page has the full graph; here are the concrete commands in the order most operators run them. Each project ships its own README with deeper detail once you have it cloned.

1. radicle-seed-kit — bring up the seed first

   Without a healthy seed, the other projects cannot replicate. Seed Kit ships the DigitalOcean automation and the friend-onboarding flow; the README walks through both.

   rad clone <rid> radicle-seed-kit
   cd radicle-seed-kit
   cat README.md
   # follow RADICLE_DO_SEED.md to provision the seed,
   # then RADICLE_SEED_ONBOARDING.md to mirror your repos to it.

2. radicle-priorities — the canonical backlog protocol

   Adopt the backlog protocol so the rest of the suite’s scenarios are visible in one place. The methodology site at extremebdd.com has the walkthrough video; the repo holds the board server.

   rad clone <rid> radicle-priorities
   cd radicle-priorities
   python3 scripts/board_server.py --repo .
   # open http://127.0.0.1:8844/

3. poor-mans-ci — runner + attestations

   Stand up the runner host. PMCI 0.4 ships with commit-addressed checkouts, pinned runner images, and the artifact mirror by default. Run it against your canonical Radicle ref to start producing attestations on every commit.

   rad clone <rid> poor-mans-ci
   cd poor-mans-ci
   cat docs/PMCI_PROTOCOL.md
   # wire your runner per docs/ARCHITECTURE__END_TO_END.md

4. poor-mans-cd — release manifests + deploy host

   Bring PMCI evidence into a deploy plane. The PMCD dashboard reads PMCI attestations and gates promotion. The deploy itself is manifest-driven and hash-verified.

   rad clone <rid> poor-mans-cd
   cd poor-mans-cd
   python3 -m pmcd --help
   # walk through docs/ARCHITECTURE.md and docs/DO_RUNNER_DASHBOARD_PROVISION.md

Verifying the install end-to-end

Once the four are up, the standing smoke test is:

1. Open a Radicle issue from one peer.

   Use Radicle Priorities to land the issue with a @pending BDD scenario referencing it.

2. Gossip the change through the seed.

   rad sync from the originator. The seed kit’s scheduled timers should mirror within a minute.

3. Trigger a PMCI build on the runner.

   Confirm an attestation lands in pmci-out/ and the artifact mirror serves the sha256.

4. Promote a PMCD release manifest.

   Confirm the deploy host installs only when the sha256 matches and writes a receipt to /var/lib/pmcd/receipts/.

If all four steps succeed without touching a hosted CI provider, a central forge, or a SaaS dashboard, the suite is doing its job.