Decision pages

Two workspace hygiene decisions: (1) restrict posting on #x-all and migrate discussions to specific channels, and (2) remove third-party AI bots and competitor tools from the production workspace.

Created public sub-processor register at boolab.ai/legal/subprocessors with 18 vendors. Key distinction: customer-connected integrations are NOT sub-processors — they are the customer's own tools accessed on their behalf.

When a user asks about an integration that isn't pre-built, Boo must never lead with limitations. The correct response leads with what Boo CAN do. LLMs already know how to use most tools — building a catalogue of 400 integrations adds zero value.

Heartbeat capability is enabled by default for new customers, but no default heartbeat tasks are configured. The scheduler won't run until the customer sets up their own tasks. This balances capability availability with avoiding unwanted charges.

When a customer creates a second Boo deployment in their org, certain default bundles (like content calendar) should be disabled to avoid frustrating the user. Acknowledged as a design consideration but deferred as 'problems of tomorrow.'