NervaFS is the substrate layer for agent systems. Keep storage, identity, policy, tools, and mounted capabilities behind one filesystem contract, then let runtimes and orchestration bind above it.
Most agent stacks collapse storage, execution, and coordination into one moving target. NervaFS argues for a different shape: keep Substrate, Runtime, and Orchestration separate, then connect them through one filesystem-native contract.
A substrate layer that makes identity, memory, policy, logs, tools, channels, and mounted systems inspectable and governable without forcing a runtime or orchestration opinion.
This is not a feature buffet. It is the operational upside of keeping the agent substrate stable while runtimes and orchestration evolve above it.
read, write, ls semantics..agent_bundle. Deploy on any runtime in seconds, any environment.Plugins are how NervaFS grows without turning back into a bundled stack. Mount systems, replace stores, and package capabilities while keeping the same substrate contract.
type: tool name: my-tool mount: /tools/my-tool entrypoint: ./bin/my-tool interface: stdin: json stdout: json exitcode: standard man: ./docs/man.md
plugin.yaml declaring type, mount path, entrypoint, and interface contract.nervafs plugin install ./my-plugin. The path appears instantly in every agent's filesystem.man doc or .readme.skill and start using the new capability immediately.The page should teach the idea first, then let visitors self-select. Use docs if you want to inspect, use the waitlist if you want updates, and use Discord if you want to discuss the architecture now.