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 · Rule 30

Slides and video script

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

Subject: Rule 30 at commit e3be477fded2, 2180 facet records, source digest c4584388f052fc09.

The talk, slide by slide1. Rule 30: title 2. Behavior and proofs: theorem 3. Security and threat model: Asset 4. Quality: QualitySubcharacteristic 5. Architecture: Concern01Rule 30title02Behavior andproofstheorem03Security andthreat modelAsset04QualityQualitySubcharacteristic05ArchitectureConcernThe talk, slide by slide1. Rule 30: title 2. Behavior and proofs: theorem 3. Security and threat model: Asset 4. Quality: QualitySubcharacteristic 5. Architecture: Concern01Rule 30title02Behavior and proofstheorem03Security and threat modelAsset04QualityQualitySubcharacteristic05ArchitectureConcern
The talk, slide by slide. One title slide, then one slide for each facet of Rule 30, each showing one real record.
The data in this figure
StepWhat happens
1. Rule 30title
2. Behavior and proofstheorem
3. Security and threat modelAsset
4. QualityQualitySubcharacteristic
5. ArchitectureConcern

Rule 30

  • 2180 facet records
  • 8 pages teach them
Script

This talk walks through Rule 30 one facet at a time. Every record it shows is real, quoted from the model at commit e3be477fded2.

Behavior and proofs

  • 2119 records in this facet
  • For example: commandCountIs (theorem)
Script

Behavior is what the Lean kernel checks. The example on screen is Api::commandCountIs.

Security and threat model

  • 20 records in this facet
  • For example: attemptAsset (Asset)
Script

The security facet holds ISO/IEC 27034 and ISO/IEC 27005 records: assets, threats, risks and controls. The example on screen is ResearchArchitecture::attemptAsset.

Quality

  • 4 records in this facet
  • For example: boundedWork (QualitySubcharacteristic)
Script

The quality facet follows ISO/IEC 25010:2023. The example on screen is ResearchArchitecture::boundedWork.

Architecture

  • 37 records in this facet
  • For example: evidence (Concern)
Script

The architecture facet is an ISO/IEC/IEEE 42010 architecture description. The example on screen is ResearchArchitecture::evidence.

explanationDiscovercase studyMarkdown

Words on this page 3
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.