Playbooks
Vertical- and regulation-agnostic rules that start work — tiers 1–3, pause anytime.
Who this is forOrg admins, compliance, and shared-service leads configuring orchestration.
Org adminHR reviewerCompliance officerScreenshot shown as: Priya Raman
moosh.app/admin/playbooks
Playbooks are versioned rules: recurring pulse, signal-to-pack, post-control effectiveness, review-trigger executor, and standard-control auto-approve.
They are deliberately **not** industry- or country-hardcoded. Jurisdiction packs declare capabilities; playbooks reuse them. Pause or test-fire without code changes.
Default posture in the mock is Tier 2 (orchestrated). Tier 3 only auto-applies standard library controls under policy.
For example
Priya test-fires signal_threshold_pack; a Logistics Decision Pack appears for shared-service approval and an email outbox row is recorded.
Worth knowing
- Autonomy tier
- 0 console · 1 assisted · 2 orchestrated · 3 conditional auto for standard controls only.
- Playbook
- A versioned rule that starts work from a schedule, threshold, or event.
What you can do here
- 1Review system templates and tiers.
- 2Pause or resume auto_run playbooks.
- 3Test-fire a signal pack in the demo.