Lacuna Labs

Docs

The work, written down. Append-only.

Each entry tracks the current shipping shape. Where a document was superseded, the prior version is preserved next to it — never overwritten. Visual Canon entries follow the arXiv refinement protocol (Ginsparg, 1991): versions increment sequentially; revisions are never removed.

Browse the full library → Every document across every Lacuna Labs repo — searchable, grouped, indexed.

Positioning

Document Contents
About Lacuna Labs What Lacuna Labs is — the canonical positioning doc. Studio shape, what we believe, the four products, how we publish.ABOUT.md current

Curator

Document Contents
Sakura pricing tool Interactive cost model for the Curator token system. Configure verb costs (on-device, cloud fast, cloud workhorse, cloud deep, MCMC), see per-tier daily burn, compare token bundles, and tune the unit price. The ground truth for what automations cost operators and what margin we earn.sakura-pricing-tool.html current
Automations catalog — browsable Every Curator automation, every tier — ~600 entries, searchable + filterable. Each entry has a Unix man(1)-shaped per-page reference: NAME · SYNOPSIS · DESCRIPTION · MECHANISM · EXAMPLES · TIER · SEE ALSO · HISTORY · KNOWN BUGS. Generated mechanically from the canonical MD. Deep-linkable — cart code, error messages, Sakura responses all land on the right page.docs/automations/index.html · per-entry: docs/automations/<id>.html current

Architecture & operations

Document Contents
Architecture overview What the system is, in ten minutes. The six substrates, the L0 / L1 / L2 stack, the data flow on every upload, the voice discipline.curator/docs/architecture.md current
Pipeline metrics + SLOs Coverage of common operations, response-time tables, "who hits what" attribution, the golden-path smoke harness, the regression alarms that block ship.curator/docs/PIPELINE-METRICS.md current
Stores scaling How Etsy’s per-token bucket and eBay’s per-application pool fit under one unified budget facade. Fair-share partitioning, burn-rate alerts, the policy field shown to operators.curator/docs/STORES-SCALING.md current
Production walkthrough The deploy switch. Prod-readiness signups, environment topology, the boring steps that move a build from green to live.curator/docs/PROD-WALKTHROUGH.md current

Lacuna Scheme

Document Contents
Lacuna Scheme — a modern Scheme for the LLM-authored, Unix-native era A long-form public document making the case for a new Scheme dialect: GPL runtime, R7RS-small baseline, capability-tier security as a first-class language primitive, LLM-agnostic with shim packs, Python interop via PyO3, Emacs as the canonical surface, message-passing workers in the Erlang/OTP lineage. Fifteen chapters, twenty-five technical reasons, embedded Scheme engine REPL slates the reader can run inline, a long historical pass on Scheme on Unix from 1958 to today, a candid post-mortem chapter, a Pitfalls chapter that names the ways this could be wrong, and a Proposed Implementation section the operator edits in place. Print stylesheet yields a clean PDF. Living document — revisions tracked in git, not in the prose.docs/scheme/index.html · v0.1 draft

Baobab

Document Contents
Baobab design document — interactive The full pitch and architecture for Baobab as a single browseable document. Cover through § 13, slide-out table of contents, print-to-PDF affordance, invite gate while in closed beta. Fourteen numbered sections: markets overview, blockchain rationale, intellectual frame, operator voice, architecture, economics deep dive, features in beta, Lacuna + workers, how-to-try diagrams, IP & patents, four-slice roadmap, one page per founding seat.docs/baobab/index.html · gated current
Baobab v1 design spec The machine-readable form of the design. Mission, audience, three pillars, entity graph, ambient AI, custodial wallet, payments rails, federated forums on Matrix, six launch languages, tier gating, four-slice plan, and a migration plan that ends with Rust Lacuna instances and our own auth.baobab/docs/specs/2026-05-11-baobab-v1-design.md current
Lacuna Worker Protocol v0.1 A language-agnostic protocol so workers in any language (Rust, Python, Go, JS) can serve as Lacuna’s hands. Workers speak Scheme on the wire; Lacuna logs JSONL at its edge. Specifies transport, message + response envelopes, R7RS-subset Scheme, threading via fork / join / channel, eight standard capabilities, and the plan-signing roadmap to v1.0.baobab/docs/specs/2026-05-11-worker-protocol.md spec v0.1
Worker reference implementations Two workers in the Baobab repo. The interim Cloudflare JS Worker (deploy-ready) runs the RSS + image-extraction pipeline end-to-end. The Rust v1 (baobab-worker-rs, scaffolded) compiles to both WASM (Cloudflare) and native binary (Fly, local), with a ~50-primitive Scheme tool registry across net, parse, cache, storage, time, threading, crypto, text, AI, and audit.baobab/workers/ interim live · v1 in flight

Visual Canon

The DID (Designed-Identity Document) family was renamed to Visual Canon (VC) per lacuna-canon-v0.4.0. Existing files keep their original paths (append-only at the filesystem level); new entries land under research/lacuna-vc-v*.md.

Document Contents
Lacuna Labs visual canon (v1.0) Designed-iconographic datasheet for the parent surface. Tri-tone Bar lockup v3, Geist Mono wordmark, palette in sRGB / CIELAB / Oklch, fidelity tiers (vector, ANSI, ASCII), Merkle manifest.research/lacuna-labs-did-v1.md canon
Lacuna visual canon (v1.0) Parent canon for the bare Lacuna mark. Living Mark Mode supported — bar segments map to telemetry channels via ANSI 24-bit color escape sequences.research/lacuna-did-v1.md canon
Canon v0.4.0 — rename to Visual Canon Locks the DID → VC rename and the scope rule going forward. Visual decisions only: palette, mark, wordmark, motion, geometry, chrome.research/lacuna-canon-v0.4.0-visual-canon-rename.md canon
Sakura UX standard Motion canon and surface canon for the Sakura subdomain. Easing library, wisp arc, card register, accessibility floor, performance ceiling.curator/docs/SAKURA-UX-STANDARD.md subdomain

Research

Document Contents
Loam — bifurcation analysis The dynamical-systems analysis behind Loam — the closed loop that turns usage into a graph that answers the next question for free. The engineering manual ships as PDF; this is the analysis it leans on.research/loam-bifurcation-analysis-v0.1.md research
Sakura cognitive map A metaphor — not a claim of mind — that keeps the substrates from drifting into chatbot orientation. Voice, prefrontal cortex, subconscious, world model, shared culture, public face.curator/research/sakura-cognitive-map-v0.1.md research