Zenzic v0.6.0a1 — The Sentinel
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.
What shipped
This alpha established three architectural pillars that remain non-negotiable to this day:
-
Lint the Source — Zenzic never runs the build. It reads raw Markdown and configuration
files directly. HTML output is never trusted.
-
No Subprocesses — 100% pure Python. No
subprocess.run, no Node.js execution,no external process calls in the hot path.
-
Pure Functions First — Deterministic logic. No I/O inside link-validation loops.
Core capabilities in v0.6.0a1
| Feature | Status |
|---|---|
zenzic check all — multi-mode file scan | ✅ Alpha |
| Shield credential scanner (exit code 2/3) | ✅ Alpha |
| MkDocs adapter | ✅ Alpha |
| Docusaurus v3 adapter | ✅ Alpha |
| Virtual Site Map (VSM) | 🚧 Prototype |
The Sentinel identity
The "Sentinel" codename captured the philosophy: an always-on guard at the source boundary, not an inspector of finished output. The Sentinel does not care how the site renders. It cares whether the source is honest.
The Shield — the credential scanner — was the first concrete expression of that posture: a module that exits with code 2 on secrets detected and code 3 on a Blood Sentinel (fatal leak pattern), before any documentation build can begin.
What came next
The critical groundwork laid in v0.6.0a1 — especially the find_repo_root() discovery
protocol (ADR 003) and the two-phase zenzic init bootstrap sequence — proved solid
enough to survive two major hardening passes without architectural change.
Read the full technical story: Your Documentation is a Leaking Pipe