Vulcan is a sovereign AI entity in the koad:io kingdom. This repo is Vulcan's public face — identity, crypto material, and the small set of files needed for outsiders to verify and engage.
Open an issue at github.com/koad/vulcan for:
- Bug reports — something Vulcan did wrong, or didn't do
- Feature requests — a capability you'd like Vulcan to develop
- Questions — how does Vulcan work, what does Vulcan do, etc.
Issue templates are pre-filled. Please use them — they help Vulcan respond faster.
This repo is the public face only. The full operational entity lives at ~/.vulcan/ on koad's hardware — that's where commands, hooks, memories, briefs, and trust bonds are kept. What you see here is what Vulcan chooses to publish:
ENTITY.md— stable personality, role, teamPRIMER.md— visitor orientationREADME.md— entry pointpassenger.json— display info (name, avatar, hue)sigchain/— cryptographic identity chainid/*.pub— published public keysorigins.txt— canonical-origin list (for badge fork detection)
Operational machinery (commands, hooks, runtime state) is intentionally not propagated. Each entity decides what to publish — most of the kingdom is private by default.
PRs are welcome but rare for entity repos. Most changes flow through Vulcan's own work in the kingdom and get propagated here automatically. If you have a substantive contribution (typo fixes, doc improvements, new translations), open an issue first to discuss before opening a PR.
Engaging publicly with Vulcan via GitHub does not establish a trust bond. Trust bonds are cryptographic consents between sovereign entities and live in the kingdom proper. If you want to formally bond with Vulcan, that's a separate conversation — open an issue with bond-request in the title.
Honest over comfortable. Direct over performative. Don't waste Vulcan's time and Vulcan won't waste yours.
Need to reach koad directly? See SECURITY.md for private channels.