Asset Lineage

The generators are anchored to real UiPath Studio 24.10 exports. The assets/ directory preserves the corpus and its derivatives.

The Corpus Chain

Real UiPath Studio 24.10 export
  │
  ├── assets/simple-sequence/        Full Studio exports, preserved as-is
  │     FormFilling_Main.xaml
  │     WebScraping_Sequence1.xaml
  │     PDFExtraction_Main.xaml
  │     Main.xaml
  │
  ├── assets/stripped/               Visual metadata removed; used as generator reference
  │     FormFilling_Main.xaml        ("STRIPPED EXCERPT ... Visual metadata removed")
  │     REFramework_Main.xaml
  │     SetTransactionStatus.xaml
  │
  ├── scripts/generate_activities/   F-string templates encoding the stripped structure
  │     ui_automation.py
  │     application_card.py
  │     ...
  │
  └── assets/generator-snapshots/    Regression lock on generator output
        ui_automation_login.xaml
        try_catch_with_retry.xaml
        ...

assets/simple-sequence/

The original Studio 24.10 exports. These are complete XAML files with full ViewState blocks, the long namespace list Studio adds on save, and all designer metadata. They are the ground truth from which everything else was derived.

assets/stripped/

The comment on line 1 of each file states its origin:

<!-- STRIPPED EXCERPT of FormFilling_Main.xaml for LLM reference.
     Visual metadata removed. Full Studio file: assets/simple-sequence/FormFilling_Main.xaml -->

Stripping removes ViewState blocks, excessive namespace declarations, and designer-only metadata, leaving the structural skeleton that the generator f-strings were modelled on.

assets/reframework/

A separate Studio export — the clean REFramework template for Studio 24.10. Contains the full Framework/ folder, Tests/, Data/, project.json, and entry-points.json. Used by scaffold_project.py as the base for performer variant projects.

assets/samples/

Common workflow pattern samples: API dispatcher, Excel dispatcher, performer process, browser navigation, app close. Used as reference for modify_framework.py wiring patterns.

assets/lint-test-cases/

A separate corpus of intentionally malformed XAML files. These are not Studio exports — they are hand-crafted to trigger specific lint rules. 105 bad_*.xaml files plus one good_browser_workflow.xaml. See Snapshot Testing for the test infrastructure that uses them.

assets/generator-snapshots/

The output of the generators, stored as golden files. 15 snapshot files covering major activity categories. These are regression fixtures: any structural change in generator output causes a test failure. They were generated by running the generators and committing the output — not exported from Studio.

The Manual Gap

There is no automated pipeline that refreshes the stripped assets or generator f-strings when a new Studio version ships. When UiPath releases Studio 25.x with new or changed activity attributes, the update process is:

1. Export the affected workflows from Studio 25.x
2. Manually compare with the current stripped assets
3. Update the generator f-strings to match any attribute changes
4. Regenerate and commit the snapshots with --update

This is the primary maintenance burden introduced by the "derived from real exports" approach.