PrismDevRelOpen the app
Case studies: Command reference

Overview

Case studies

UORust

How UORust was modeledArchitecture walkthroughDesign views in OPM and UMLFeatures and journeysSecurity and threat modelQuality model (ISO/IEC 25010)Behavior and proofsSystem and releaseExtension facetsCommand referenceSlides and video scriptRecord explorerllms.txt and Markdown twins

Prism-DevRel

How Prism-DevRel was modeledArchitecture walkthroughDesign views in OPM and UMLFeatures and journeysSecurity and threat modelQuality model (ISO/IEC 25010)Behavior and proofsExtension facetsSlides and video scriptRecord explorerllms.txt and Markdown twins

Rule 30

How Rule 30 was modeledArchitecture walkthroughSecurity and threat modelQuality model (ISO/IEC 25010)Behavior and proofsSlides and video scriptRecord explorerllms.txt and Markdown twins

Verdant Resonance

How Verdant Resonance was modeledBehavior and proofsExtension facetsSlides and video scriptRecord explorerllms.txt and Markdown twins

Foundry

How Foundry was modeledBehavior and proofsSlides and video scriptRecord explorerllms.txt and Markdown twins

// case study · UORust

Command reference

Every command and option of the UORust tool, read from its source. Also the commands its gate runs.

Subject: UORust at commit afd5cea950a8, 331 facet records, source digest f3f743b6834adaff.

The UORust command line7 nodes and 6 links. uorust to project; uorust to check; uorust to mir; uorust to prove; uorust to core; uorust to routes.uorustprojectWrite the projection of a workspace intoa directorycheckCheck that a directory holds exactly theprojection of a workspacemirDump the MIR of every library and binarytarget of a workspace, for the MIR pathof the lift (`--mir`)proveDecide every translation of the MIR pathwith `lexlean verify` and write theverdict register (`--verdicts`)coreTranslate every body of core's MIR, as`scripts/mir/dump-coreroutesPrint the route tableThe UORust command line7 nodes and 6 links. uorust to project; uorust to check; uorust to mir; uorust to prove; uorust to core; uorust to routes.uorustprojectcheckmirprovecoreroutes
The UORust command line. Each command, read from the source of the command line, and what it does.
The data in this figure
FromLinkTo
uorust→project
uorust→check
uorust→mir
uorust→prove
uorust→core
uorust→routes

Read from the clap declaration in crates/uorust/src/main.rs at commit afd5cea950a8. The tutorial runs these on a fixture.

Commands

CommandWhat it does
projectWrite the projection of a workspace into a directory.
checkCheck that a directory holds exactly the projection of a workspace.
mirDump the MIR of every library and binary target of a workspace, for the MIR path of the lift (`--mir`).
proveDecide every translation of the MIR path with `lexlean verify` and write the verdict register (`--verdicts`).
coreTranslate every body of core's MIR, as `scripts/mir/dump-core.sh` dumps it one module at a time, and write the core register.
routesPrint the route table.

Arguments of project and check

ArgumentWhat it sets
<workspace>The workspace root, the directory with the top `Cargo.toml`.
--outThe directory the dumps are written to.

What UORust's gate runs

These are the lines of the uorust recipe of the Justfile that name the fixture, the self-projection and its register:

cargo run -q --locked -p uorust -- check crates/uorust/tests/fixtures/thermostat --out crates/uorust/tests/fixtures/thermostat-prism --name thermostat --last-modified 2026-11-11T00:00:00Z
cd crates/uorust/tests/fixtures/thermostat-prism && lexlean fmt --check && lexlean lock --check && lexlean verify && prismpm check
cargo run -q --locked -p uorust -- check . --out target/uorust-self --name uorust --last-modified 2026-11-11T00:00:00Z --register frontier.toml {{mir}}

referenceBuildcase studyMarkdown

Words on this page 2
facet
One view of a model, such as its architecture, its security or its quality. Each facet holds records.
record
One entry in a facet: a component, a threat, a measure or a journey step, with the place in the source it came from.