CREATE KV

Offline compiler; no publication. Fuze's Zig Declaration.compile validates this statement as a named KV definition and formats it for review. It does not provision state, choose a writer or install a decoder. SQL query interfaces reject it; CLI, Board and language SDKs have no administrative route for it.

Syntax

CREATE KV name (data_type);
data_type := INT64 | BOOL | UTF8 | BINARY

name is an identifier. Exactly one type token is required. This rule has no key declaration, initial entries, nullability, retention options or IF NOT EXISTS clause. It does not define a byte codec or an executable type binding for the resource.

Examples

These examples compile as offline definitions:

CREATE KV settings (UTF8);
CREATE KV counters (INT64);

Meaning and current interface

The form refers to a native v1 KV resource. Actual reads and mutations use the public client under current resource policy and writer ownership. Mutations share a turn's commit decision with input progress and outputs; the declaration creates no new transaction boundary.

Use growing client operations or application installation to provision and access supported state. Unified SQL needs an explicitly declared KV decoder and schema; arbitrary stored bytes are not implicitly SQL values. See query source profiles. The offline declaration contract defines owned names, complete-input validation, canonical formatting and bounds.

Source: createKv, dataType.