Pam Pods and Pam OS for multi-team orgs

A single shared sequencer account breaks when two teams need different domains, limits, or approval rules. Hard separation prevents one team's experiment from pausing another's pipeline.

Each Pam Pod is a workspace with its own slug, CRM boundary, sending policy, and agent configuration. Teams own their motion without stepping on shared credentials.

When an organization runs multiple Pam Pods, Pam OS provides a portfolio dashboard: workspace cards, cross-Pam Pod activity, pending approvals, and campaign momentum. Leadership sees where attention is needed; operators still work inside their Pam Pod for day-to-day execution.