Bridge Architecture
Every bridge follows the same pattern:Available Bridges
Robotics & Physical AI
ROS2 Bridge
Package:
@sint/bridge-ros2Bridges SINT capability tokens to ROS2 (Robot Operating System 2). Wraps cmd_vel, joint commands, and sensor subscriptions with policy enforcement.- Control loop latency: P50 < 1ms, P95 < 2ms (benchmarked)
- Supports
geometry_msgs/Twist,sensor_msgs/JointState - Topic-level capability scoping
MAVLink Bridge
Package:
@sint/bridge-mavlinkConnects SINT to drone and UAV systems via the MAVLink protocol. Enforces geofence constraints, altitude limits, and velocity caps.- MAVLink v2 message framing
- GPS-based geofence enforcement
- Flight mode restriction via capability tokens
OpenRMF Bridge
Package:
@sint/bridge-open-rmfIntegration with Open-RMF (Robotics Middleware Framework) for multi-robot fleet management in facilities like hospitals, warehouses, and airports.- Fleet dispatch governance
- Zone-based access control
- Task priority enforcement
HAL Engine
Package:
@sint/engine-halHardware Abstraction Layer for direct actuator control. Provides a unified interface across motor controllers, servos, and sensor arrays.- Vendor-agnostic motor API
- Real-time constraint enforcement
- Sensor fusion support
Industrial Protocols
gRPC Bridge
Package:
@sint/bridge-grpcWraps gRPC service calls with capability token authentication. Supports unary, server-streaming, and bidirectional streaming RPCs.- 176+ lines of protobuf-driven integration
- Interceptor-based token injection
- Streaming policy enforcement
MQTT/Sparkplug Bridge
Package:
@sint/bridge-mqtt-sparkplugSparkplug B protocol adapter for SCADA and industrial IoT. Bridges SINT policy enforcement to MQTT-based control systems.- Sparkplug B topic namespace compliance
- Device/node birth/death tracking
- Metric-level access control
OPC-UA Bridge
Package:
@sint/bridge-opcuaOPC Unified Architecture adapter for industrial automation. Connects SINT to PLCs, SCADA systems, and manufacturing execution systems.- Node-level capability scoping
- Subscription-based monitoring with policy gating
- Historical data access governance
IoT Bridge
Package:
@sint/bridge-iotGeneric IoT device bridge for constrained environments. Supports lightweight protocols and device shadow patterns.- Device twin management
- Command-and-control with capability tokens
- Telemetry ingestion with policy filtering
AI & Agent Protocols
MCP Bridge
Package:
@sint/bridge-mcpModel Context Protocol adapter. Allows MCP-compliant AI agents to interact with SINT-governed resources. Tool calls are intercepted and policy-checked before execution.- MCP tool discovery with capability-scoped filtering
- Context preservation across tool calls
- Automatic evidence logging per tool invocation
A2A Bridge
Package:
@sint/bridge-a2aAgent-to-Agent protocol bridge (Google A2A). Enables secure inter-agent communication with capability token delegation.- Agent card registration and discovery
- Message routing with capability verification
- Task delegation across agent boundaries
Economy Bridge
Package:
@sint/bridge-economyMetered resource management. Tracks agent budgets, computes action costs, and enforces economic constraints.- Per-agent balance tracking
- Cost quoting before execution
- Budget enforcement with overdraft prevention
- Event stream for billing integration
Swarm Bridge
Package:
@sint/bridge-swarmMulti-agent swarm coordination. Manages consensus, task allocation, and collective decision-making for agent groups.- Swarm membership governance
- Consensus protocol with capability-weighted voting
- Task allocation with constraint propagation
Cognitive Engines
In addition to protocol bridges, SINT includes three cognitive engine packages:| Engine | Package | Purpose |
|---|---|---|
| System 1 | @sint/engine-system1 | Fast, reactive subsystem — handles real-time sensor responses and reflexive safety actions (sub-millisecond) |
| System 2 | @sint/engine-system2 | Deliberative planning subsystem — handles complex multi-step reasoning and plan generation |
| Capsule Sandbox | @sint/engine-capsule-sandbox | Isolated execution environment for untrusted agent code with syscall-level sandboxing |
Adding a New Bridge
All bridges implement the same interface pattern:Every bridge follows this exact pattern: intercept → check → log → forward. There are no “lightweight” or “bypass” modes. The evidence ledger captures every decision.
Gateway Server Endpoints
The bridge system is exposed through the gateway server’s unified API:| Bridge | Endpoint | Method |
|---|---|---|
| Core intercept | /v1/intercept | POST |
| Batch intercept | /v1/intercept/batch | POST |
| A2A messaging | /v1/a2a | POST |
| A2A agent registry | /v1/a2a/agents | GET, POST |
| Economy balance | /v1/economy/balance/:agentId | GET |
| Economy budget | /v1/economy/budget/:agentId | GET |
| Economy quote | /v1/economy/quote | POST |
| Economy routing | /v1/economy/route | POST |
| Risk stream | /v1/risk/stream | GET (SSE) |