The operating system is the product.
The Alchemist, reusable Agents, Magnum Opuses, and Distill execution form the product trunk. Coding is one surface of that system, never the frame around it.
This is the public product contract for Lembic 0.1. It defines what the product is intended to preserve; it does not claim that every capability below is available in the current private build.
The Alchemist, reusable Agents, Magnum Opuses, and Distill execution form the product trunk. Coding is one surface of that system, never the frame around it.
The Agent Server is designed to persist independently of a shell or client. Agents, workflows, schedules, and approvals belong to the machine, not to a browser tab.
Every execution path must leave evidence. When a delegated or remote path cannot provide the full record, Lembic must identify that reduced evidence class explicitly.
Authority starts with the user and can only become smaller as it flows through the Alchemist, an Agent, an Opus node, and an individual tool call. Model output cannot widen it.
Sandboxed, evidenced, verified, and attested are different claims. Lembic states the enforcement and proof it actually has, including the limits it does not remove.
A workspace or Distill answers to one authority process at a time. Interfaces request and render; the authority process decides permissions, invokes tools, and records evidence.
An action must be attributable to its Distill, Agent definition, workflow node, grant or approval, and supporting evidence. Autonomy without an explanation is not acceptable.
Sets the machine ceiling and resolves approvals.
Authors and operates within that ceiling; it cannot expand its own grants.
Declare narrower capabilities for reusable work and each workflow node.
Receive the effective intersection for one bounded execution and one action.
Deterministically checks the evidence chain, causality, recorded authority, and lifecycle. A clean result does not prove semantic correctness or host integrity.
Asks a fresh, isolated grader whether the declared outcome satisfies the task. Its answer is a judgment with findings, not a theorem.
Reproduces the result and runs its declared mechanical contract. A green assay establishes only the check and environment that were actually declared.
Product laws describe the intended system. The status below says what that means today, without turning design work into an availability claim.
Read the 0.1 guide for the domain model, or see the build-status page for the current sequence and access posture.