PrismDevRelOpen the app
Case studies: How Rule 30 was modeled

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

How Rule 30 was modeled

Who the Rule 30 model is for and what they care about. Then how those concerns became facets.

The records of Rule 30 by facetArchitecture: 37 records; Security and threat model: 20 records; Quality: 4 records; Behavior and proofs: 2119 recordsArchitecture37Security and threat model20Quality4Behavior and proofs2119
The records of Rule 30 by facet. Every record of the Rule 30 model, counted by facet. Each one is taught by at least one page of this case study.
The data in this figure
records
Architecture37
Security and threat model20
Quality4
Behavior and proofs2119

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

This case study reads every facet record of Rule 30. Each record is taught by at least one page here, and no page teaches a record Rule 30 does not declare.

Records
2180
Covered
2180
Pages
8
Facets
4

People, concerns and the application

These are the records of Rule 30 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.

How the facets answer each concern

For each concern, the records of Rule 30 that name it or name a viewpoint that frames it, counted by facet. Each count links to the first such record.

ConcernNamed by
evidenceArchitecture: 2
ownershipArchitecture: 2
velocityArchitecture: 2

Learning paths

The pages of this case study, by the stage of the developer journey each one serves:

Pages of this case study

PageModalityRecordsWhat you get
How Rule 30 was modeledWalkthrough4Who the Rule 30 model is for and what they care about. Then how those concerns became facets.
Architecture walkthroughWalkthrough37Who Rule 30 is for, what they care about, its parts and how they connect.
Security and threat modelWalkthrough20The assets of Rule 30, its threats, risks and controls, and the risks it accepts on purpose.
Quality model (ISO/IEC 25010)Reference4What good quality means for Rule 30, and the numbers that measure it.
Behavior and proofsReference2119Every theorem of Rule 30, and how it is proved. The Lean kernel checks each one.
Slides and video scriptSlides and script4One slide for each facet of Rule 30, with a script to read over it.
Record explorerInteractive0Search every record of Rule 30 by name, facet or text. Each result links to the pages that teach it.
llms.txt and Markdown twinsAgent twin0The Rule 30 case study as plain text for agents. It has llms.txt, a twin of each page and a feed.

Facets of Rule 30

Each facet links to the page that explains it for every Prism model, beside the count for this one:

explanationEvaluatecase studyMarkdown

Words on this page 6
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.
holo
The app Prism builds: one signed, verified file that a browser or a device runs.
stakeholder
A person or group with an interest in the system, as ISO/IEC/IEEE 42010 defines it.
developer journey
The stages a developer goes through with a product: discover, evaluate, learn, build and scale (Lewko and Parton).