Skip to main content

Documentation Index

Fetch the complete documentation index at: https://docs.signalrooms.xyz/llms.txt

Use this file to discover all available pages before exploring further.

​
Operator guide

Status: Current overview. Each subsection links to a deeper page; this index is the map. SignalRoom’s operating model has six concepts. They sit on top of the Warmr control plane, but you can operate the product without reading the control-plane reference, every concept has a UI surface in Warmr.app and a warmrctl surface for scripts and agents.

​
The six concepts

                ┌─────────────────────────────────────────────────┐
                │                  Device lanes                    │
                │   One iPhone = one lane = one runner at a time   │
                └────────────────────────┬────────────────────────┘
                                         │
                                         ▼
        ┌────────────────────────────────────────────────────────┐
        │                     Posting runs                        │
        │  Template × Account list × Lanes × (optional proxy)     │
        └─────┬────────────────┬────────────────┬─────────────────┘
              │                │                │
              ▼                ▼                ▼
       ┌────────────┐    ┌────────────┐    ┌─────────────────┐
       │ Cooldowns  │    │ Approvals  │    │ Logs + evidence bundles │
       │ Pacing the │    │ Operator   │    │ Streaming +     │
       │ work       │    │ intent     │    │ post-run audit  │
       │            │    │ gates      │    │                 │
       └────────────┘    └────────────┘    └─────────────────┘
                                                  │
                                                  ▼
                                    ┌──────────────────────┐
                                    │  Failure recovery     │
                                    │  When a run errors    │
                                    │  or a lane wedges     │
                                    └──────────────────────┘

​
Device lanes

A lane is one physical iPhone connected to the Mac host. Lanes have ownership (exactly one Warmr instance owns a lane at a time), readiness (connected + trusted + runner installed), and a state surface (warmrctl devices list). Scaling SignalRoom = adding more lanes, not bigger lanes.

​
Posting runs → step-by-step

A posting run is the operator-facing label for the publish workflow. Under the hood it’s a thread: a template + an account list + one or more lanes. Threads start, run, and finish. Each thread has an id, a status, and a set of counters (videos watched, likes given, accounts processed). One posting run can fan out across multiple lanes in parallel.

​
Cooldowns

Three pause knobs control pacing: between publications on the same account, between accounts, between cycles. Cooldowns aren’t just throttling, they’re what makes “five publications across a list” look like a person working rather than a script crashing through the list. Sensible defaults are documented; pushing them too low produces the failure modes most operators run into first.

​
Approvals

Action commands (thread start, thread stop, evidence export, app lifecycle) require explicit operator intent. The control plane has an automation enabled toggle that gates action methods entirely, when it’s off, thread start returns a domain error instead of doing anything. Agents are expected to treat this as a hard wall and not try to work around it.

​
Logs and evidence

Two surfaces. Logs are server-pushed log.line notifications you can subscribe to for real-time visibility (warmrctl logs --follow). Evidence bundles are evidence bundles you export at the end of a run (warmrctl evidence export), they’re the “what happened” artifact for review or support tickets.

​
Failure recovery

When a run errors, recovery is layered: per-step retry inside the runner, runner restart on the iPhone, lane reconnect from the Mac, and (last resort) app restart. The page walks the decision tree, when to wait, when to intervene, when an error class means the operator (not the app) has to do something.

​
What’s NOT in this section

  • Step-by-step setup for a posting run, captions, activity workflows, content folders → that’s How-to guides.
  • Host machine / iPhone hardware prep → Setup.
  • Driving runs from warmrctl for agents and scripts → Agent docs.
  • Schema / control-plane / state-model details → Reference.
This section is the concept layer. Use it when you want to understand what something is in SignalRoom’s model; use the how-to and reference pages when you want to do something or look up a field.

​
A typical operator’s mental model

After your first 30 minutes, this is the model that gets refined:
  • Lanes are physical and finite, adding a lane means adding hardware.
  • Templates are the recipes you write once and reuse across runs.
  • Account lists are the targets a template gets applied to.
  • Threads are runs in flight, they hold a template, accounts, lanes, and runtime state.
  • Evidence bundles are the immutable record of what a thread did.
  • Cooldowns + approvals are the rate-limiters and the operator’s seat in the loop.
  • Failure recovery is the rulebook for what the app handles automatically vs. what wants human attention.
If you internalize that model, the rest of the docs map cleanly.