Skip to main content
SINT Protocol is open source under Apache-2.0. The specification is open under CC BY 4.0. Contributions are welcome.

​
Ways to contribute

Spec clarifications

Find an ambiguity in the protocol spec? Open a PR or file a SIP.

Bridge implementations

Implement a transport bridge for a protocol we don’t yet cover. See bridges for the Bridge interface.

SDK ports

Port the SDK to a new language. SDKs follow the coverage matrix.

Conformance tests

Add regression tests against known physical-AI incidents. See conformance suite.

Documentation

Fix typos, clarify prose, add examples. Docs live in docs/ and on docs.sint.gg.

Research

Empirical safety studies, formal-methods work, academic papers citing SINT — we read and respond to everything.

​
Contribution workflow

1

Open an issue first (for substantive changes)

For anything larger than a typo fix, open an issue before coding. We’ll confirm the direction, surface related work, and save you time.
2

Fork and branch

Fork sint-ai/sint-protocol and create a feature branch.
3

Write tests

Every change needs tests. No PR without a red-green-refactor loop is merged.
4

Run the suite

pnpm run test locally. CI runs the full 1,772-test suite on every PR.
5

Sign your commits

Use git commit -s (DCO, not CLA). We accept commits signed under the Developer Certificate of Origin.
6

Open the PR

Include a clear description, link to the issue, and a short impact statement (breaking change? performance regression? new dependency?).

​
Coding standards

  • TypeScript 5.7, strict mode. No any. No @ts-ignore without a justifying comment.
  • Result<T, E> over exceptions for fallible operations. See the repo’s existing error-handling patterns.
  • Tests colocated with code. foo.ts → foo.test.ts in the same directory.
  • No new dependencies without discussion. We aim for minimal dependencies; a heavyweight library has to earn its place.

​
SIP process

Substantive changes to the specification follow the SINT Improvement Proposal process:
  1. Open a SIP issue using the template in docs/SIPS.md
  2. Discuss in the issue; revise until stable
  3. PR the spec change alongside the SIP
  4. Merge requires approval from at least two existing maintainers

​
Security

Security-sensitive contributions (auth, crypto, attestation) require additional review. Please coordinate with maintainers before opening a PR touching these areas. Report vulnerabilities privately — see security policy.

​
Steering committee

A steering committee is forming in Q2 2026. It will govern SIP acceptance, release cadence, and maintainer appointments. If you have standing in robotics security, agent identity, or industrial compliance and want to participate, write to [email protected].

​
Recognition

Contributors are listed in CONTRIBUTORS.md. Substantial contributors get a did:sint:contributor:* identity and an entry in the certification bundle metadata.

​
Code of conduct

We follow the Contributor Covenant 2.1. Behavior that makes contribution unwelcoming is not acceptable regardless of technical contribution.

​
Questions