nacl

🇷🇺 Русская версия

NaCl

NaCl is a graph-first software-delivery framework for Claude Code and Codex. Business analysis, system specifications, delivery evidence, and traceability live in a Neo4j knowledge graph instead of a disconnected document pile.

Choose the runtime channel

Runtime	Ordinary installation	Status
Codex Desktop	Full NaCl plugin from the Plugins UI	Local candidate verified; public HTTP/OAuth service, public listing, and release are NOT_RUN
Claude Code Desktop	NaCl marketplace plugin	Supported by the current 2.24.0 package
Claude Code CLI	Repository-backed Claude skills	Supported compatibility channel

For Codex, the full plugin is the normal path: one UI install supplies the application surface, ten public skills, sixty internal skills, and twenty-five bounded MCP tools. The old skills-only Codex layout is compatibility-only. See Skill Installation.

Install in Codex Desktop

Open Plugins, select the trusted NaCl card supplied for your workspace, install it, grant only the permissions shown by Codex, fully restart the app, and open a new task. Do not use a saved package path from another computer.

The local candidate has been verified from Codex's installed cache. A portable public card or URL is not yet available: the public Streamable HTTP MCP endpoint, OAuth flow, release, and marketplace submission remain NOT_RUN. Follow the Codex installation guide for the current verified boundary.

Verify before project work

In a new Codex task, ask NaCl to call nacl_installation_doctor exactly once. Continue only when it reports:

• status=VERIFIED;
• mode=plugin-only;
• the version shown by the installed card;
• executionLocation=installed-cache.

Then use the Quick Start for the first dry run and project initialization.

Graph model

Each project gets its own Neo4j 5 Community container and durable volumes. /nacl-init can create it locally, connect to a project container on a reachable VPS, or register an existing connection. Local Docker remains the default.

The server is the current authorization boundary: a developer who has access to a Neo4j server is treated as able to access every project database hosted there. project_scope selects and records the logical project; it is routing and provenance, not an authorization control. A future public Codex service must authenticate the user with OAuth, map that principal to an allowed server, and reject cross-server routing. NaCl does not provide a managed graph service.

Key concepts

• Graph-first analysis. Processes, entities, roles, rules, and use cases are Neo4j nodes and relationships, so impact analysis and traceability are queryable.
• Configurable language. An explicit --lang=en or --lang=ru wins, then project.lang in config.yaml, then the layer default. BA and SA default to Russian; TL defaults to English.
• Atomic delivery. Each use case is developed, tested, reviewed, and shipped as one bounded unit.
• Two-level QA. Local code verification precedes staging E2E verification.
• Config-driven operation. config.yaml controls Git strategy, graph connection, project identity, and optional integrations.

Release foundation and strict mode

The 2.10.0 goal-protocol foundation added nacl-goal, the GOAL_PROOF wire format, the wave, fix, validate, and reopened-drain aliases, structured refusals, and a permissions denylist. See the goal command guide.

Since 2.8.0, NaCl has used evidence-blocking gates instead of treating missing evidence as explanatory prose. Closure refuses terminal states in {UNVERIFIED, BLOCKED, FAILED, NOT_RUN}. Removed skip flags cannot bypass this rule; the retained --skip-e2e has explicit scope. Older projects should start with project-gap-closure.md and use only signed exceptions or the bounded emergency procedure.

What's inside the framework

Root skills follow nacl-{layer}-{action}: