Skip to content

feat(ixp): guide the confirm --model-version version guard [ACTV-89481] - #2548

Draft
cezara98t wants to merge 3 commits into
mainfrom
feat/ixp-confirm-version-guard
Draft

feat(ixp): guide the confirm --model-version version guard [ACTV-89481]#2548
cezara98t wants to merge 3 commits into
mainfrom
feat/ixp-confirm-version-guard

Conversation

@cezara98t

Copy link
Copy Markdown
Contributor

What

Teaches the IXP labelling flow to use the new confirm version guard:

  • Capture ModelVersion from get-predictions (step 2a).
  • Pass it as confirm -m/--model-version (step 2d) — a retrain landing between the read and the confirm can't stamp drifted predictions as ground truth; the server rejects with PredictionVersionChangedError instead.
  • On that rejection: re-read get-predictions, re-review, confirm against the new version.
  • New Critical Rule 19; cli-reference get-predictions + confirm rows updated.

⚠️ Gated on CLI release — merge after the flag ships

-m/--model-version on confirm ships in UiPath/cli#3539 (stacked on the ModelVersion-on-get-predictions PR). Merge this only after that CLI release — otherwise agents on the current CLI hit an unknown flag. Draft until then.

Server side

The guard itself is UiPath/DU-App#35850 (returns 409 [PredictionVersionChangedError] when the pinned version drifted).

Follow-up

A command-shape smoke task (grade that the agent passes --model-version) is a good follow-up — mock-based, so it can land independently of the CLI release.

🤖 Generated with Claude Code

Teach the labelling flow to capture ModelVersion from get-predictions and pass
it to `confirm -m/--model-version`, so a retrain mid-review can't stamp drifted
predictions as ground truth. Adds Critical Rule 19, the 2a capture note and 2d
guidance in the label-documents guide, and the cli-reference get-predictions +
confirm rows. Gated on the CLI flag release (UiPath/cli#3539).
"step 2a"/"step 2d" cross-refs; "change the values confirm stamps" instead of
"swap" (values drift, they don't swap).
The per-document flow always has the doc's ModelVersion, so always pass -m; and
bulk confirm-all is already forbidden by the guide — no reason to carve it out.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant