Stdlib Primitive Registry

The current v0.5 registry exposes 24 primitive entries. Pure helpers require @caps(); time, filesystem, and network primitives require explicit authority.

This is a registry reference, not a promise of a mature standard library. Higher-level HTTP, JSON, package, async, and data APIs remain future library work.

Primitive Table

Name	Arity	Caps	Description
time::now_ms	0	time	Monotonic clock in milliseconds since process start.
time::wall_clock_ms	0	time	Wall clock in milliseconds since UNIX epoch.
time::sleep	1	time	Sleep the current thread for N milliseconds.
str::split	2	@caps()	Split a string on a delimiter; returns an Array<String>.
str::replace	3	@caps()	Replace all occurrences of old with new.
str::to_lower	1	@caps()	Lowercase a string.
str::to_upper	1	@caps()	Uppercase a string.
str::trim	1	@caps()	Trim whitespace from both ends.
str::starts_with	2	@caps()	Return true if the string starts with the prefix.
str::contains	2	@caps()	Return true if the string contains the substring.
array::insert	3	@caps()	Insert value at index; shifts following elements right.
array::remove	2	@caps()	Remove and return the element at index.
array::sort	1	@caps()	Sort the array in-place.
crypto::blake3	1	@caps()	BLAKE3 hash of a byte sequence.
crypto::sha256	1	@caps()	SHA-256 hash of a byte sequence.
crypto::hmac_sha256	2	@caps()	HMAC-SHA-256 of a byte sequence with a given key.
fs::read_file	1	fs	Read a UTF-8 file as String.
fs::write_file	2	fs	Write a String to a file, creating or truncating.
fs::read_bytes	1	fs	Read a file as Bytes.
fs::write_bytes	2	fs	Write Bytes to a file, creating or truncating.
fs::list_dir	1	fs	List entries in a directory.
net::tcp_connect	2	net	Open an outbound TCP connection.
net::tcp_listen	1	net	Open a TCP listener on a local port.
net::udp_bind	1	net	Bind a UDP socket on a local port.

What Is Still Missing

A production-feeling language needs more than this registry. The next useful layers are JSON, HTTP client/server helpers, regex, UUID, datetime, structured logging, configuration, package manifests, and richer test helpers. Those should land behind the same capability discipline, with examples and dogfood evidence beside the implementation.