How it works

The loop has six steps: publish, declare, bind, pull and sync, apply to home, and check drift. Here is each one, with the command that does it.

Step 1
Publish
`wl push <path> --package @scope/name` publishes a local asset directory as a new package version. The secret scan runs first, and `--draft` keeps the version out of the published set.
Step 2
Declare
In the dashboard or the API, give a workspace its targets: which packages at which version constraints, for which providers, written to the project or to home. Each change is a new workspace revision.
Step 3
Bind
`wl init` or `wl bind --workspace <id>` links a local directory to that workspace and its registry.
Step 4
Pull and sync
`wl pull` fetches the current revision, resolves it into the lock file, renders each provider’s files and writes the ones Workloom owns or may create. `wl pull --dry-run` prints the plan first.
Step 5
Apply to home
`wl home diff` previews and `wl home apply` writes a home profile into your home directory, inside the home allowlist. `wl home install` adds a single published package without a binding.
Step 6
Check drift
`wl diff` and `wl sync --check` report drift from the desired state, `wl restore` puts Workloom-owned files back, and `wl keep-local` keeps a deliberate local edit as a user override.

One desired state for every repo and every laptop

Publish your organization’s AI workflow content once, declare where it goes, and let `wl sync --check` tell you when anything drifts.