Completeness of the model
Every fact uorust reads is routed to exactly one record kind or refused; nothing is dropped silently.
- index
0
Taught by How UORust was modeled, Architecture walkthrough
Overview
Case studiesUORust
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 twinsPrism-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 twinsRule 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// case study · UORust
Who the UORust model is for and what they care about. Then how those concerns became facets.
UORust says what it is in its own model:
Routes each kind of Rust fact UORust reads from a Cargo workspace to the one Prism record kind it emits, or refuses it.
Subject: UORust at commit afd5cea950a8, 331 facet records, source digest f3f743b6834adaff.
This case study reads every facet record of UORust. Each record is taught by at least one page here, and no page teaches a record UORust does not declare.
These are the records of UORust that say who the model is for, what they care about, and what its holo is built from. Each viewpoint of the architecture pairs one stakeholder with one concern.
Every fact uorust reads is routed to exactly one record kind or refused; nothing is dropped silently.
0Taught by How UORust was modeled, Architecture walkthrough
Running uorust twice on the same workspace writes byte-identical files.
1Taught by How UORust was modeled, Architecture walkthrough
A newcomer can learn what UORust does from its published page and run its route table in the browser.
2Taught by How UORust was modeled, Architecture walkthrough
Every emitted record traces to the Rust item, manifest entry or lock entry it came from.
3Taught by How UORust was modeled, Architecture walkthrough
An ambiguous or unknown fact is refused with a typed reason and recorded as an open claim, never resolved by a guess.
4Taught by How UORust was modeled, Architecture walkthrough
uorust reads the subject workspace and never builds it, runs its build scripts or sends its source anywhere.
5Taught by How UORust was modeled, Architecture walkthrough
The released binary, its dependencies and the published page are what the locked sources say they are.
6Taught by How UORust was modeled, Architecture walkthrough
Writes the walkthroughs and explorers that teach UORust, and covers every facet record with a resource.
0Taught by How UORust was modeled, Architecture walkthrough
Changes the route table, the engine and this model, and keeps the Rust router, the verified table and the Pages site in step.
1Taught by How UORust was modeled, Architecture walkthrough
Reads, checks and extends the Prism project uorust emits, and relies on every record tracing to a source span.
2Taught by How UORust was modeled, Architecture walkthrough
Owns a Cargo workspace and runs uorust to get a Prism model of it without writing the model by hand.
3Taught by How UORust was modeled, Architecture walkthrough
Reviews the threat model uorust derives from unsafe code, effects and the supply chain, and the controls that answer it.
4Taught by How UORust was modeled, Architecture walkthrough
prismpm/text-application/3uorust-routes0.1.1Routes each kind of Rust fact UORust reads from a Cargo workspace to the one Prism record kind it emits, or refuses it.https://github.com/afflom/uorusthttps://afflom.github.io/UORust/Uorust.Routes.dispatch(acceptanceVectors)Uorust.Routes.dispatchhologram:guest/core-wasm@1(318 : UInt32)(8192 : UInt32)(319 : UInt32)(ctor Option.some [UInt32] (32 : UInt32))(ctor Option.some [UInt32] (65536 : UInt32))truetrue(0 : UInt8)(1 : UInt8)UORust route tableUORust route tableRust fact kinds, one per lineRouteRoute or refusalEnter UTF-8 text of at most 512 bytes.The answer could not be displayed.routeUORust reads a Cargo workspace and writes a complete Prism model of it. This page runs UORust's route table, the verified function that decides which Prism record each kind of Rust fact becomes, or refuses the fact.
(64 : UInt8)(74 : UInt8)(ctor Option.none [UInt8])routedroute (0 : UInt8)refusedrefused (1 : UInt8)errorerror (2 : UInt8)REQUESTOne kind of Rust fact per line, such as pub-fn, error-enum or unsafe-block. Every line must name the same route.
ANSWER route ID, fact KIND, record PRISM-RECORD, facet FACET
the one route every kind names
refused unknown-fact, fact KIND
no route names the kind
refused ambiguous, fact KIND, fact KIND
two kinds name different routes
error REASON
the request is empty, too large, not UTF-8 or has a blank line
routederror-enumambiguouserror-enum
state-enum(ctor Option.some [Foundation.View.Text.V3.Model::WorkbenchView] (Guide::view))Taught by Turn a Rust project into a Prism model, How UORust was modeled, Slides and video script
For each concern, the records of UORust that name it or name a viewpoint that frames it, counted by facet. Each count links to the first such record.
| Concern | Named by |
|---|---|
| Completeness of the model | Architecture: 2, Design views: 1 |
| Deterministic output | Architecture: 2 |
| Discoverability | Architecture: 2 |
| Fidelity to the source | Architecture: 2, Design views: 2 |
| No silent defaults | Architecture: 2, Design views: 1 |
| Read-only ingestion | Architecture: 2 |
| Supply-chain integrity | Architecture: 2 |
UORust lifts its own functions too. It keeps the result in frontier.toml, the register its gate passes to --register. Every function of its product code has one row. The rows not lifted are the distance to the goal that every function lifts. That goal is an open claim, measured at each commit:
| Row | Rows | Meaning |
|---|---|---|
| residue | 443 | A pure function outside the lift so far, with the construct that stopped it. |
| foreign | 34 | Its parameter or result is a type of a dependency with no LexLean model yet. |
| effect | 55 | The I/O shell. It reads files, the environment, a process or the network, and is recorded as a capability in the security facet. |
| lifted | 230 | The function became a LexLean definition the kernel checks. |
Here is the residue by the construct that stopped the lift. It is the work list for the next lifts:
| Reason | Functions |
|---|---|
| mir | 348 |
| type | 59 |
| form | 17 |
| collision | 8 |
| call | 7 |
| arithmetic | 3 |
| statements | 1 |
The tutorial shows what one lifted row looks like.
The pages of this case study, by the stage of the developer journey each one serves:
| Page | Modality | Records | What you get |
|---|---|---|---|
| Turn a Rust project into a Prism model | Walkthrough | 6 | Run UORust on a sample workspace and check what it writes. Then read a Rust function beside the LexLean it became. |
| How UORust was modeled | Walkthrough | 13 | Who the UORust model is for and what they care about. Then how those concerns became facets. |
| Architecture walkthrough | Walkthrough | 61 | Who UORust is for, what they care about, its parts and how they connect. |
| Design views in OPM and UML | Diagrams | 73 | Every design view of UORust, drawn. It shows things, steps, parts, messages and states. |
| Features and journeys | Walkthrough | 15 | What UORust does, the calls that do it, the rows that accept it, and the paths people take. |
| Security and threat model | Walkthrough | 108 | The assets of UORust, its threats, risks and controls, and the risks it accepts on purpose. |
| Quality model (ISO/IEC 25010) | Reference | 40 | What good quality means for UORust, and the numbers that measure it. |
| Behavior and proofs | Reference | 29 | Every theorem of UORust, and how it is proved. The Lean kernel checks each one. |
| System and release | Walkthrough | 2 | What UORust ships, its release manifest, and how its holo goes live. |
| Extension facets | Reference | 2 | The records UORust adds of its own. They sit beside the standard facets. |
| Command reference | Reference | 0 | Every command and option of the UORust tool, read from its source. Also the commands its gate runs. |
| Slides and video script | Slides and script | 9 | One slide for each facet of UORust, with a script to read over it. |
| Record explorer | Interactive | 0 | Search every record of UORust by name, facet or text. Each result links to the pages that teach it. |
| llms.txt and Markdown twins | Agent twin | 0 | The UORust case study as plain text for agents. It has llms.txt, a twin of each page and a feed. |
Each facet links to the page that explains it for every Prism model, beside the count for this one:
| Facet | Records |
|---|---|
| Architecture | 61 |
| Design views | 73 |
| Features and journeys | 15 |
| Security and threat model | 108 |
| Quality | 40 |
| Behavior and proofs | 29 |
| System and release | 2 |
| Extension facets | 2 |
| Application | 1 |