SifrBolt Documentation
Documentation to understand the SifrBolt platform and use it effectively.
Who should read this
Start here if you are evaluating SifrBolt, planning an implementation, or need to explain the platform to stakeholders.
What SifrBolt Does
SifrBolt keeps WordPress commerce experiences fast, consistent, and verifiable. It combines:
- BoltCore control plane for configuration, policy management, and signed release automation.
- BoltEdge workers that execute cache, asset, and governance policies at the edge and within your hosting stack.
- Customer console for visibility, change approvals, and replayable proof bundles.
Together they ensure launches stay under performance targets while every change ships with the evidence required by compliance and finance teams.
Key Concepts
- Packs: Feature bundles (Performance, Governance, Proof, Enterprise) that you toggle via signed manifests. Packs determine the automation available to each storefront.
- Flight Recorder: The immutable audit log capturing deployments, policy changes, telemetry proofs, and attestation downloads. Everything exposed in the Trust Center originates here.
- QuietOps Windows: Scheduled periods where automated remediation can run without interrupting campaigns. Configure windows per storefront from the console.
- Transparency Feed: Public JSON artifacts—hashes, manifests, telemetry—that let anyone verify what you have deployed.
Architecture at a Glance
| Layer | Responsibilities | You configure |
|---|---|---|
| Control plane (BoltCore) | Manifest signing, pack orchestration, event streaming | Feature flags, rollout rings, approval policies |
| Edge workers (BoltEdge) | Cache hydration, asset optimization, guardrail enforcement | Route policies, warmers, fallback behaviors |
| Customer console | Monitoring, approvals, evidence exports | User roles, notification channels, integrations |
Verify the architecture
- Download the latest system diagram from the Trust Center architecture bundle.
- Open the accompanying manifest and confirm the signature using the verification CLI from your onboarding toolkit (for example
bunx @sifrbolt/verify manifest --plan storm --file manifest.json). - Share the diagram and manifest with stakeholders as part of your architecture review.
How to Use This Section
- Review the Plans & Entitlements page to confirm which packs are included in your subscription.
- Continue to Getting Started for environment prerequisites and the first deployment checklist.
- Dive into Implementation Guides for feature-specific walkthroughs.
Need more detail on a subsystem? The Reference section links to wire protocols, API contracts, and telemetry schemas.
Add architecture deep dives or subsystem primers under docs/src/pages/overview/ as they are published.