The product

A workspace is a committed manifest, workloom.workspace.json, that binds one repository or folder. It lists one or more targets (paths inside the workspace), and each target selects its providers and packages. A monorepo has one target per package path.

The manifest also carries a projection policy, a telemetry policy and a CI policy. `wl validate` checks it against the schema and then runs the trust gates over a render plan.

Render is side-effect free. For each target and provider pair it produces a render plan: every planned file with its path, content hash, projection policy, ownership and write mode, plus diagnostics.

The same manifest and packages give the same plan every time, because content is addressed by SHA-256.

Sync applies a render plan through trust-gated, atomic, ownership-checked writes and records each written file in the drift baseline. Workloom changes or removes only files it owns.

Drift is any difference between disk and that baseline. `wl status` and `wl diff` show it, `wl restore` rewrites drifted Workloom-owned files, and `wl sync --check` writes nothing and exits non-zero on drift.

The `wl` CLI is the main surface. The registry API (Hono, OpenAPI 3.1) holds packages, profiles, workspaces, content objects, the audit log, telemetry, webhooks and service accounts. The web console is for browsing the registry, moderating package versions, inspecting workspaces and drift, reading telemetry and administering an organization.

The desktop app (Tauri) runs the same workspace operations through one bundled sidecar: bind a folder, then see status and diff, render, sync and restore.