SifrBolt / docs

SifrBolt Documentation

Documentation to understand the SifrBolt platform and use it effectively.

Scope

Use this section when you are responsible for keeping storefronts healthy after the initial launch.

Daily Checklist

  • Review the console Health dashboard for agent status, error budgets, and cache hit ratios.
  • Confirm QuietOps sweeps completed successfully; investigate incidents before the next trading window.
  • Check Transparency alerts for new manifests or rulepack updates that require action.

Key Requirement

Never promote a new policy without attaching the signed bundle to Flight Recorder. This keeps your audit trail complete.

Weekly Tasks

  1. Reconcile rollout rings to confirm storefronts remain on their intended policies.
  2. Export latency and conversion metrics for stakeholders using the console reporting tab.
  3. Rotate API tokens or keys flagged for refresh in the Trust Center.

Incident Response

  • Use the console Support panel to open Sev-1 tickets; include the bundle ID associated with the issue.
  • Pull the latest transparency bundle for the affected storefront and attach it to your incident bridge.
  • Capture remediation steps in the console so the Flight Recorder entry contains the full resolution timeline.

Evidence Management

Prepare an audit packet

  1. Download the latest compliance bundle (SOC, PCI, regional) from the Trust Center.
  2. Verify signatures with the CLI (for example bunx @sifrbolt/verify manifest --plan <code>storm</code> --file compliance-bundle.json).
  3. Store verified artifacts in your evidence repository with the associated Flight Recorder IDs.

Add storefront-specific checklists or advanced runbooks under docs/src/pages/operations/ as operations mature.