Lembic is a local-first, resident system designed around the Alchemist: a main agent that authors reusable agents, composes them into Magnum Opuses, and runs each bounded execution as a Distill on hardware you own.
An always-on Agent Server may need filesystem, process, network, and tool access to do useful work.
Lembic 0.1 is designed so that authority only narrows, while every Distill leaves durable evidence of what happened and why it was allowed.
Effective grants are the intersection of every layer above an action. A model, agent, or approval can never widen them.
Agents and Magnum Opuses are versioned definitions. The Alchemist target reuses what exists before authoring something new.
The Alchemist is Lembic's designed resident main agent: primary interface, author, operator, and memory of practice.
The target is to take plain-language work, show a structured plan, author reusable agents, compose a Magnum Opus, and supervise its Distills within the user's grants.
In the target design, every agent definition persists — named, versioned, reusable. The Alchemist searches what exists before authoring something new.
Your workflows become things you own, not prompts you retype.
Proof applies to Distills by policy. C — Consistency checks the recorded evidence; B — Adjudication judges the outcome in fresh context; A — Assay reproduces and checks a declared contract mechanically.
Consistency verification is in development. Adjudication and Assay are designed, but not yet built. `lembic verify` targets C; `lembic prove` targets the fail-fast C→B→A pipeline according to policy and applicability.
Read the proof specification →Is the evidence internally consistent — chain intact, causality sound, and every action inside recorded authority?
Does the outcome satisfy the task when judged in a fresh, isolated context?
Does the result hold when reproduced and checked mechanically against a declared contract?
The 0.1 architecture centers one resident server per machine. Rust decides, executes, and records; CLI, TUI, Code, and ADE request, observe, and render through one semantic protocol.
Four rules enforced by architecture, not by discipline.
The Ultimate Dashboard, Lembic Code, and Lembic ADE are designed product surfaces that are not yet built. Proof is kernel-level: Consistency is in development, while Adjudication and Assay are not yet built. Client surfaces share identifiers but hold no execution authority.
Lembic Code is one surface of the operating system. It is not the product frame.
Lembic operates provider models and external agents. It never pretends to be them.
0.1 is local-first: one machine, one Agent Server, one human owner.
Lembic 0.1 is in private development. All first-party source is currently private and proprietary; there is no operative open-core or public-source split.
The product laws are equally direct: the OS is the product, authority only narrows, evidence precedes convenience, and every guarantee must say exactly what it can prove.
Development updates