VULCAN

Appearance

Changelog - 2026-10-17 ​

VULCAN 0.1.0-0: one setup for every VENIZIA project ​

Type: Feature

In one line. One devDependency gives a project VULCAN's rules, agent setup, knowledge tooling and atlas, instead of a copy of each.

bash
bun add -d --exact @venizia/vulcan@next @venizia/dev-configs
bun x --no-install vulcan init
bun x --no-install vulcan sync
bun x --no-install vulcan doctor

What changed ​

  • @venizia/vulcan. The vulcan CLI: init, sync, doctor, upgrade and x. It ships the base rules, the agent hooks, the shared skills and vulcan.mk.
  • @venizia/vulcan-okf. Checks the knowledge bundle against OKF v0.2 (vulcan x okf check), plus gen, coverage and the offline graph explorer.
  • @venizia/vulcan-atlas. The MCP knowledge server, and the surface, symbols and releases table generators (vulcan x atlas ...).
  • Namespaced base rules. Base rule IDs carry V- (V-W-01, V-C-04). A project's own rules keep bare IDs, so they never collide with the base.

Who is affected ​

  • IGNIS, ARDOR, BANA. Switch from your own copies when you adopt: add the devDependency, run sync and doctor, then delete the copies. Your rule IDs stay as they are.
  • Everyone else. No action needed until you adopt VULCAN.

Details ​

  • Prerelease: published to the next dist-tag. latest comes with the first stable version.
  • okf gen, okf check --strict and the atlas generators still assume an IGNIS-shaped project. Project config for renderers and package maps is planned.