SifrBolt Documentation

Why it matters

Drift sweeps detect configuration changes that fall outside your approved policies. Automating them keeps procurement, security, and marketing aligned.

Prerequisites

• Storm or Citadel plan with Governance Packs enabled.
• Console access with permissions to edit QuietOps windows and automation scripts.
• Ticketing or notification channel to receive sweep summaries.

Step 1 · Define QuietOps Windows

1. Open Operations → QuietOps in the console.
2. Create windows that avoid peak traffic. Typical cadence is daily, 01:00–03:00 in the storefront’s local time.
3. Assign notification recipients—security, marketing, platform engineering—to ensure everyone receives the report.

Step 2 · Configure Drift Sweeps

1. Navigate to Automation → Drift Sweeps.
2. Select the storefronts covered by the QuietOps window.
3. Choose the policies to verify (rulepacks, cache policies, access controls).
4. Enable Attach transparency bundle so each run links to signed artifacts.

Step 3 · Enable Ticket Sync (Optional)

1. If you use Jira, ServiceNow, or Zendesk, connect the integration under Integrations → Ticketing.
2. Map sweep severity levels to issue priorities.
3. Test the connection using the Send sample sweep button.

Step 4 · Verify Automation

Run a validation sweep

1. Trigger a manual sweep from the console and wait for the completion webhook.
2. Download transcript quietops-sweep-2025-01 from the Trust Center.
3. Use the verification CLI to replay the transcript (for example bunx @sifrbolt/verify drift --bundle quietops-sweep-2025-01).

Ongoing Operations

• Review sweep summaries weekly; investigate any failures before the next campaign window.
• Rotate notification recipients quarterly to keep stakeholder lists current.
• Archive validated transcripts in your compliance evidence folder for audits.

---

Add additional governance automations under docs/src/pages/implementation/ to cover other proof workflows.