Workspaces

Workspace folder is the delivery boundary

Looky CLI resolves context from your current directory. Wrong directory means wrong workspace identity, wrong billing context, and unreliable push results.

Required directory shape

<local_root>/
  <billing_account_id>/
    <workspace_slug>/
      workspace.yml
      content/
        models/
        visualizations/
        dashboards/
        exports/
      runtime/
        sources.runtime.yml
      secrets/

How to verify workspace context quickly

Move to workspace root:

cd <local_root>/<billing_account_id>/<workspace_slug>

Run:
```
looky status
looky validate
```
Confirm workspace id is <billing_account_id>/<workspace_slug>.
Open workspace.yml and confirm id matches folder slug.

Deleting a workspace

Run looky delete <workspace_slug> from <local_root>/<billing_account_id>. The CLI prompts for the slug as a confirmation; pass --yes to skip the prompt in automation.

Who can delete:

Billing-account owners can delete any workspace under their billing account.
super_admin can delete only workspaces that they themselves created.
Billing-account developers cannot delete workspaces — even ones they created. Deletion is a billing-owner decision.

What gets removed on the server, atomically:

The workspace directory under workspaces_root/<billing>/<slug>/ (workspace.yml, content, runtime, secrets, runtime caches).
Any in-flight or zombie validation staging under workspaces_root/.validation-staging/<billing>/<slug>/.
Database rows in auth_workspace_owners, auth_workspace_memberships, auth_invitation_workspace_grants, catalog_items, ui_user_folders, and ui_user_folder_items.

What stays:

Your local copy under <local_root>/<billing_account_id>/<workspace_slug>/. The CLI leaves it in place and prints an rm -rf hint so you decide when to remove it.
Outstanding invitations that grant access to the deleted workspace stay valid for any other workspaces they grant — only the row for this workspace's grant is removed.

There is no soft-delete or undo. Re-creating the workspace requires looky create followed by a fresh looky push.

What breaks when structure is wrong

looky validate may fail to resolve local workspace.
looky push may target wrong workspace id.
looky list dashboards may show unexpected workspace results.

Three directory tiers, enforced by the CLI. Commands that create or delete a workspace run one level above the workspace folder, because the folder either doesn't exist yet (create, pull) or is about to disappear (delete).

From <local_root> exactly — looky billing list/use, looky workspaces. Running them in a subdirectory is rejected.
From <local_root>/<billing_account_id> — looky create, looky pull, looky delete.
From any subdirectory under <local_root>/<billing_account_id>/<workspace_slug> — everything else (status, validate, diff, push, list, sources). The CLI walks up the path to infer the workspace root, so content/models/ works too.