10 min

# Curate an app-managed project

Open an issue, decide the missing business rule, review the Assistant's proposed edit, and publish only after the diff is correct.

Use a [demo project](/start/try/), or an app-managed project where you can edit the ontology. If domains, tables, and metrics are new to you, first [explore a real ontology](/start/ontology/).

## 1\. Open the issue

In **Review**, choose **“Top sellers” has no agreed ranking basis**. Its two occurrences used different ranking definitions, so the answer was unreliable.

This seeded demo issue deliberately has no proposal. The evidence does not establish what “top” should mean; someone who knows the business must decide.

## 2\. Ask the Assistant to fix it

Choose **Fix in chat** and provide the rule:

```text
On DIM_SELLER, state that seller rankings default to delivered business volume.
Ranking by order count must be requested explicitly.
```

The Assistant shows the object it will change and the proposed text. Nothing is applied until you approve it.

## 3\. Review the diff

Approve the proposal, then open **Pending changes**. Expand the line diff and verify that it adds one clear default without changing unrelated context.

## 4\. Publish and verify

1.  Publish the pending changes with a clear version label.
2.  Ask “Who are our top sellers?” again and confirm the answer uses delivered business volume.
3.  Capture a candidate eval case, then have a reviewer validate its SQL and business interpretation.
4.  Resolve the issue only after the published version contains the fix.

- **Small change** Work directly in pending changes.

- **Larger change** Create a [Cassis branch](/curate/branches/), make and test the edits there, then merge it.

**Do not edit a git-managed ontology here.** Review and triage in the app, but make the change in the repository so concurrent full-tree imports cannot overwrite one another.

For the repository equivalent, see [Curate a git-managed project](/curate/agent/).