Publishing changes

There is no separate "Draft branch" you push and no pull request to merge. In Celiq today, you edit CML directly in Forge, run it through the Check & Save gate, and the moment a save succeeds the file becomes the live model. Discover queries and Orion answers immediately reflect what you saved.

This page explains the gate, what each verdict means, who can do what, and exactly how a saved file reaches Discover and Orion.

Overview

Saving in Forge is deliberately not a one-click write. When you click Check & Save, Celiq runs a short pipeline of semantic checks over the parsed CML — the same way a CI run gates a code merge — and only then decides whether the save proceeds.

The checks resolve one at a time in a small panel titled Semantic Check, then the panel shows a single verdict:

• Semantic Check Passed — the file saves automatically.
• Passed with warnings — you choose Save anyway or Review warnings.
• Blocked — the save is held until you fix the issue or a Luminary overrides it.

A successful save writes the CML to the node or domain in your project. That stored CML is the live semantic layer — there is no second promotion step. Every Reveal, Prism, and Mosaic tile in the workspace queries against it, and Orion reads it when answering questions.

When to use it

Use the Check & Save gate whenever you have edited a node or domain and want the change to take effect:

• You added or changed a metric, attribute, or join.
• You edited a domain's reveals, filters, or relationships.
• You imported or regenerated nodes and want to commit the result.
• You fixed a CML error flagged by Validation.

You do not need the gate to preview your edits — the editor shows parse state and the graph/lineage views as you type. The gate is the step that makes the edit live.

Concepts

Getting started

• You are a Weaver or Luminary. Tracers and Lens users cannot edit or save model files.
• You have a project open in Forge with a node or domain selected.
• The project is not a system project — system projects (such as project.celiq) are read-only and do not show the Check & Save button.

1. Go to Forge and select your project.
2. Open a node or domain file. Make sure you are in Build mode.
3. Make your edits in the editor.
4. Click ✓ Check & Save in the toolbar (top-right of the editor for domain files).

Step-by-step

Examples

Suppose you add a total_revenue metric to your orders node:

node: orders
physical_table: analytics.orders
date_column: created_at
attributes:
  - name: status
  - name: customer_id
metrics:
  - name: total_revenue
    intent: sum
    column: amount
    owner: weaver@yourco.com

When you click Check & Save:

• Validation passes — the CML parses and the structure is valid.
• Performance passes — there is no fanout risk and a date column is present.
• Governance passes — the metric has an owner. (Metrics without an owner lower the governance score and can produce a warning.)
• Lineage and Impact pass.

The verdict is Semantic Check Passed, the file auto-saves, and total_revenue is immediately available in Discover and to Orion.

Now suppose the same metric sums a value across a many-to-many join, creating a fanout that would inflate the total. The Performance row fails and is blocking, so the verdict is Blocked: Revenue Fanout. The save is held. You click Fix & Re-run, apply the suggested fix, and the gate re-runs — once Performance passes, the save proceeds.

Best practices

• Give every metric an owner. An unowned metric drags down the Governance score and surfaces as a warning at save time. Setting owner keeps your saves clean.
• Fix fanout instead of overriding it. A blocking fanout means the metric can return inflated numbers. Prefer Fix & Re-run over overriding so the live model returns correct values.
• Watch the Impact row on widely-used files. When a domain feeds many Mosaics, the Impact check warns you that the save affects a lot of downstream tiles and users. Review before saving.
• Save in small, coherent edits. Because saving is the publish step, smaller saves make it easier to see what changed in Discover and to roll back conceptually if a number looks wrong.
• Regenerate Orion context after structural changes. Adding nodes can auto-trigger context regeneration; for larger reshapes, regenerate context so Orion's understanding stays current.

Tips

Common mistakes

Troubleshooting

Related pages

• Validation — the checks behind the gate and how to clear failures.
• Forge — authoring nodes and domains in CML.
• CML reference — the syntax for the files you publish.
• Discover — where your saved model is queried.