Documentation
Grouped by what a page is for, not by what it is about: guides that get you through a task, reference you look things up in, explanation you read once.
Tutorial
01How to
02- Choose a provider The model providers Namzu ships as drivers, how to register one, what changes when you switch, and which to pick for local development, hosted inference, aggregation, or an OpenAI-compatible endpoint of your own.
- Check your environment Use the namzu operator CLI to verify a machine before debugging an agent - runtime version, installed packages, and whether the provider you registered is actually reachable.
Explanation
03- What Namzu is Namzu is an agent kernel for TypeScript, not an application framework. What that distinction buys you, what the kernel owns, what it deliberately refuses to own, and how the layering keeps your stack yours.
- What Yuva is Yuva is a from-scratch, agent-native sovereign unikernel in no_std Rust, with formally verified leaves and a boot that fails closed. What it is for, how it is verified, and exactly which parts are not live yet.
- Agent identity and capabilities Every Cogitave agent acts under its own identity inside an explicit least-privilege capability grant, in a sandbox, with every action recorded as evidence. What that model guarantees, and where a human is still required.
Reference
02- Packages reference Every published Namzu package and what it is responsible for - the kernel, the sandbox and telemetry layers, the operator CLI, the file registry contracts, and the eight model provider drivers.
- Glossary The terms used across Cogitave documentation and training, defined once - agent kernel, capability grant, provider driver, sandbox, sovereign unikernel, MCP, evidence, and the words that are easy to assume.