Skip to main content
SINT OS is what happens when you combine OpenClaw (the agent runtime), SINT Protocol (the governance engine), SINT Avatar (the face), and multimodal AI (the senses) into a single operating system for autonomous agents. SINT OS is not a separate product. It’s the integration layer. Each component already exists and runs independently. SINT OS makes them work as one system.

​
Architecture

┌─────────────────────────────────────────────────────────────┐
│                         SINT OS                              │
│                                                              │
│  Face (Avatar) · Brain (Console) · Hands (Operators) ·       │
│                  Content (CMO Operator)                       │
│                          │                                    │
│          @sint/os-core (Orchestrator)                        │
│          Boot → Govern → React → Evidence                    │
│                          │                                    │
│     OpenClaw Adapter · SINT Protocol · Evidence HUD          │
│                          │                                    │
│              SINT Protocol Core                              │
│  Tokens · Policy Gateway · Evidence Ledger · 12 bridges      │
│                          │                                    │
│              OpenClaw Runtime                                 │
│  WS gateway · channels · MCP router · sessions · sandbox     │
└─────────────────────────────────────────────────────────────┘

​
Core packages

@sint/os-core

Main entrypoint. Boots all components, orchestrates governance, connects avatar reactions to policy events.

@sint/openclaw-adapter

The governance choke-point for OpenClaw. Every tool call passes through here before execution.

@sint/integration-langchain

LangChain callback handler and tool wrapper. SINT governance for LangChain agents.

​
Boot sequence

import { SintOS } from "@sint/os-core";

const os = new SintOS({
  gatewayUrl:    "http://localhost:4100",
  agentId:       "did:key:z6MkExample",
  openclawWsUrl: "ws://127.0.0.1:18789",
  avatar:        { serverUrl: "http://localhost:3005" },
  evidenceHud:   { enabled: true },
  crossSystemPolicies: DEFAULT_PHYSICAL_POLICIES
});

await os.boot();
boot() does:
1

Connect to SINT Protocol gateway

Verifies health, registers this OS instance as a client.
2

Initialize OpenClaw adapter

Maps all registered tools to T0–T3 tiers via the tier classifier.
3

Connect to Avatar server

Verifies the 3D face is running; subscribes to expression and animation updates.
4

Start Evidence HUD

Opens the real-time ledger stream.
5

Activate cross-system policy engine

Loads the default plus custom cross-system policies.

​
Tier classification

Every OpenClaw tool, MCP server, and node action is classified into a safety tier.
TierDescriptionOpenClaw examples
T0Observe onlyread, web_search, web_fetch, memory_search, session_status
T1Reversible digitalwrite, edit
T2Requires governancemessage.send, tts, image_generate, sessions_spawn, exec (non-elevated)
T3Physical / irreversibleexec (elevated), canvas.eval, nodes.invoke
T0 calls never hit the network. They’re approved locally in microseconds. Governance adds zero latency to read operations.

​
Cross-system policies

These policies span multiple subsystems — no single-protocol safety system can enforce them.
PolicyWhen activeDeniesWhy
no-fs-while-movingrobot.movingFile writesPrevents controller corruption during motion
no-exec-while-movingrobot.movingShell executionPrevents control-loop interference
no-deploy-while-activecmd_velDeploysCan’t restart while velocity commands active
no-network-while-armeddrone.armedNetwork, execSafety-critical — no external access while armed
// Activate a system state
adapter.getStateTracker().activate("robot.moving");

// File writes now automatically denied
const result = await adapter.governToolCall({
  tool:   "write",
  params: { path: "/robot/config.yaml" }
});
// result.allowed === false
// result.reason === "[Cross-System Policy: no-fs-while-moving] ..."
Custom policies: 
const os = new SintOS({
  crossSystemPolicies: [
    {
      name:        "no-reboot-during-surgery",
      whenActive:  "patient.connected",
      denyActions: ["system:reboot*", "deploy:*"],
      reason:      "Cannot disrupt systems during active patient monitoring"
    }
  ]
});

​
Avatar reactions

Governance events route to visual avatar reactions.
EventExpressionAnimationWidget
T0 approvedefault——
T1 approvedefaultHead-Nod-YesStatus (3s)
T2 denythinkingThoughtful-Head-ShakeStatus (8s)
T3 escalatesurprisedThinkingApproval action (30s)

​
Evidence HUD

Real-time viewer of the SHA-256 evidence ledger. Rolling window of governance decisions with chain-integrity verification. 
const hud = os.getEvidenceHUD();
hud.onEntry((entry) => {
  console.log(`${entry.tier} ${entry.outcome}: ${entry.resource}`);
});

const { valid, brokenAt } = hud.verifyChainIntegrity();

​
End-to-end example: voice command

“Jarvis, deploy the staging build”:
1
Voice → OpenClaw transcribes → text
2
Text → OpenClaw Gateway → SINT agent session
3
Agent proposes tool call: exec("railway up --environment staging")
4
@sint/openclaw-adapter classifies → T2
5
Cross-system check: robot.moving? No → continue
6
Policy Gateway validates token scope → ALLOW
7
Evidence ledger writes SHA-256 entry
8
OpenClaw executes the command
9
Result → Conversation Compiler → “Staging deploy is live.”
10
Avatar: smile + Head-Nod-Yes + status widget
11
Evidence HUD: new entry in real-time feed

​
Packages

PackageDescriptionTests
@sint/os-coreMain entrypoint, lifecycle, orchestration9
@sint/openclaw-adapterOpenClaw governance middleware42
@sint/integration-langchainLangChain handler14
Additional components pulled in transitively: @sint/gate-capability-tokens, @sint/gate-policy-gateway, @sint/gate-evidence-ledger, and all 12 bridges.

Console

The visual control surface for SINT OS.

Quickstart

Run the OS locally in under five minutes.