PrismDevRelOpen the app
Case studies: Slides and video script

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

Slides and video script

One slide for each facet of UORust, with a script to read over it.

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

The talk, slide by slide1. 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: SystemManifest01UORusttitle02ArchitectureComponent03Behaviorandproofstheorem04ExtensionfacetsAuthority05DesignviewsUmlConnector06FeaturesandjourneysFeature07QualityProductQualityCharacteristic08ApplicationTextApplication09SecurityandthreatmodelAcceptedRisk10SystemandreleaseSystemManifestThe talk, slide by slide1. 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: SystemManifest01UORusttitle02ArchitectureComponent03Behavior and proofstheorem04Extension facetsAuthority05Design viewsUmlConnector06Features and journeysFeature07QualityProductQualityCharacteristic08ApplicationTextApplication09Security and threat modelAcceptedRisk10System and releaseSystemManifest
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
StepWhat happens
1. UORusttitle
2. ArchitectureComponent
3. Behavior and proofstheorem
4. Extension facetsAuthority
5. Design viewsUmlConnector
6. Features and journeysFeature
7. QualityProductQualityCharacteristic
8. ApplicationTextApplication
9. Security and threat modelAcceptedRisk
10. System and releaseSystemManifest

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.

Admission

Architecture::componentAdmission Component #0 source

Admission: what the router proposes is admitted, or refused with a typed reason that becomes an open claim.

index
0
kind
(ctor Foundation.Arch::ComponentKind.service)

Taught by Architecture walkthrough, Slides and video script

authority

Brand::authority Authority #63 source

framework
Alina Wheeler, Designing Brand Identity, 5th ed., Wiley, 2017; W3C Design Tokens Format Module 2025.10; WCAG 2.2
repository
UOR-Foundation/website
commit
a863acf85f90bacfd34dbef5c2e5c96fa0f98840

Taught by Extension facets, Slides and video script

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

Features::featureBrowserRoutes Feature #142 source

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

statement
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
calls
  • Features::callPagesRoute
  • Routes::dispatch
acceptance
  • Routes::acceptanceVectors

Taught by Features and journeys, Slides and video script

UORust

Routes::application TextApplication #207 source

UORust 22 entries
profile
prismpm/text-application/3
cargoName
uorust-routes
cargoVersion
0.1.1
cargoDescription
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
examples
  • TextCliExample
    name
    routed
    text
    error-enum
  • TextCliExample
    name
    ambiguous
    text
    error-enum state-enum
workbench
(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

systemManifest

System::systemManifest SystemManifest #323 source

applicationModelDigest
sha256:a2f3e6e8d6d66c70e2351a24478ffbbe7cef7c26eed9279f47ee0fbe9757af05
productId
uorust
productVersion
0.1.1
componentId
uorust-browser
artifactId
uorust-application
targetId
pages
controls
  • application-acceptance
  • artifact-closure
  • source-proof
  • spdx

Taught by System and release, Slides and video script

explanationDiscovercase studyMarkdown

Words on this page 5
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.
Lean kernel
The small checker at the heart of the Lean prover. It accepts a proof only if every step follows the rules.
holo
The app Prism builds: one signed, verified file that a browser or a device runs.
acceptance test
An input and the output the app must give for it. The holo replays each one before it is offered.