Skip to content

Glossary ​

compute provider ​

The identity that executed one CI job and signed its Job Result. It may be the same key as the coordinator, as in ngit-ci today, or a separate key the coordinator delegated the job to.

coordinator ​

A Nostr CI service that watches repositories, matches workflow files to pushes and pull requests, applies policy and secrets, schedules jobs, and signs the progress and combined result events. Maintainers choose which coordinators to request; readers choose which to trust.

GRASP ​

Git Relays Authorised via Signed-Nostr Proofs: protocol profiles for Git hosting authorised and discovered through signed Nostr events.

GitNostr ​

The open ecosystem of clients and services that use Nostr protocols for Git collaboration. GitNostr is not one product suite, company, or required set of tools. See Grasp Awesome for current examples.

GitWorkshop ​

A browser client for NIP-34 collaboration and on-demand Git exploration. It is not a central repository host or source of truth.

maintainer ​

A Nostr identity participating in the repository's confirmed maintainer chain. Maintainer authority is derived from mutually signed repository announcements, not from matching an identifier alone.

Manual Trigger ​

A maintainer-signed, one-shot CI request naming a coordinator, a commit, and a workflow file by path and content hash. It needs no standing Service Request and can replay a workflow that declares no manual trigger.

naddr ​

A bech32-encoded address for a replaceable or addressable Nostr event. ngit accepts an naddr when explicitly selecting a repository with --repo.

nevent ​

A bech32-encoded Nostr event reference that can include useful relay and author hints. ngit's JSON output uses nevent1… for ids.

NIP-AD ​

A Nostr protocol proposal for mapping a familiar web address to a Nostr filter. ngit can resolve a repository address such as nostr://ngit.dev/ngit.git to its NIP-34 repository announcement.

NIP-34 ​

The Nostr protocol specification for Git collaboration events, including repository announcements, state, issues, and patch proposals.

Nostr relay ​

A server that accepts and serves signed Nostr events. Relays move repository state and collaboration; they do not replace Git object storage.

repository announcement ​

A signed addressable event describing a repository identifier, clone URLs, relays, maintainers, web URLs, and other metadata.

repository state ​

Signed ref state: which commits branches and tags point to, plus the repository's HEAD. Git objects remain in ordinary content-addressed Git storage.

runner ​

Software that executes a CI workflow format. act runs GitHub Actions-compatible files today; a coordinator advertises its runner families and the runs-on selectors it accepts, such as act:ubuntu-latest. A runner is not a Nostr identity.

Service Request ​

A maintainer-signed, standing instruction that one coordinator serve one repository perspective. It covers runs started after it and lasts until a Service Stop from the same perspective.

signer ​

Software or hardware that authorises Nostr events for an identity. ngit can use stored local credentials, one-shot protected files, or remote NIP-46 signers.

trust context ​

The evidence a client attaches to a CI signer: maintainer-directed, operationally associated, seen in your network, or no known context. It describes why a result may deserve attention; it does not change the result.

workflow ​

A file under .ngit/act/workflows/ that a coordinator executes. Every CI result names the workflow by path and by the SHA-256 of its content at the commit that ran.