Torno documentation
Everything you need to run growth Loops with Torno — from the first
torno init to sequential evidence, policy-gated ad publishing, and a fleet
of agents working through the CLI.
Getting started
What is Torno? Torno is the agent-native system of record for growth work: what the Loop is, who Torno is for, what it bundles, and what it deliberately leaves out. Getting started The shortest path from a repository to a first Loop: create a Workspace and Property, run torno init, define a Metric, and verify events arrive.
Core concepts
The Loop The durable state machine behind every growth objective in Torno: its states, a complete turn, honest failure semantics, and the append-only decision log. Loops in practice The operational side of Loops: what a Loop binds, subscriptions and routing, cadence, the intake queue, proposals, pause and archive, and concurrency. Metrics and the semantic layer How Torno defines a business number once — named, typed, versioned — and serves every surface the same envelope, with uncertainty rendered honestly.
Signals & data
Signals How Torno records observations as immutable Signals with provenance, trust labels, and quarantine for untrusted content. Event collection Torno's first-party collection boundary: the track, identify, expose, and goal calls, write keys, the event dictionary, dedup, signing, and bot handling. Listening Connectors that bring reviews, forums, search queries, and support email into Loops as quarantined, provenance-labeled Signals. Identity and privacy Torno's two-zone identity model: cohort-only visitors, the pseudonymous Subject key, k-anonymous aggregates, consent, retention, and data subject requests.
Measurement
Experiments Pre-registered Experiments wrap Change variants in a stats plan and report evidence in an explicit, closed vocabulary — never a naked p-value. Analytics Funnels, retention, and paths as Loop instruments, with autocapture controls, historical imports, and k-anonymous privacy on every read. Revenue and the Needle Read-only Stripe data becomes normalized MRR, and the Needle composes your target Metric, its decomposition, and every live Change aimed at it.
Action
Changes and delivery How a Change declares its measurability up front, and how variants are delivered from signed, locally evaluated bundles with sticky rollout, ramp, and kill controls. Briefs Versioned landing-page and content briefs that specify what to build, why, how to instrument it, and how Torno will know whether it worked. Ads Campaign and creative drafts for Google and Meta, grounded in your Brand Kit, published under human approval with hard spend controls. SDKs A JS core under 10 KB gzipped, framework adapters, server SDKs, and edge middleware — event collection and local Change assignment with no Torno call in your customer's request path.
Agents & governance
The agent interface One registered capability map drives Torno's web app, REST API, CLI, and MCP surfaces, with idempotent mutations, webhooks, and exportable data. The CLI torno is the priority agent interface: non-interactive by default, machine-readable, with meaningful exit codes and the same policy paths as the web app. Loops as code Represent Metrics, Loops, Changes, tags, and the event dictionary in torno.config, sync with pull, diff, and push, and enforce the contracts in CI. Policy and approvals How policy gates irreversible, sensitive, and spending actions with allow, deny, or require-approval outcomes, Approval Requests, and spend ceilings. Stella Loop sync The optional integration that turns accepted Hypotheses into Stella Loop work items, activates Changes on ship, and posts Results back as evidence.