Keyboard shortcuts

Press ← or → to navigate between chapters

Press S or / to search in the book

Press ? to show this help

Press Esc to hide this help

Native services and packaging

Requirements

IDRequirement
LAI-LOCAL-001The maintained Buzz-derived agent MUST retain provider adapters, permission gates, model discovery, metadata summaries and token-source support with complete Apache attribution and source pins.
LAI-COMPUTE-001Compute MUST retain authenticated loopback inference, explicit model preparation/download/import/start/stop, bounded limits and mutually admitted inference-only peers. Sharing defaults off and startup never downloads.
LAI-COMPUTE-002Lapis compute MUST preserve the jj-store/compute/1 ALPN, invitation representation and request/response semantics. Mixed-version acceptance MUST use isolated pinned legacy helpers.
LAI-PACKAGE-001Staged local bundles MUST include production executables, licenses and a TOML manifest with target, versions, hashes and native ABI pins. Test executables, secrets and model weights MUST be excluded.
LAI-PACKAGE-002macOS ARM64 and Linux CPU acceptance MUST separately prove cold native inference and an approved ACP tool operation. Unavailable prerequisites MUST leave their gates pending.

Initial inference remains non-streaming. No cross-application singleton, public discovery or automatic cloud fallback is introduced. Consumer migration remains separate. Hosting and release automation follow the release contract. The Cargo and native-runtime pins remain exact.

Cargo packages retain the agent capability manifest and normative corpus inside crates/lapis-agent/data/. Relocation changes no bytes, capability rules, provider behavior or wire contract (LAI-LOCAL-001); required package inputs travel together.

The agent declares its Reqwest query feature explicitly so provider pagination compiles outside the workspace. This preserves the already qualified request behavior and removes an accidental dependency on compute feature unification.

The canonical GitHub owner is now lapismd. Service documentation and Cargo metadata follow this identity; providers, native pins and wire contracts remain unchanged (LAI-LOCAL-001, LAI-COMPUTE-001–002).