Skip to content

feat(uipath-ontology): build ontologies as local solutions [DS-9944] - #4432

Open
diwakar-jha3110 wants to merge 17 commits into
mainfrom
feat/ontology-onboarding
Open

diwakar-jha3110 wants to merge 17 commits into
mainfrom
feat/ontology-onboarding

Conversation

@diwakar-jha3110

@diwakar-jha3110 diwakar-jha3110 commented Nov 5, 2026 •

Copy link
Copy Markdown

Jira: DS-9944

Summary

Adds one skill, uipath-ontology, that builds a UiPath ontology as a local solution, driven only by the uip CLI, and teaches uipath-solution to deploy a solution that carries one.

  • uipath-ontology: from an SDD/PDD or design document, a plain-language domain, or existing artifact files, models the domain and builds the solution: local Data Fabric entities, relationships, choice sets and federated entities (uip df … --local), the ontology artifacts (OWL schema, YARRRML mapping, optional summary and context) checked with uip ont artifacts check <path>, the ontology resource (uip ont create --local), validation (uip ont validate --local), the attached zip (uip ont files add), then uip solution pack. It stops after pack. Nothing is created on a tenant before deploy.

  • Constraints are optional. The ontology service retired SHACL constraints (UiPath/ontology a32d5f1ff): it stores them without parsing or using them, and a package needs none. The skill writes a constraints file only when the user supplies one or asks; required, range and value-list rules go in the schema's rdfs:comment. The eval tasks no longer require one.

  • Document mode (references/document-guide.md): reads an SDD/PDD/design document and confirms the model one table at a time (concepts, properties and relationships, labels). Refused entity names (Order, Group, C#/VB keywords) are caught while the user approves, and a FILE field's upgrade cost is told before it is confirmed. This was a separate uipath-ontology-authoring skill until review: one skill keeps the repo's self-contained rule and needs no handoff form or copied rules.

  • Saved model: the confirmed model is written to <WORKDIR>/input/model.md with a CONFIRMED_THROUGH step, every later fix goes into it first, and a folder holding it is resumed in a new session.

  • uipath-solution (pack-and-deploy.md, develop-solution.md): deploying an ontology solution, ontology name conflicts (Replace / RenameInSolution), and which properties a deployer can edit (name, displayName, description). The folder-scoped entity flow for other solutions (uip df entities create --folder-key, then resources add --source remote) is unchanged.

  • The attached ontology zip lives under resources/files/ (the layout from UiPath/Automation.Solutions#10268); the skill never writes there by hand.

  • Studio Web: not available by design. The Studio Web flavor stops with a "use the local uip CLI" message before any file or command; ontologies are built only with the local CLI. Non-ontology PDD/SDD requests still go to uipath-planner there.

The skill is preview in assets/skill-status.json; skills.sh.json and CODEOWNERS are updated.

Depends on (do not merge before)

  • UiPath/cli#5710 (uip ont): merged into cli/main. UiPath/cli#5798 (Data Fabric --local choice sets, reference fields and federated entities) and UiPath/Automation.Solutions#10268 (attached resource files) have merged; #5710 carries the resource builder build that packs the attached zip.
  • UiPath/gitops-centralized-cluster#612233 for deploying an ontology on alpha.
  • UiPath/cli#6194: maps the new skill name uipath-ontology in CLI telemetry (SKILL_ATTRIBUTION). Not a merge blocker: until it ships, uip ont calls from this skill carry no SkillName.

Remaining blocker

The CLI verb gate (and its per-skill skills/uipath-ontology / skills/uipath-solution jobs) and Run skill smoke tests fail until uip ont is in the @dev CLI on GitHub Packages, which both read: the verb gate through assets/uip-catalog-snapshot.json, the smoke image directly. cli#5710 has merged, but cli/main can't publish a -dev CLI until UiPath/cli#6173 clears the repo-wide picomatch audit failure. After that, a -dev build with ontology-tool is published, the nightly refresh-uip-catalog run adds uip ont to the snapshot on main, and a re-run of these checks clears them. No stable uip release is needed.

Every other check should be green.

Testing

  • tests/scripts/test_ontology_skill_contract.py: 69 passed. It pins the stage order, the commands each stage runs, the error table, Document mode and the saved model, and that nothing of the old two-skill split is left.
  • tests/scripts/test_ontology_solution_golden.py, run against a build of cli#5710 (published SDK 1.8.4 and resource builder): the golden SalesOrder/Customer flow (choice set with values, a CHOICE_SET_SINGLE field, a RELATIONSHIP, a federated entity over a native one, the five artifacts (the fixture supplies a constraints file, as Files mode allows), each checked with uip ont artifacts check <path>, XF-019 fix loop, files add, service validation on alpha, pack, ont files list --package) passes, and checks the packed resources and their dependencies[]; a class mapped over the federated entity validates. It needs a uip build with cli#5710 (stable or preview: every uip ont command ships on stable builds); with an older build, which has no uip ont create, the test skips.
  • coder_eval tasks, all under uipath-ontology: smoke_artifacts_only, e2e_pack, smoke_sdd_document and e2e_sdd_to_pack. The two SDD tasks check that input/model.md is saved; the smoke SDD names an entity Group (must be renamed before any create) and has a FILE field. Not run yet after the merge: they need the @dev CLI with uip ont (see Remaining blocker). Besides the CLI checks, three of them grade the schema's classes with check_ontology.py classes: each class is declared, labelled, commented and the domain of a property (the smoke task by name, the e2e tasks by count).
  • tests/scripts/test_check_ontology_classes.py: 13 passed, against the golden schema and broken copies of it, plus the relates check on entity resources; runs in the ontology CI job.
  • Activation: the gate measured 52/52 under uipath-ontology (runs 44284706628, 44293074603); baseline 100. One row set for the skill, document prompts included, plus boundary rows that keep a tenant entity create (uipath-platform) and deploying a packed ontology solution (uipath-solution) with their own skills.
  • The golden test runs in test-helpers.yml (skips without UIP_CLI); the skill is registered in the genome checker and the Studio Web browser-command allow list.
  • npm run skills:validate and skills:check-links: clean. skills:test: one local failure in compose-skill-flavor.test.mjs (an npm pack publish-registry check that depends on the local npm setup); it fails the same way on the commit before these changes. check-skill-status, check-skills-sh, check-sensitive-content, check-task-host-paths: clean.

🤖 Generated with Claude Code

@diwakar-jha3110 diwakar-jha3110 self-assigned this Nov 5, 2026
@github-actions

github-actions Bot commented Nov 5, 2026

Copy link
Copy Markdown
Contributor

⚠️ Smoke test coverage gap — the following changed skills have no tests under tests/tasks/:

  • uipath-ontology-authoring

Consider adding smoke tests before merging.

@github-actions

github-actions Bot commented Nov 5, 2026 •

Copy link
Copy Markdown
Contributor

skill-lint: 0 new errors, 2 new warnings

Rule Location Message
warning CODE-FENCE-PARSE skills/uipath-ontology/references/mapping-yarrrml-guide.md:107 yaml block does not parse: expected <block end>, but found '?' (line 2 of the block)
warning CODE-FENCE-PARSE skills/uipath-ontology/references/relationships-guide.md:37 yaml block does not parse: expected <block end>, but found '?' (line 2 of the block)
What these rules check
  • CODE-FENCE-PARSE: JSON and YAML code blocks must parse, unless they are clearly sketches or fragments. Agents copy example payloads verbatim into files and commands. A block that does not parse teaches a broken shape. Blocks with ..., <placeholder>, {{template}}, → annotations or JSON comments, JSON Lines, and fragments showing a few properties are accepted as documentation.

Only what this PR adds is listed, compared with the commit it branched from; issues already on the base branch are not. Updated on every push.

@github-actions

github-actions Bot commented Nov 13, 2026 •

Copy link
Copy Markdown
Contributor

Claude finished @diwakar-jha3110's task in 2m 31s —— View job


Review of PR #4432: uipath-ontology-modeler + uipath-ontology-authoring

Summary

The PR adds two preview skills. uipath-ontology-modeler builds an ontology and its local Data Fabric entities as a local solution, then validates and packs it. uipath-ontology-authoring turns an SDD or PDD into a confirmed model and hands it to the modeler. It also extends uipath-solution for deploying a solution that carries an ontology. The work is solid: the stage order is clear, the recovery table is thorough, the stop conditions are explicit (3 check rounds, 5 validate rounds, no pack after ServiceValidationFailed), and both skills say what to do when the sibling skill is missing. I found no Critical or High issues. Three Medium issues are worth fixing before merge.

This was a read-only review. Running pytest and the scripts/check-*.py checkers wasn't permitted in this run, so the PR's claims that they pass were not re-verified. Links and anchors were checked by hand.

Change-by-Change Review

1. skill-flavors/studioweb/uipath-ontology-authoring/SKILL.md:2

Medium. The override says "Stop before Phase 3", but the authoring skill is organised as Steps 1–5, not Phases. In Studio Web an agent can't tell where to stop: it could stop at Step 3, which is still modeling and harmless, instead of at Step 5, the delegation that needs a local solution. Change it to "Stop before Step 5 (the delegation)". The modeler's override is correct.
Fix this →

2. skills/uipath-ontology-modeler/SKILL.md:219-222 — Updating an existing solution

Medium. These commands don't follow the skill's own Critical Rule 1 (every step runs with --output json). They also don't follow the Stage 4 and Stage 6 pattern for choosing the solution:

  • uip ont get (line 219), uip df entities list --local (line 219), uip df entities create|update and uip ont update … --add-entity (line 220), and uip ont files add|remove (line 221) have no --output json.
  • uip ont update, files add and files remove have no --solution-folder "<SOLUTION_DIR>".
  • The uip df calls have no cd "<SOLUTION_DIR>" && prefix. Stage 4 explains why it matters: the shell's working directory may differ.

An agent upgrading a solution will copy these lines as written. Several recovery-table rows (lines 247, 249, 250, 290) have the same gap, though there it is less serious because they are pointers rather than commands to copy.
Fix this →

3. skills/uipath-solution/references/develop-solution.md:319 vs :313

Medium. The new text says a repeated remote import "returns Unchanged; it never overwrites". Six lines above, line 313 (not changed by this PR) still says "Updated" means the "cloud spec re-applied when SDK detects drift on --source remote". These two statements now contradict each other in the same section. Either update line 313 to match the Step 11a behaviour or drop the new claim. This edit is also unrelated to ontologies: it is a uipath-solution behaviour fix inside an ontology PR. Mention it in the PR description, or move it to its own PR.

4. skills/uipath-solution/references/pack-and-deploy.md

Medium. The added 37 lines bring the file to 41,624 bytes, past Codex's 40,000-byte single-read limit (the skill-lint AGENT-READ-TRUNCATED warning). Codex will drop the middle of this file. The new "Solutions that carry an ontology" section reads as a self-contained scenario. Move it to references/scenarios/ and keep a one-line link where it sits now.

5. skills/uipath-ontology-modeler/references/owl-patterns-guide.md (~30 blocks), relationships-guide.md:27, mapping-yarrrml-guide.md:103

Low. The fenced code blocks have no language identifier (content-quality rule). Use ```text for OWL functional syntax.

6. skills/uipath-ontology-modeler/references/mapping-yarrrml-guide.md:13,84

Low. The {ClassName} / {propName} placeholders are YAML flow-mapping syntax, so these blocks don't parse (skill-lint CODE-FENCE-PARSE). Pasted literally, they produce broken YAML. Consider the repo's <PLACEHOLDER> convention, or keep {…} and accept the warning on purpose. {name} is used consistently across all files, so either choice is fine as long as it is deliberate.

7. skills/uipath-ontology-modeler/SKILL.md:5

Low. allowed-tools: Bash grants unrestricted Bash (skill-lint SEC-BROAD-BASH). Consider Bash(uip:*), Bash(mkdir:*), Bash(cd:*).

8. skills/uipath-ontology-modeler/references/owl-patterns-guide.md:34 and :42

Low. The same "without them, the AI agent … cannot answer questions about value domains, grain, cardinality, or join columns" sentence appears twice in one section. Drop line 42.

9. Handoff contract duplicated in both SKILL.md files (modeler:66-95, authoring:37-66)

OK. This is deliberate: Critical Rule 13 requires it, the self-contained-skill rule forces it, and the contract test pins it.

10. Frontmatter, registries, CODEOWNERS, flavors

OK.

  • name matches the folder in both skills, and both descriptions are under 1024 characters, start with "UiPath Ontology", and use → redirects.
  • skill-status.json, skills.sh.json and the README table are updated.
  • CODEOWNERS covers both skill folders, both flavor folders and both task folders. It does not cover tests/scripts/test_check_ontology_classes.py.
  • The flavor marker blocks are compact and sit at column one. The solution-create replacement block is the smallest marked passage.

11. Cross-skill references

OK. Both skills hand work to siblings by skill name at runtime, and each hand-off says what to do when the sibling is missing: authoring:223 and entity-guide:7 do; pack-and-deploy names uipath-ontology-modeler and says what to tell the user without it. No skill reads another skill's files.

12. Links and anchors

OK. I checked these by hand and all resolve: #domain-annotation, #inverse-properties, #choice-set-columns, #source-system, #joins, #property-object-pairs-po, #federated-entities, #value-list-from-a-choice-set, #step-11a-…, #step-4-deploy-to-orchestrator.

13. Test tasks

OK. Each skill has a smoke task and an e2e task. The first tag is the skill name, then smoke or e2e and mode:build. The task_ids follow skill-ontology-<…>. Prompts state goals, not steps. The criteria grade the result through check_ontology.py, plus command_not_executed checks that nothing touched the tenant or deployed. @uipath/cli is not pinned. The tasks need a uip build with uip ont, as the PR body says.

14. .github/workflows/test-helpers.yml + docs/REQUIRED-CHECKS.md

OK. The new job ontology skill contract guards is added to the required set in the same PR, and no existing job was renamed or had its trigger narrowed.

What's Missing

  • /tests/scripts/test_check_ontology_classes.py has no CODEOWNERS entry; the other two ontology test scripts have one.
  • upgrade-guide.md is linked only inline (SKILL.md:224, :288) and is missing from the Reference Navigation table.
  • No passing-run evidence for the four coder_eval tasks yet. That is expected until uip ont ships in a release, but it should be added before merge.

Area Ratings

Area Status Notes
Frontmatter OK Valid; broad Bash grant on the modeler (Low)
E2E Tests OK smoke + e2e for both skills; blocked on uip ont release
Skill Body Issue Commands in Updating an existing solution break Critical Rule 1 (#2)
References & Assets Issue Studio Web flavor points to a nonexistent "Phase 3" (#1); pack-and-deploy.md over the Codex read limit (#4); develop-solution.md contradicts itself (#3)
Repo Hygiene OK Registries/CODEOWNERS updated; no secrets or personal paths found; one test script has no CODEOWNERS entry

Issues for Manual Review

  • I can't verify the CLI surface: uip ont *, uip df … --local (choice sets, federated entities, referenceEntityName), and the error codes in the recovery table. It depends on UiPath/cli#5710 and #5798.
  • Whether uip solution pack "<SOLUTION_DIR>" "<SOLUTION_DIR>/out" excludes a previous out/ folder from the next pack during upgrades.
  • Self-reference relationships are marked "unverified" at deploy (relationships-guide:82). Confirm whether that should stay in a preview skill or be gated harder.
  • Possible trigger overlap between uipath-ontology-modeler and uipath-platform for "Data Fabric entity" requests. The boundary activation rows cover it; the activation eval will confirm.

Conclusion

I recommend requesting changes for the Medium items. #1 and #2 are quick fixes, #3 is a contradiction inside uipath-solution that needs a decision, and #4 means moving the new section into its own scenario file. The rest is polish. Once a uip release carries cli#5710 and the CLI-verb and smoke checks go green, the PR looks ready.

@diwakar-jha3110

Copy link
Copy Markdown
Author

On the SEC-BROAD-BASH warning (skill-lint, and item 7 of the Claude review): kept allowed-tools: Bash on both ontology skills to match every other skill in the repo. The modeler also runs cd "<SOLUTION_DIR>" && uip …, which Bash(uip:*) would not match.

The other review and task-lint items are fixed in 4b1dede, beb25f4, ae84776 and 3291ca0.

@diwakar-jha3110
diwakar-jha3110 force-pushed the feat/ontology-onboarding branch 2 times, most recently from ad7b703 to 2312d4a Compare November 17, 2026 04:42

@alingherasimuip alingherasimuip left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Review notes on the ontology skills: two should-fix items, two design questions and one nice-to-have, inline below.

diwakar-jha3110 added a commit that referenced this pull request Nov 18, 2026
…er [DS-9944]

One skill now takes all three inputs: an SDD/PDD or design document, a
plain-language domain, or artifact files. Review on #4432 showed the split
broke the repo's self-contained rule and cost copied rules, a handoff form
and tests that only kept the copies equal.

- Document mode: the table-by-table confirmation and the phrase-to-model
  tables move to references/document-guide.md, which links the type, name
  and relationship rules instead of copying them. Refused names (Order,
  Group, C#/VB keywords) are checked while the user approves.
- The confirmed model is saved to <WORKDIR>/input/model.md with a
  CONFIRMED_THROUGH step, every fix goes into it before the next command,
  and a WORKDIR holding it is resumed.
- A FILE field's upgrade cost is told before the user confirms it.
- Removed: uipath-ontology-authoring, Delegated mode, the handoff contract
  and the copy-matching tests. Evals and activation rows move under the
  modeler; the smoke SDD now names an entity Group and has a file field.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@diwakar-jha3110 diwakar-jha3110 changed the title feat(uipath-ontology-modeler): build ontologies as local solutions [DS-9944] feat(uipath-ontology): build ontologies as local solutions [DS-9944] Nov 18, 2026

@gabrielavaduva gabrielavaduva left a comment

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Approving. Non-blocking follow-ups:

  • Artifacts-only mode runs only the per-file check. Tell the user at the end of Stage 5 that the cross-file and service checks run only when the files are built into a solution (Files mode). The Report also assumes a packed solution.
  • Artifacts-only still asks for a solution name in Stage 2.
  • Rule 17 fires after the solution and entities exist; a one-line uip ont --help check in Stage 1 would warn before the interview.
  • Deploy merges into a same-name entity in the target folder; worth telling the deployer to check the folder first.
  • The activation baseline (100) was measured before the rename; re-run under uipath-ontology.

Still needed before merge: rebase on main (conflict in uipath-planner/SKILL.md), green CI once the -dev CLI with uip ont lands, and the PR description could list UiPath/cli#6194 and drop the leftover "modeler" wording.

diwakar-jha3110 and others added 17 commits November 19, 2026 09:36
…lutions [DS-9944]

Adds two preview skills over the `uip ont` CLI (UiPath/cli#5710):

- uipath-ontology-authoring: turns an SDD, PDD or domain specification
  into a confirmed domain model (classes, Data Fabric typed properties,
  relationships, choice sets, federated sources, annotations) and
  delegates the build to the modeler.
- uipath-ontology-modeler: writes the schema (.ofn), SHACL constraints,
  YARRRML mapping and optional summary/context; authors the entities,
  choice sets and federated entities locally with `uip df --local`;
  creates the ontology resource, validates with the ontology service and
  packs. Also reads a deployed ontology (`uip ont get|list`). The full
  rule and error recovery table is in references/errors-guide.md.

uipath-solution gains the ontology scenario (name conflicts, post-deploy
check, install errors) and the local-entity FILE-field upgrade recovery.
Registers both skills in skill-status.json, skills.sh.json, CODEOWNERS,
the planner skill map and genome checker, with Studio Web flavor stops,
activation rows, contract/golden tests and smoke and e2e tasks.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
…[DS-9944]

The CLI now writes ontology entity dependencies as `Entity`, like Data Fabric
entities. The assertion already compares kinds lowercased; only the comment
described the old spelling.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
…facts check [DS-9944]

The ontology service retired SHACL constraints (UiPath/ontology a32d5f1ff):
it stores them without parsing or using them, and a package needs none.
The modeler now writes the schema, mapping and optional summary and
context; a constraints file only when the user supplies one or asks.
Required, range and value-list rules go in the schema's rdfs:comment,
which already lists choice-set values.

Follows UiPath/cli#5710:
- `uip ont artifacts check <path> [--type]`: the file name decides the
  type, as in `files add`; --content-type and --file are gone.
- SHC-011 (WARNING) and SUM-003 (ERROR) are in the errors guide.
- validate's failure Data key is `serviceValidation`.

Evals: constraints are no longer required (check_ontology.py, e2e_pack,
e2e_sdd_to_pack); smoke_artifacts_only grades the choice-set values in the
schema comment and that no constraints file was written.

Verified: contract tests (59) pass, and the golden flow passes end to end
(service validation and pack included) against a local build of #5710.
Merge after #5710: the CLI verb gate needs `uip ont` in the @dev catalog.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
…es [DS-9944]

Stage 4 showed an inline --body, so agents sometimes skipped the Stage 2
input/entities files; the sdd-handoff smoke task reads them.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
…pied rules [DS-9944]

Authoring kept the approved model only in the conversation, so a compacted
or ended session lost it before the modeler wrote anything. It now saves the
handoff block to <BASE_DIR>/<ONTOLOGY_NAME>-handoff.md after each confirmed
step, resumes from it in Step 1 and delegates from it in Step 5.

Authoring's type table lacked the FILE type the modeler supports. Added it,
and contract tests now pin every rule authoring restates from the modeler:
type tables, name and folder checks, error codes, backing and junction rules.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
…er [DS-9944]

One skill now takes all three inputs: an SDD/PDD or design document, a
plain-language domain, or artifact files. Review on #4432 showed the split
broke the repo's self-contained rule and cost copied rules, a handoff form
and tests that only kept the copies equal.

- Document mode: the table-by-table confirmation and the phrase-to-model
  tables move to references/document-guide.md, which links the type, name
  and relationship rules instead of copying them. Refused names (Order,
  Group, C#/VB keywords) are checked while the user approves.
- The confirmed model is saved to <WORKDIR>/input/model.md with a
  CONFIRMED_THROUGH step, every fix goes into it before the next command,
  and a WORKDIR holding it is resumed.
- A FILE field's upgrade cost is told before the user confirms it.
- Removed: uipath-ontology-authoring, Delegated mode, the handoff contract
  and the copy-matching tests. Evals and activation rows move under the
  modeler; the smoke SDD now names an entity Group and has a file field.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
…odeler [DS-9944]

The planner claims every PDD and SDD ("A PDD always routes here"), so
"build an ontology from this PDD" could stop at the planner, which has no
ontology path yet.

- uipath-planner: redirect an ontology, even from a PDD/SDD, to
  uipath-ontology-modeler, and carve ontologies out of the PDD rule, as it
  already does for every other build skill.
- uipath-ontology-modeler: its description claims ontology builds and
  updates, even from an SDD or PDD.

Both stay inside the 1024-char description and the 1536-char listing cut
(planner 1524, modeler 1037); the contract test pins the wording and the
limits. Invoking /uipath-ontology-modeler directly still works either way.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
…-only, keep the model current on update [DS-9944]

- Being logged out no longer blocks confirming the model: Stage 2 needs no
  tenant, so login is asked for before Stage 3 instead.
- Artifacts-only output takes a document too, confirmed table by table.
- An update reads input/model.md, saves each change to it first and marks
  it built after pack; a built model is updated, not offered for resume.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
The activation gate skipped uipath-ontology-modeler ("no baseline"), so CI
never checked that its 25 SDD/PDD/design-document prompts reach it rather
than the planner. Add a provisional baseline of 80 (floor 70%, the suite's
recall.yes threshold); replace it with the measured figure after the first
run.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
…easured 100 [DS-9944]

The first gate run routed all 52 rows to uipath-ontology-modeler, the 25
SDD/PDD/design-document prompts included (actions/runs/44280682981).

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
…ntology [DS-9944]

The skill now covers every way into an ontology (a document, plain words or
artifact files), so it takes the product name, as review suggested. Folder,
frontmatter, Studio Web flavor, evals, activation rows and gate baseline,
planner redirect and genome list, skill status, skills.sh, README and
CODEOWNERS follow. The CLI's telemetry list needs the new name too
(separate PR in UiPath/cli).

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
…S-9944]

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
…DS-9944]

The resource builder still reports Updated when a new remote import also
changes resources already in the solution (their dependency links, or
hidden resources), so the status line lists all three values again. A
resource already in the solution is still never re-imported (Unchanged).

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
…ke create check [DS-9944]

The smoke run on a CLI without `uip ont` showed the agent working around
"unknown command 'ont'" and packing the solution without the ontology.
Critical Rule 17 and the error tables now say: stop, ask the user to update
uip, report what is done; never pack, refresh or import to work around it.
The check fires on the error, not up front, so Stages 1-4 still run on an
older CLI.

The smoke task's "created with the local CLI" check needed two matching
Bash calls; the agent created the choice set and the entities in one
script, so it matched once although every resource existed. It is now two
checks, one per kind, each needing one match.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
…e [DS-9944]

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
…without a solution, warn about same-name entities [DS-9944]

From review: Stage 1 runs `uip ont --help` in every mode so an old uip
stops before the interview. Artifacts-only no longer asks for a solution,
gets its own report saying the cross-file and service checks did not run,
and resumes at Stage 5. The deploy handoff tells the user to check the
target folder for same-name entities.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@diwakar-jha3110
diwakar-jha3110 force-pushed the feat/ontology-onboarding branch from 8f8f0ce to daa024a Compare November 19, 2026 04:08

This branch has not been deployed

No deployments
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.

4 participants