app-development-with-cgs
Building apps on the Certified Group Service
You are an agent writing app code against a Certified Group Service (CGS) deployment. CGS puts role-based access control (owner / admin / member) in front of a single shared atproto account (the "group"), so several people can write to one repo without sharing its signing key.
This file is a router: it makes the first decision (which auth mode) and
points you at the one reference file for your task. Each reference file holds the
decisions and traps for its topic; the canonical request shapes live in the
repo's docs/ and are linked from there. Read the relevant reference file (and
the docs/ link it carries) before writing code — don't reconstruct request
shapes from memory.
Terminology (match it): "group service" (never "GPDS"), "group's PDS" (never "group PDS").