PrismDevRelOpen the app
Case studies: Features and journeys

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

Features and journeys

What UORust does, the calls that do it, the rows that accept it, and the paths people take.

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

Features and journeys records by kindFeature: 10 records; Journey: 5 recordsFeature10Journey5
Features and journeys records by kind. The 15 records this page teaches, one bar for each kind. Each kind has its own section below.
The data in this figure
records
Feature10
Journey5

Features say what the product does. Each has a statement, the interface calls that do the work, and the acceptance rows that accept it. A journey is the features one stakeholder uses, in order. The SDK checks them with PP2014 to PP2018. See PrismPM SPEC section 2.2.

Features and journeys facet explains the facet for every Prism model, with the counts of every case study.

Every record

Every record 15 rows
IndexRecordKindName
142Features::featureBrowserRoutesFeatureUORust'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
143Features::featureCheckProjectionFeatureCheck that a directory holds exactly the projection of a workspace.
144Features::featureCheckedOutputFeatureThe gate checks the committed fixture projection and a fresh projection of this workspace with lexlean and prismpm
145Features::featureDeterministicOutputFeatureTwo projections of the same workspace are byte-identical, for the fixture and for this workspace
146Features::featureLiftBehaviorFeatureFunction bodies to LexLean definitions, where the lift is mechanical.
147Features::featureProjectWorkspaceFeatureWrite the projection of a workspace into a directory.
148Features::featureRefuseAmbiguityFeatureAdmission: what the router proposes is admitted, or refused with a typed reason that becomes an open claim.
149Features::featureRouteFactsFeatureThe route table and the router: which kind of Rust fact becomes which kind of Prism record in which facet.
150Features::featureSelfModelFeatureUORust is modeled in every facet, each with records, and every module title has a project-local glossary entry
151Features::featureTypedErrorsFeatureEvery way a run can end without a projection is a typed UorustError variant with a negative test
152Features::journeyDevRelAuthorJourneyjourneyDevRelAuthor
153Features::journeyMaintainerJourneyjourneyMaintainer
154Features::journeyPrismModelerJourneyjourneyPrismModeler
155Features::journeyRustDeveloperJourneyjourneyRustDeveloper
156Features::journeySecurityReviewerJourneyjourneySecurityReviewer

Feature (10)

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

Check that a directory holds exactly the projection of a workspace.

Features::featureCheckProjection Feature #143 source

Check that a directory holds exactly the projection of a workspace.

statement
Check that a directory holds exactly the projection of a workspace.
calls
  • Features::callCheck
acceptance
  • Features::acceptFixtureProjection
  • Features::acceptByteIdentical

Taught by Features and journeys

The gate checks the committed fixture projection and a fresh projection of this workspace with lexlean and prismpm

Features::featureCheckedOutput Feature #144 source

The gate checks the committed fixture projection and a fresh projection of this workspace with lexlean and prismpm

statement
The gate checks the committed fixture projection and a fresh projection of this workspace with lexlean and prismpm
calls
  • Features::callPrismPmCheck
acceptance
  • Features::acceptFixtureProjection
  • Features::acceptGate

Taught by Features and journeys

Two projections of the same workspace are byte-identical, for the fixture and for this workspace

Features::featureDeterministicOutput Feature #145 source

Two projections of the same workspace are byte-identical, for the fixture and for this workspace

statement
Two projections of the same workspace are byte-identical, for the fixture and for this workspace
calls
  • Features::callProject
  • Features::callCheck
acceptance
  • Features::acceptByteIdentical

Taught by Features and journeys

Function bodies to LexLean definitions, where the lift is mechanical.

Features::featureLiftBehavior Feature #146 source

Function bodies to LexLean definitions, where the lift is mechanical.

statement
Function bodies to LexLean definitions, where the lift is mechanical.
calls
  • Features::callProjectWorkspace
acceptance
  • Features::acceptLift

Taught by Features and journeys

Write the projection of a workspace into a directory.

Features::featureProjectWorkspace Feature #147 source

Write the projection of a workspace into a directory.

statement
Write the projection of a workspace into a directory.
calls
  • Features::callProject
  • Features::callProjectWorkspace
acceptance
  • Features::acceptFixtureProjection
  • Features::acceptGate

Taught by Features and journeys

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

Features::featureRefuseAmbiguity Feature #148 source

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

statement
Admission: what the router proposes is admitted, or refused with a typed reason that becomes an open claim.
calls
  • Features::callProjectWorkspace
  • Features::callRespond
acceptance
  • Features::acceptTypedRefusals
  • Features::acceptRouteTheorems

Taught by Features and journeys

The route table and the router: which kind of Rust fact becomes which kind of Prism record in which facet.

Features::featureRouteFacts Feature #149 source

The route table and the router: which kind of Rust fact becomes which kind of Prism record in which facet.

statement
The route table and the router: which kind of Rust fact becomes which kind of Prism record in which facet.
calls
  • Routes::dispatch
  • Features::callRespond
  • Features::callRoutes
acceptance
  • Routes::acceptanceVectors
  • Features::acceptRouterConformance
  • Features::acceptRouteTheorems

Taught by Features and journeys

UORust is modeled in every facet, each with records, and every module title has a project-local glossary entry

Features::featureSelfModel Feature #150 source

UORust is modeled in every facet, each with records, and every module title has a project-local glossary entry

statement
UORust is modeled in every facet, each with records, and every module title has a project-local glossary entry
calls
  • Features::callPrismPmCheck
acceptance
  • Features::acceptGate
  • Features::acceptRouteTheorems

Taught by Features and journeys

Every way a run can end without a projection is a typed UorustError variant with a negative test

Features::featureTypedErrors Feature #151 source

Every way a run can end without a projection is a typed UorustError variant with a negative test

statement
Every way a run can end without a projection is a typed UorustError variant with a negative test
calls
  • Features::callProject
  • Features::callCheck
acceptance
  • Features::acceptTypedErrors

Taught by Features and journeys

Journey (5)

explanationLearncase studyMarkdown

Words on this page 5
Prism model
A description of an app, written in LexLean, that covers every facet of it and that the Lean kernel checks before the app is built.
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.
SDK
Software development kit. Here, the PrismPM container image that builds, checks and verifies Prism models.
stakeholder
A person or group with an interest in the system, as ISO/IEC/IEEE 42010 defines it.