index.md

August 29, 2026 · View on GitHub

Product boundary

Artifact semantics for Agents, without POSIX baggage

NoKV gives datasets, scripts, logs, outputs, reports, checkpoints, and provenance stable path-shaped identities. It intentionally does not target FUSE, complete POSIX, CSI, or transparent fsspec access.

Application surface

CLI · Python SDK · Rust SDK

Downstream skills use the native CLI by default; embedded callers use the Python SDK, and native integrations use the Rust SDK. All three share the same 18-tool semantics.

Metadata layer

Canonical ordered paths

Workspace incarnations gate visibility. Full relative paths are authoritative ordered keys; indexes remain derived.

Body layer

Revision-owned objects

Immutable blocks live in S3-compatible storage. Strong references, epochs, and fenced GC make sharing and restore safe.

Core flow

Upload bytes first; publish identity last

Native CLI or direct Python SDK
  -> route RootId to one logical shard
  -> allocate publish operation + immutable revision
  -> stream and verify object blocks
  -> one fenced metadata command publishes:
       path + revision + references + indexes + event + replay result

Recovery is explicit. Leased snapshots pin MVCC history. Durable commits retain exact revisions. Restore stages a new Workbench incarnation and reveals it only after a verified member seal.

Documentation Map

Product and interface: Product Design, Architecture, and Workbench Contract.
Storage and distribution: Metadata Schema, Object Layout, and RustFS Provider Profile.
Workloads and evidence: AI Training Workload, Benchmarks, Live Deployment Preflight, and Workspace Acceptance.
Development: Code Contract, nokv-agent Handbook, PR Review Checklist, Change Governance, and Path-Native Metadata Comparison.
Storage architecture: Metadata Store Interface.
Collaboration record: NoKV x LingTai and Chinese version.

Research workflow

Reproducible reconstruction runs

Seal one immutable input dataset, materialize verified files for the local scientific executable, collect declared outputs, and compare multiple runs through shared lineage and metadata queries.

Read the contracts before the code

The Workbench contract fixes the upper behavior. The metadata schema fixes storage safety, and the acceptance plan defines the evidence required for release.

Workbench contract → Metadata schema Acceptance plan Path model comparison