GRASP protocol overview
GRASP, Git Relays Authorised via Signed-Nostr Proofs, is a protocol, not a server product. It defines how signed Nostr state can authorise Git hosting and how clients discover server capabilities.
Specification and implementation
graspowns the portable protocol specifications.ngit-graspis one implementation and owns its deployment, configuration, operations, monitoring, and internal architecture docs.ngitand GitWorkshop are clients that consume compatible services.
Keeping those boundaries visible prevents an implementation setting from being mistaken for a protocol requirement.
Profiles
| Profile | Role | Requirement |
|---|---|---|
| GRASP-01 | Core Git service authorised by signed repository state | Required |
| GRASP-02 | Proactive synchronisation | Optional |
| GRASP-03 | Proactive Sync Plus | Optional |
| GRASP-05 | Archive behaviour | Optional |
| GRASP-06 | Alternative pull request hosting | Optional |
| GRASP-08 | Private repository service | Optional |
The future gitgrasp.com protocol site should render the normative specification separately from operator explanations and mark requirement language clearly. ngit.dev keeps this concise protocol map beside the ngit-grasp operator guide.