From a whiteboard gap to a working gate
How Veylqorix came to be, told the way it happened: the problem that started it, the eight-day board, the principle that holds it together, the architecture underneath, the process that shipped it, and the extension point that just landed. Six posts, in order.
- WHY2026-10-25
Why: AI code moves faster than your safety net
AI coding agents write a lot of production code — fast, plausible, and sometimes unsafe. Veylqorix fills the gap with a real scanner and a deterministic gate.
Read the post →
- PLAN2026-10-25
Eight days on the board
The plan put a Rust core on day 2. What shipped first is a pnpm TypeScript monorepo; the Rust core later returned as a byte-compatible security engine.
Read the post →
- PRINCIPLE2026-10-25
The day the gate learned to say INCOMPLETE
Exit codes 0, 1, and 2 — and why exit 2 exists: because a scanner that cannot run must never be mistaken for a clean pass.
Read the post →
- ARCHITECTURE2026-10-25
One engine, many surfaces
packages/core sits under every front-end. The CLI, the MCP server, and the API are thin adapters that all call the same runAudit and gate functions.
Read the post →
- PROCESS2026-10-26
A hundred pull requests in a day
The build ran on an automated sync loop: 217 commits, 101 merged sync PRs, 18 web-iteration commits — every GitHub action pinned to a commit SHA.
Read the post →
- EXTENSION2026-10-26
New scanners in. The gate, unchanged.
The plugin SDK adds your own scanners and checks with two invariants: a broken plugin can never clean a scan, and plugins only add evidence.
Read the post →
- SUPPLY CHAIN2026-10-26
Shipped hardened: pinning every byte before it reaches a consumer
The release pass hardens the supply chain: SHA-pinned CI, 8 patched postcss/sharp advisories, a clean cargo audit, and fail-closed provenance. Run from source.
Read the post →
More of the record
Roadmap
The eight-day board, day by day
The target sequence, the honest pivot, where the project stands now, and what is next.
Open the roadmapChangelog
0.1.0 and 0.1.1, release by release
Every group of changes, the release checklist, and the sync-loop activity strip.
Open the changelog