RTQ Documentation
Dependency-free capability-security runtime. Every operation is an explicitly registered capability; every authorization is a short-lived, single-use, cryptographically-signed ticket.
→ Clarification → Approval (human/device) → Ticket (signed, single-use)
→ Execution (OS-sandboxed) → Audit (redacted)
Overview
RTQ pipeline, packages, and getting started.
Security Overview
Pipeline layers, core principles, quick example.
Threat Model
Trust boundaries, threats, mitigations, honest limitations.
Verification Matrix
12 automated invariants, test suites, platform gating.
Verification & Traceability
Source file:line citations for every security claim.
Platform Support
macOS Seatbelt, Linux bubblewrap, Windows AppContainer.
Aartiq Integration
How to bring RTQ to an Aartiq-style federated MCP app.
Mobile Approval
QR challenge-response, signing, pairing, protocol.
CLI Reference
Capabilities, policy check, sandbox test, verify, diagnostics.
Testing Strategy
Labels, suites, platform gating, CI.
Provenance
Original implementation, audit trail, design inputs.
Quick start
import { createRTQ } from "@rtq/security";
const rtq = createRTQ({ signingKey: process.env.RTQ_SIGNING_KEY! });
rtq.registerCapability({
name: "files.read",
version: 1,
description: "Read a file inside the workspace",
inputSchema: { type: "object", properties: { path: { type: "string" } }, required: ["path"] },
risk: { base: "low" },
execute: async (ctx, input) => ({ ok: true, data: { input } }),
});