SifrBolt Documentation

Documentation to understand the SifrBolt platform and use it effectively.

How to use this guide

Work through these phases sequentially. Each milestone links to verification steps so you can prove progress to stakeholders.

Phase 0 · Confirm Readiness

Review the Plans & Entitlements page to confirm required packs are included.
Invite stakeholders to the console with roles that match their responsibilities.
Capture baseline performance and compliance metrics for your current storefront.

Phase 1 · First 48 Hours

Activate your pilot environment

Install the WordPress bridge plugin and connect to your sandbox storefront.
From the console home, run Perform Handshake to make sure storefront agents register.
In the console, open Launch Checklist and confirm all agents report Healthy.

Capture baseline metrics for page load, cart conversion, and compliance exceptions.
Enable BoltEdge critical CSS and JS scheduling on a low-risk route to validate integration.
Notify your internal stakeholders so they can observe the Flight Recorder entry for this phase.

Phase 2 · First 7 Days

Expand coverage to top revenue routes using rollout rings (10% → 50% → 100%).
Configure governance templates that match your regulatory posture (PCI, SOC 2, regional residency).
Connect telemetry exports to your analytics stack so exec dashboards show live improvements.

Verify improvements

Download the latest attestation pack from the Trust Center.
Use the verification CLI (for example bunx @sifrbolt/verify rollout --bundle <code>bundle-id</code>) to validate locally.
Share the verification output with stakeholders and update your launch record.

Phase 3 · Day 30 Review

Present the revenue impact, performance gains, and compliance posture using the Success Narrative template.
Decide whether to unlock enterprise packs (SSO/SAML, WAF orchestration, ZK attestations) based on upcoming initiatives.
Schedule the next business review internally and log the action in the console so it appears in Flight Recorder.

Next Steps

Read the Platform Overview if you have not already.
Dive into Implementation Guides for feature-specific configuration.
Monitor new functionality in Release Notes.

Add specialized launch guides under docs/src/pages/getting-started/ for verticals, partner programs, or advanced features.