Skip to content
Raw Markdown
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, or an app-managed project where you can edit the context. If domains, tables, and metrics are new to you, first explore a real context.

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.

Review 3 open issues
Analyze conversations
Unreliable answer Context gap Seen in 2 conversations · Jul 18 to Jul 25
"Top sellers" has no agreed ranking basis
Two conversations asked for top sellers, one meaning delivered business volume and one meaning order count. The context doesn't define a default ranking, so the agent had to caveat each answer with the basis it chose.
Occurrences (2)
Chat · Jul 18 chat_message
"Who are our top sellers this quarter?" → answered on delivered business volume, with a caveat that another basis was possible.
Chat · Jul 25 chat_message
"Top sellers by number of orders?" → answered on order count. Same phrase, different measure.
Fix proposal
manual needs input
No resolution was provided in the source conversations. Suggested action: state on DIM_SELLER that seller rankings default to delivered business volume, and add order-count ranking as an explicit alternative phrasing.
▶ Fix in chat ✕ Dismiss

2. Ask the Assistant to fix it

Choose Fix in chat and provide the rule:

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.

Context assistant · issue attached: "Top sellers" has no agreed ranking basis
On DIM_SELLER, state that seller rankings default to delivered business volume, and note that ranking by order count is an explicit alternative a question has to ask for.
That resolves the ambiguity in both conversations. Here is the change I propose:
Update table description
One edit, on the table both questions routed through.
Object STALLORA.DIM_SELLER
Rankings of sellers default to delivered business volume (GMV of delivered orders, excluding freight). Ranking by order count is a different question and must be asked for explicitly.
✓ Approve Reject
Approving stages the edit. It affects no answers until the unpublished changes are published.

3. Review the diff

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

Unpublished changes Discard all ↑ Publish changes
Tables~1 modified
→ STALLORA.DIM_SELLER modified Description
One row per seller on the marketplace. + Rankings of sellers default to delivered business volume (GMV of + delivered orders, excluding freight). + Ranking by order count is a different question and must be asked + for explicitly.
Label: Default seller ranking to delivered business volume

4. Publish and verify

  1. Publish the unpublished 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. A fix that ships through a pull request closes its issue on merge instead, see Review detected issues.
Small change
Work directly in the unpublished changes.
Larger change
Create a Cassis branch, make and test the edits there, then merge it.

Do not edit a git-managed context 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.