Quartz Maturity
During the final consolidation sprint for v0.7.0, we ran four AI agents against Zenzic's own documentation site. They were instructed to find everything wrong with it.
Open source practices, licensing, and community building.
Guarda tutte le etichetteDuring the final consolidation sprint for v0.7.0, we ran four AI agents against Zenzic's own documentation site. They were instructed to find everything wrong with it.
The siege is over. All four bypass vectors are closed. 1,195 tests pass. The Bastion holds.
Your docs have broken links. You just haven't found them yet.
Zenzic finds them before your readers do — before you build, before you deploy, before it's too late.
This is a historical record of a development milestone. The first stable release is v0.7.0 — Quartz Maturity.
v0.6.0a1 — The Sentinel is the founding alpha: the release that crystallised the philosophy of Zenzic from a prototype into a disciplined engineering system.
Skip the engineering deep dive — jump straight to the ⚡ Tutorial: Stop Broken Links and protect your docs in 5 minutes.
Every CI/CD pipeline has a security perimeter. Developers run static analysis on source code. They scan container images for CVEs. They audit dependencies for known vulnerabilities. They enforce secrets detection in commit hooks.
And then they push raw, unvalidated Markdown files directly into a documentation build — and call it shipped.
This is not a theoretical gap. It is the default posture of almost every engineering team I've observed. I built Zenzic to prove it — and fix it.