CI interoperability

ngit and ngit-ci coordinate work through signed Nostr events, but the ecosystem does not yet publish a complete, implementation-independent CI protocol profile.

Not a specification

This page reserves the protocol boundary. It must not be treated as a normative contract or used to infer event shapes from the current implementation.

What is documented today

• Using CI with ngit covers contributor and maintainer workflows.
• Self-hosting ngit-ci covers the current coordinator and runner implementation.
• The generated ngit ci reference owns exact CLI syntax.
• NIP-34 and GRASP describe adjacent repository and hosting boundaries.

Those pages document shipped tools. They do not define what an independent CI coordinator must implement.

What a future profile must define

• request, progress, cancellation, and result event semantics;
• repository, revision, workflow, and coordinator identifiers;
• authorization and trust assertions;
• workflow-content and result-integrity binding;
• log and artifact discovery;
• replay, retry, expiry, and idempotency behaviour; and
• compatibility and version negotiation.

Until that profile is reviewed and published, ngit-ci behaviour remains an implementation contract rather than a general protocol promise.