Operational Library Reference

This page catalogs the ordinary seed packages staged by the operational LLVM compiler from seed/compiler/llvm/libs. It does not treat every directory in the top-level Grove compatibility tree as a current package.

Import and build model

Repository core packages use bare imports:

use "io"
use "parse"
use "vec"

The launcher's incremental build and run paths resolve these names, build profile/target-compatible native and .sdi artifacts, and reuse exact installed generations. The narrower check subcommand currently invokes direct source checking and does not stage a missing bare package first. An explicit --static build selects matching static seed dependencies; ordinary hosted linking uses the profile-compatible dynamic artifacts by default.

Availability remains constrained by each package manifest and the canonical target capability matrix. A package being present in the source tree does not add runtime services to a target that lacks them.

Package catalog

Application packages in the top-level Grove tree include std-uuid 0.2. It provides allocation-free UUID text validation, strict RFC 9562 UUIDv7 validation, deterministic uuid_v7_from_parts, and fallible uuid_v7 generation backed by hosted wall-clock milliseconds plus 74 bits from the audited operating-system entropy package. UUIDs remain identifiers rather than credentials.

Ownership and error conventions

Operational packages follow the language ownership model:

• constructors that allocate return Result<T, alloc_error> or AllocResult<T>;
• owned values move and run their destructor exactly once on structured exits;
• borrowed str and slice results preserve receiver/input provenance;
• @mut receiver methods hold exclusive call-scoped loans and persist changes in the caller;
• explicit consuming helpers transfer ownership rather than hiding clones;
• raw pointer construction remains unsafe, even when later methods are safe because the wrapper preserves the audited invariant;
• recoverable I/O and parsing failures use package ADTs rather than sentinel values or implicit process termination.

I/O

New code should prefer io over the narrower file compatibility wrappers. The important distinction is partial input:

• input_stream.read(mut []u8) returns a typed data/EOF count;
• stdin_read_all() is available when retaining the complete input is desired;
• output operations distinguish one write from write_all;
• f-string format_args can be written directly without allocating an owned string.

byte_buffer and io share the initialized-prefix contract. Safe callers never observe spare uninitialized capacity.

Grove command execution

The Grove command package provides bounded argv-based child execution for hosted applications. command_run_configured_with_stdin_file has the same working-directory, environment, timeout, and capture-limit contract as command_run_configured, and additionally connects an existing regular input file to the child's standard input. The file is opened without following a final symlink and all parent/child descriptors retain exact cleanup. This is useful for bounded stdio protocols such as language servers without invoking a shell or retaining a second in-memory copy of the framed request.

Collections and slices

vec<t> is the canonical growable generic sequence. It provides fallible capacity and push operations, checked update/pop, read-only and mutable views, and exact cleanup for move-only elements. Queue, set, and map types use the same ownership model.

Native []t and mut []t remain the standard borrowed sequence types. The slice package adds algorithms; checked indexing, slicing, fill, copy_from, and split_at_mut are core operations rather than a legacy raw fat-slice wrapper.

Tasks

task is an ordinary package, not a set of language built-ins. It provides:

• ownership-split bounded channels;
• typed one-shot joins and Result<T, E> task results;
• events and cancellation;
• waitgroups, semaphores, barriers, and locks.

Endpoints and tickets retain their linear/exact-cleanup contracts. Direct spawn remains lexically structured, and postfix ? cannot cross the spawned body boundary while that body ABI returns void.

Systems package

system targets declared freestanding profiles. Raw addresses, MMIO pointers, atomic storage, pinned buffers, DMA buffers, and allocator backing storage are created through unsafe constructors. Safe methods rely on those constructors' alignment, lifetime, address-space, synchronization, and ownership obligations.

Presence of this package does not imply that all hosted or freestanding targets provide every system service. Consult System Primitives and the Gate 14 target matrix.

Grove package inventory

The top-level grove/libs/ corpus completed G01–G22 classification: 218 manifested packages are covered exactly once by the Grove gate harness. Ported packages expose current source-elided interfaces; archived packages expose only their documented validation/unavailability boundary. See Grove Compatibility Tree and Library Roadmap.

Operational network client packages

The full limits and target evidence are recorded in the G12 and G14 baselines.

Operational adaptive UI remote-update packages

The cache does not implement conditional HTTP validators, expiry, eviction, shared quota, encryption, or background maintenance. Native macOS ARM64, Linux x86-64, and Windows x86-64/Wine debug/release evidence is frozen by the update and trust-distribution baselines.

Ridge v0.3 packages

The completed Ridge v0.3 local-database stack is split into ordinary Grove packages:

These are bounded local-database contracts, not PostgreSQL parity or cluster services. See Ridge Database and the Ridge capability document for the exact supported shapes and exclusions.

Sources of truth

• package source and manifests: seed/compiler/llvm/libs/*/;
• compiler-known operations: Core Built-ins and Standard Libraries;
• ownership contracts: Ownership;
• implementation and target limits: Current Status.