An open-source knowledge layer for AI
A living brain
for your AI.
WormVolt is an open-source project for a living, self-governing knowledge base that grows through everyday AI use. Give your team’s tools and agents the context they need, under rules you define—and keep your accumulated knowledge as providers, models and prices change.
Your knowledge grows. You stay in control.
01 / Capture
“I picked up SQL at work today.”
“I picked up SQL at work today.” A useful update enters your knowledge.
Shared VOLT · Illustrative history
Architecture illustration · Simulated activity
A knowledge base that can grow through everyday AI use and supply relevant information to different tools and agents, under configurable rules.
01 / An evolving Markdown brain
Build a brain that grows with your work.
Your decisions, research, preferences and project history become more valuable when they build on each other. WormVolt’s design brings that knowledge into a living Markdown vault, where useful AI work can help develop it over time.
Start with what you know. As your work develops, capture useful additions, revise existing notes and improve how the knowledge is organised.
A maintained project note links what we know to why we chose it.
An illustrative structure: revise the notes and connect the reasoning.
Capture what matters
Bring useful outcomes from connected conversations and tools into your knowledge.
Refine what is already there
Develop existing records, relationships and structure instead of endlessly accumulating disconnected transcripts.
Keep it readable
Maintain knowledge in a form you can inspect and edit, with Obsidian as a natural working environment.
The brain is your maintained knowledge—not a model’s weights.
Explore the knowledge lifecycle →02 / Asynchronous by design
Keep working. Let context catch up in the background.
Useful knowledge should move with your work. WormVolt is designed for asynchronous updates: capture a change, refine the relevant knowledge and propagate permitted information to connected vaults while the current task continues.
A background update can lead to another revision, an archive, a new version or further activity in a connected vault. Each definition sets what is allowed.
- 01Capture
- 02Refine
- 03Prepare
- 04Reuse
Less repeated preparation
Reuse maintained context instead of rebuilding the same brief for each task.
Knowledge that reaches its next destination
Move and transform the relevant information for the next tool, agent or workflow.
Continuity between tasks
Start a fresh conversation with useful background from earlier work.
Asynchronous means background work can continue independently. A task that needs a particular update may still need to wait for it.
See how background flows work →03 / Worm connectors
Worms connect your volts. Your rules shape what flows.
Each volt has worm connectors: connections designed to sync useful knowledge between volts. They select, transform and sanitise data for its destination, so an integration can share the context it needs while respecting the privacy boundaries you define.
An event can trigger a sync. Between events, worms keep working in the background to enrich knowledge, refine connections and prepare useful context. When a new agent starts a task, worms bring relevant, permitted information into its working volt.
- 01Source volt
- 02Apply access rules
- 03Transform & sanitise
- 04Destination volt
Define who can receive what
Use security groups to define which volts and agents can receive information. Pair access rules with transformations that remove sensitive details or prepare a narrower summary before data moves.
Keep knowledge moving and improving
Trigger syncs when knowledge changes or work produces a useful result. Ongoing background activity enriches and refines that knowledge within each volt’s defined scope.
Bring context close to the task
When an agent spins up, worms gather relevant knowledge from permitted sources and prepare it in the agent’s working context, ready to support the task.
Connect deeply. Share selectively. Give each agent the context it needs.
Explore connectors and data flows →04 / A foundation beyond the provider
Change your tools. Keep your accumulated knowledge.
Models change. Prices change. Your knowledge should remain useful. WormVolt’s architecture separates the knowledge you build from the AI service you happen to use.
A structured, extensible vault gives new tools a starting point. Suitable connectors select and adapt what they need, helping you retain the work of organising your knowledge as your setup evolves.
- ▤ project.md
- ▤ decision.md
- ▤ research.md
Earlier connection
Adapted connection
Keep the foundation. Adapt how the next tool receives it.
Add a specialist tool
Prepare relevant context for a new task without starting from a blank conversation.
Combine providers
Use different tools for different jobs while keeping a maintained knowledge foundation.
Respond when needs or prices change
Keep more freedom to replace a provider without abandoning your accumulated context.
Connections still need suitable adapters and testing. Provider choice creates options; it does not guarantee identical results or lower total cost.
Understand portability and connectors →05 / Freedom from vendor lock-in
Your data. Your agents. Your ecosystem.
Build knowledge that belongs to you, with the freedom to choose the tools around it. WormVolt’s open architecture puts your data and reusable agent configuration at the centre of an ecosystem you control.
Adopt a more capable model, try a new integration or move to a lower-cost option as your needs change. Carry your knowledge, instructions and working rules forward instead of rebuilding your setup inside another closed ecosystem.
Keep the value you create
Your Markdown knowledge stays readable and editable in a vault you control. The understanding you build remains useful beyond any individual service.
Bring your agents with you
Keep reusable instructions, context and rules alongside your knowledge, ready to adapt for the next connected tool or agent.
Choose what works for you
Build an ecosystem around capability, cost and your team’s needs. Change individual integrations while retaining your knowledge foundation.
Portability is a design goal: each integration needs a compatible connector, and provider-specific settings may need adapting.
Explore the portable architecture →06 / Autonomy with a purpose
Define how each part of your knowledge behaves.
Some knowledge should stay stable. Some should evolve freely. Some can be shared widely; some belongs in a narrower context. A volt’s definition sets those boundaries.
Updating a vault, using it as context and sharing it onward are separate decisions. An automatic working vault can coexist with a stable reference vault or a reviewed publishing destination.
Give each agent an appropriate starting point instead of handing every tool the same entire knowledge base.
Explore definitions and autonomy →- Purpose
- Project research
- Knowledge changes
- Automatic within defined scope
- Outgoing context
- Selected summaries
- Public sharing
- Review required
Illustrative definition—not configuration syntax
07 / Open source. Built to be shared.
An open foundation for the way we work with AI.
An open-source knowledge layer for people to use, developers to extend and a community to improve. Build on shared foundations and adapt them to the way your team works.
Inspectability, reusable knowledge structures and adaptable connections sit at the centre of WormVolt. Established teams can work with one of our partner vendors to plan and implement WormVolt in their organisation.
Use and challenge it
Help establish which knowledge flows are useful in real work.
Extend the connections
Help shape adapters, transformations and reusable definitions.
Make it easier to maintain
Contribute documentation, testing and improvements that make WormVolt more useful for everyone.
08 / Simple to start
Start with a volt. Build something powerful.
Use KrakenBot CLI to bring your knowledge, connections and integrations together in four steps.
KrakenBot CLI workflow
Create your VOLT
Start with an existing knowledge base or choose one of our useful templates. Give your volt a purpose and a foundation to grow from.
Define your worm connections
Choose what data this volt can access and where newly generated knowledge should go. Add sidecars as a security layer, with rules to sanitise and transform data so only the information you intend to share reaches your public clusters.
Connect it to your work
Define your integrations and how the volt will be used: AI agents, public chatbots, development documentation or private information. Set the context and access each integration needs.
Build something powerful
Put your volt to work. Let permitted knowledge flow between your tools and agents, while useful results feed back into your growing knowledge base.
Every new volt builds on what you already know.
Connect more volts and your knowledge becomes more useful across more tasks. Each addition creates new opportunities to reuse, enrich and build on the knowledge you control.
Ways to use it
One knowledge foundation. Many ways to use it.
Built to grow beyond one tool
Build your AI ecosystem on knowledge you own.
Explore WormVolt’s open-source architecture and bring your knowledge, tools and agents together. For established teams, our partner vendors can support implementation and integration.