Open source
Sarmal
Sarmal does not generate code; it generates intent. It writes folder layout, technology bindings and the order of work into declarative .sar files, then measures the drift between plan and disk. The human gives intent and approval, the agent produces, and the engine makes the difference between them visible.
The rail for spec-driven development.
Human driver. AI bullet train. Sarmal the rail.
Sarmal
Planning language
.sar files carry the whole memory of the work through the Phase, Block, Layer, Sublayer and Step chain.
Audit engine
Plan and disk are compared on every save; broken references, undeclared folders and cone-less Steps show up at once.
VS Code extension
Diagnostics live in the editor, the plan in a panel, status records on their own surface.
MCP server
Agents such as Claude, Codex and Gemini read and audit the plan with the same tools.
Quick start
# 1 git clone https://github.com/nexivion-labs/sarmal.git
# 2 cd sarmal/urun/cekirdek && npm link
# 3 sarmal başla proje
# 4 sarmal doğuş ilk-proje --tur proje
# 5 sarmal denetle ilk-proje
# MCP claude mcp add sarmal -- node <depo>/urun/cekirdek/src/mcp.tsNode.js ≥ 23.6
Licensed under Apache-2.0.
When to use it
For long-lived, decision-heavy, agent-heavy work. For a two-week solo experiment the discipline Sarmal brings can be heavier than needed, and we say so plainly.