EnoughFactory 0.1.2

EnoughFactory 0.1.2 improves upgrade handling and the first-run experience, and adds a small working project you can use to try the factory.

• Version-aware local state. The device service upgrades the supported unversioned baseline in a transaction and validates existing records and event storage. A newer database schema or malformed version/baseline stops startup with a clear recovery message instead of silently rewriting the schema.
• A working example. examples/status-board is a Node HTTP application with no npm dependencies. Its current envmux configuration starts a scoped Valkey cache, runs checks before the web task, and exposes the status page in Preview. The README explains how to make it an independent repository and gives a goal with concrete completion criteria.
• Clear browser onboarding. A first visit to the hosted workspace asks you to connect or pair a device. It does not poll an unselected website API or display an HTML error document. Local development keeps its API proxy.

EnoughFactory brings isolated envmux environments, terminals and previews, coding-agent conversations, connected devices and durable autonomous goals into one open-source EnoughUI workspace. Container permissions, approval policy and goal autonomy are separate controls.

The real distributed factory receipt records a completed Codex goal with a Mac coordinator and a native Linux ARM64 worker in an application-owned VM on the same physical Mac. Source and candidate artifacts crossed authenticated direct WebRTC. The candidate survived a coordinator restart, integrated exactly once at 3fb317c8587b611cd830d3f3e0f9655ed32db002, and satisfied all ten retained completion criteria. Five private-engine checks passed, including 21 CLI behavior cases.

That journey used the immutable 0.1.2 service over verified 0.1.1 native assets, whose original provenance is retained. Final downloadable archives have their own native verification records. A separate deterministic typed-callback fixture verified automatic Enough policy decisions and Codex response mappings over WebRTC. The real full-access Codex goal emitted no native approval requests. Exact topology and evidence scope.

Choose the download for Mac Apple Silicon, Linux x64 or Linux ARM64. These desktop packages are unsigned; Mac builds are not notarized. Linux's private rootless engine needs the host helpers, subordinate ID ranges, user session and, on affected Ubuntu installations, executable-specific desktop sandbox setup described in the installation guide.

Each package includes EnoughFactory's own container engine, private socket and storage. Mac also bundles its pinned Ubuntu guest. Bring your own repositories and provider accounts; model usage is not included. Git remains a host prerequisite. Chats and live tools stay on their owning device and are unavailable while that device is offline. ArtifactFS execution is available on compatible Mac workers; Linux uses Git workspaces. Selective approvals depend on the typed requests exposed by the selected provider adapter.

The release assets include archive checksums, exact-package verification records, native runtime/desktop/login-service evidence, per-target engine source and relink companions, and all seven Ubuntu corresponding-source files. Keep the source companions available when redistributing the installers.

Website and downloads · Installation guide · Status-board example · Source