SifrBolt Documentation
Documentation to understand the SifrBolt platform and use it effectively.
How to Read This Log
Each entry is designed for customers first: what changed, how it improves your outcomes, and where to verify the proof. Share it with exec sponsors or security teams so everyone sees the signal immediately.
Entry Template
### YYYY-MM-DD — Headline Impact
- **Why it matters:** Tie the change to a measurable customer outcome.
- **Proof:** Link to the relevant manifest, hash ledger, or performance chart.
- **Who benefits:** Name the roles or plans affected.
- **What’s next:** The follow-up action customers should expect.
Recent Highlights
2025-01-15 — TLS Hardening Unlocks Global Commerce Bids
- Why it matters: EU marketplaces cleared SifrBolt for regulated categories after we enforced modern cipher suites by default.
- Proof: See the updated license manifest under plan
stormand the signed rulepacktls-hardening-2025-01in the Trust Center. - Who benefits: Storm and Citadel plans; marketplace teams shipping into regions with PSD2 requirements.
- What’s next: Compliance team is preparing a joint customer briefing for Q2.
2025-01-02 — Proof Transcript Replay Goes Self-Serve
- Why it matters: Security reviewers can now replay any attestation without waiting on our team, cutting procurement cycles by five days on average.
- Proof: Transcript bundle
FR-2501and the Trust Center replay script bundled with it. - Who benefits: All plans activating proof exports, especially teams in due diligence.
- What’s next: SOC 2 Type II evidence packs arrive in February.
Add new release notes or roadmap previews under docs/src/pages/release-notes/ and link them here once they ship.