Build Workflow

The only workflow order that scales

Looky is deterministic when you build in this order. If you invert steps, you get ambiguous failures and slow delivery.

1. Workspace structure and context are correct.
2. Runtime source aliases are defined and valid.
3. Malloy models expose stable query contracts.
4. Visualizations map query fields to renderers.
5. Dashboards compose validated visualizations.
6. Validate, diff, push, and verify in UI.

Reference implementation you can inspect

If available in your account, pull ecommerce-showcase and inspect it as the canonical chain:

• runtime/sources.runtime.yml defines source alias ecommerce.
• content/models/*.malloy defines reusable dimensions/measures/queries.
• content/visualizations/*.yml binds model queries to chart/table configs.
• content/dashboards/*.yml composes visualizations into final surfaces.

Builder loop you should run every day

cd <local_root>/<billing_account_id>/<workspace_slug>
looky status
looky validate
looky diff
looky push
looky list visualizations
looky list dashboards

Run this loop for every meaningful change. It catches structural issues before users see broken dashboards.

Definition of done for a content change

• looky validate has no blocking errors.
• looky diff only shows intended files.
• looky push succeeds on target workspace.
• Dashboard is visible and renders correctly in https://my.looky.studio.