Product decisions, development status, and the distinction between what the 0.1 design promises and what the current build can do.
Lembic restarted from one constraint: a coding surface cannot be the product trunk. The resident Agent Server, the Alchemist, owned agents, Magnum Opuses, and Distills now define the center; every interface stays a surface.
The resident service, protocol, storage, and workspace foundation are taking shape in a private build. The system is being built to outlive shells, clients, and reboots, but it is not yet available as a public release.
Provider connections, native tools, grants, evidence, recovery, permissions, scheduling, the engine loop, and context compilation form the current foundation. These capabilities are still being integrated and tested together.
Every capability begins with the owner and flows down through the Alchemist, an agent, an opus node, and a tool call. The effective grant is the meet of every layer. Nothing emitted by a model can widen it.
Native, delegated, scheduled, and eventually remote work all produce an append-only, hash-chained evidence log. Different execution paths may carry different evidence classes, but none may silently claim more than it recorded.
The designed Alchemist turns the foundations into the thing a user talks to: take real work, author a reusable agent, design a Magnum Opus, pause at an approval, complete a Distill, then reuse the same definitions later. It is not yet built.
Read the product guide for the 0.1 direction, or the build-status page for current availability and designed capabilities.