Thank you for helping make physical AI safer.
New bridge = new protocol integration. See packages/bridge-iot/ as a minimal template.
High-value bridges not yet built:
- PROFINET / EtherCAT / CANopen / Modbus TCP (industrial fieldbus)
- DDS / RTPS (ROS 2 native transport layer)
- MQTT 5 with shared subscriptions (fleet telemetry)
- WebRTC data channels (browser-based operator consoles)
Each bridge needs:
src/<protocol>-resource-mapper.ts— URI + action mappingsrc/<protocol>-interceptor.ts— session + intercept logic__tests__/<protocol>.test.ts— ≥15 tests covering allow/deny/escalate paths
Every new security invariant needs a test in packages/conformance-tests/src/.
Canonical fixtures (JSON) live in packages/conformance-tests/fixtures/.
Use the bridge conformance issue template to report results.
| Language | Status | Issue |
|---|---|---|
| TypeScript | ✅ sdks/typescript/ |
— |
| Python | stub at sdks/python/ |
#4 |
| Go | stub at sdks/go/ |
— |
| Rust | not started | open an issue |
See SECURITY.md.
See docs/SIPS.md and use the template at docs/sips/0000-template.md.
git clone https://github.com/pshkv/sint-protocol
cd sint-protocol
pnpm install
pnpm run build
pnpm run test # Must be 0 failures before and after your changeNode.js ≥ 22 and pnpm ≥ 9.15 required.
pnpm run build— zero TypeScript errorspnpm run test— all 1,105+ existing tests pass- New functionality has unit tests in its own package
- New security-relevant behaviour has a test in
@sint/conformance-tests - New bridge adapter exports types from its
src/index.ts
- TypeScript strict mode —
noUncheckedIndexedAccess,noUnusedLocals Result<T, E>pattern — never throw for control flow; useok()/err()from@sint/core- Readonly interfaces by default
- Zod schemas at system boundaries (external input, API surface)
@noble/ed25519for all Ed25519 operations (audited, zero-dep)- UUID v7 for all IDs — use
generateUUIDv7()from@sint/gate-capability-tokens, nevercrypto.randomUUID()(that gives v4)
This repo is designed for parallel human + AI development. See AGENTS.md for AI-specific guidance and CLAUDE.md for implementation details and common pitfalls.
Package ownership by focus area (to avoid conflicts):
| Area | Packages |
|---|---|
| Security core | @sint/core, @sint/gate-* |
| Bridges | @sint/bridge-* — each is independent |
| Engine | @sint/engine-* |
| Server / client | @sint/gateway-server, @sint/client |
| Conformance | @sint/conformance-tests |
Open an issue or comment on an existing one. For real-time discussion, reference the A2A #1713 thread where SINT and APS are coordinating on joint physical AI governance.