The talk, slide by slide. One title slide, then one slide for each facet of UORust, each showing one real record.The data in this figure
Step
What happens
1. UORust
title
2. Architecture
Component
3. Behavior and proofs
theorem
4. Extension facets
Authority
5. Design views
UmlConnector
6. Features and journeys
Feature
7. Quality
ProductQualityCharacteristic
8. Application
TextApplication
9. Security and threat model
AcceptedRisk
10. System and release
SystemManifest
UORust
331 facet records
14 pages teach them
Script
This talk walks through UORust one facet at a time. Every record it shows is real, quoted from the model at commit afd5cea950a8.
Architecture
61 records in this facet
For example: Admission (Component)
Admission: what the router proposes is admitted, or refused with a typed reason that becomes an open claim.
Script
The architecture facet is an ISO/IEC/IEEE 42010 architecture description. The example on screen is Architecture::componentAdmission.
Behavior and proofs
29 records in this facet
For example: edgesJoinDistinctComponents (theorem)
Script
Behavior is what the Lean kernel checks. The example on screen is Architecture::edgesJoinDistinctComponents.
Extension facets
2 records in this facet
For example: authority (Authority)
Script
Extension facets are models for one use case that a project adds beside the standard facets, as Foundation/<Domain>/V1/Model.lex.tex. The example on screen is Brand::authority.
Design views
73 records in this facet
For example: connectorAdmissionEmitter (UmlConnector)
Script
Design views add drawings to the architecture. The example on screen is Design::connectorAdmissionEmitter.
Features and journeys
15 records in this facet
For example: UORust's application answers the route table of model/routes.toml route for route, and replays every router and workbench vector of that file in order (Feature)
UORust's application answers the route table of model/routes.toml route for route, and replays every router and workbench vector of that file in order
Script
Features say what the product does. The example on screen is Features::featureBrowserRoutes.
Quality
40 records in this facet
For example: characteristicFlexibility (ProductQualityCharacteristic)
Script
The quality facet follows ISO/IEC 25010:2023. The example on screen is Quality::characteristicFlexibility.
Application
1 record in this facet
For example: UORust (TextApplication)
Script
The application record is what a holo is built from: its entry root, its acceptance vectors and its view. The example on screen is Routes::application.
Security and threat model
108 records in this facet
For example: acceptedPagesHostSubstitution (AcceptedRisk)
The page cannot defend against its own host. A user who needs more can build the route table from the tagged source with prismpm verify and compare.
Script
The security facet holds ISO/IEC 27034 and ISO/IEC 27005 records: assets, threats, risks and controls. The example on screen is Security::acceptedPagesHostSubstitution.
System and release
2 records in this facet
For example: systemManifest (SystemManifest)
Script
The system facet is the production system model. The example on screen is System::systemManifest.
Routes each kind of Rust fact UORust reads from a Cargo workspace to the one Prism record kind it emits, or refuses it.
cargoRepository
https://github.com/afflom/uorust
cargoHomepage
https://afflom.github.io/UORust/
libraryRoots
Uorust.Routes.dispatch
acceptanceVectors
(acceptanceVectors)
entryRoot
Uorust.Routes.dispatch
coreContract
hologram:guest/core-wasm@1
requestMaximum
(318 : UInt32)
responseMaximum
(8192 : UInt32)
guestAllocationMaximum
(319 : UInt32)
coreMemoryPages
(ctor Option.some [UInt32] (32 : UInt32))
coreStackBytes
(ctor Option.some [UInt32] (65536 : UInt32))
capabilitiesEmpty
true
fatArchive
true
primaryLayer
(0 : UInt8)
viewLayer
(1 : UInt8)
view
TextView
title
UORust route table
heading
UORust route table
inputLabel
Rust fact kinds, one per line
submitLabel
Route
outputLabel
Route or refusal
inputError
Enter UTF-8 text of at most 512 bytes.
responseError
The answer could not be displayed.
cli
TextCli
command
route
description
UORust 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.
usageCode
(64 : UInt8)
ioCode
(74 : UInt8)
limitCode
(ctor Option.none [UInt8])
outcomes
TextCliOutcome
name
routed
prefix
route
exitCode
(0 : UInt8)
TextCliOutcome
name
refused
prefix
refused
exitCode
(1 : UInt8)
TextCliOutcome
name
error
prefix
error
exitCode
(2 : UInt8)
sections
TextCliSection
title
REQUEST
body
One kind of Rust fact per line, such as pub-fn, error-enum or unsafe-block. Every line must name the same route.
TextCliSection
title
ANSWER
body
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