What nvoken supports

nvoken combines the pieces around a model call into one durable runtime:

• owner-namespaced Agents with immutable, publishable revisions;
• inline behavior for one-off work;
• durable Turns with idempotent admission, checkpoints, controls, and recovery;
• optional tenant- or user-owned Conversations;
• optional user or tenant-namespaced MemorySpaces;
• host, callback, MCP, and built-in tools;
• live Turn and Conversation streams with resumable cursors;
• structured output, model discovery, and cross-provider routing;
• usage attribution, credits, narrowed per-Turn limits, traces, and logs;
• machine credentials, browser grants, anonymous access, and signed deliveries.

These features preserve one boundary: your application owns product data, membership, authorization, and product-level orchestration. nvoken executes the accepted Agent work and records what happened.

Every Turn selects exactly one stored Agent revision or one inline behavior snapshot. Conversation continuity and MemorySpace selection are independent and optional, so standalone execution, shared conversations, and shared memory do not require synthetic resources.