index.md
August 1, 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.
Workbench · SDK · CLI · MCP
Agents keep familiar list/read/search/commit/snapshot/restore behavior while storage internals change underneath.
Canonical paths in Holt
Workspace incarnations gate visibility. Full relative paths are authoritative ordered keys; indexes remain derived.
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
Agent SDK
-> route RootId to one logical shard
-> allocate publish operation + immutable revision
-> stream and verify object blocks
-> one fenced Holt command publishes:
path + revision + references + indexes + event + replay resultDocumentation 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, LingTai Workbench Preflight, and Workspace Acceptance.
- Development: Code Contract,
nokv-agentHandbook, PR Review Checklist, and Path-Native Metadata Comparison. - Collaboration record: NoKV x LingTai and Chinese version.
First client
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.