Stella Loop sync

Torno decides what to build and measures whether it worked; many teams run the building itself in Stella Loop, the agent-native project management tool. An optional sync connects the two at the API boundary: Hypotheses become work items, shipped work activates Changes, and Results flow back as evidence. They remain separate products.

Connecting a Workspace

A Workspace owner stores a write-only Stella API key, verifies the remote organization, registers a signed webhook, and maps each Torno Property to a Stella project. A health view covers credentials, webhook status, mappings, queue and dead-letter state, and reconciliation. Disconnecting preserves historical links read-only and visibly cancels queued deliveries — nothing disappears without saying so.

Hypothesis to work item

Only an accepted Hypothesis whose proposed Change is a product change, backed by a suitable brief, can link to Stella. A preview shows the exact contract that will be sent before anything leaves Torno. Submission is idempotent and retry-aware, and the link records the remote state: queued, accepted, building, shipped, dropped, or unlinked. Later edits in Torno annotate the Stella item rather than rewriting its history, and bursts of edits coalesce instead of spamming the other side.

Ship events activate Changes

When Stella reports work shipped, a signed, idempotent event moves the linked Change through Torno’s normal readiness and policy transitions — acting as the connection’s own Principal, subject to the same rules as everyone else. A Change that is not ready, or that is held for approval, stays visibly held; a ship event cannot skip governance. Shipping also starts a drift expectation: Torno now expects to observe exposure, and the first real exposure clears it. A Change that shipped but was never seen is a finding, not a footnote.

Results post back

Experiment evidence posts back to the Stella item with its uncertainty intact — a significant_win arrives as a significant win with bounds, and insufficient_evidence arrives as exactly that. Guardrail breaches bypass normal coalescing and go through immediately. If the postback fails, Torno’s own measurement is unaffected; the evidence exists regardless of whether Stella heard about it.

Voice evidence, still fenced

Selected voice Signals and theme Insights can promote to Stella as triaged feedback, carrying provenance and sample size with them. The content stays fenced as untrusted data end to end, exactly as it does inside Torno’s own listening pipeline. Behavior Signals are refused — event streams are not feedback. And if the original author’s data is later erased, the promoted copy is redacted through the same data-subject-request contract described in Identity and privacy.

When Stella is unreachable

Outages queue and degrade. Deliveries retry on a schedule, dead-letter when exhausted, and reconcile when the connection returns, with all of it visible in the health view. Postback failure never blocks measurement, and no state transition in the Torno Loop waits on Stella. The sync is a convenience at the boundary, not a dependency in the middle — see The Loop for what always keeps running.