evidence
- index
0
Taught by How Rule 30 was modeled, Architecture walkthrough, Slides and video script
Overview
Case studiesUORust
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 twinsPrism-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 twinsRule 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// case study · Rule 30
Who the Rule 30 model is for and what they care about. Then how those concerns became facets.
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.
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.
0Taught by How Rule 30 was modeled, Architecture walkthrough, Slides and video script
0Taught by How Rule 30 was modeled, Architecture walkthrough
1Taught by How Rule 30 was modeled, Architecture walkthrough
2Taught by How Rule 30 was modeled, Architecture walkthrough
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.
| Concern | Named by |
|---|---|
| evidence | Architecture: 2 |
| ownership | Architecture: 2 |
| velocity | Architecture: 2 |
The pages of this case study, by the stage of the developer journey each one serves:
| Page | Modality | Records | What you get |
|---|---|---|---|
| How Rule 30 was modeled | Walkthrough | 4 | Who the Rule 30 model is for and what they care about. Then how those concerns became facets. |
| Architecture walkthrough | Walkthrough | 37 | Who Rule 30 is for, what they care about, its parts and how they connect. |
| Security and threat model | Walkthrough | 20 | The assets of Rule 30, its threats, risks and controls, and the risks it accepts on purpose. |
| Quality model (ISO/IEC 25010) | Reference | 4 | What good quality means for Rule 30, and the numbers that measure it. |
| Behavior and proofs | Reference | 2119 | Every theorem of Rule 30, and how it is proved. The Lean kernel checks each one. |
| Slides and video script | Slides and script | 4 | One slide for each facet of Rule 30, with a script to read over it. |
| Record explorer | Interactive | 0 | Search every record of Rule 30 by name, facet or text. Each result links to the pages that teach it. |
| llms.txt and Markdown twins | Agent twin | 0 | The Rule 30 case study as plain text for agents. It has llms.txt, a twin of each page and a feed. |
Each facet links to the page that explains it for every Prism model, beside the count for this one:
| Facet | Records |
|---|---|
| Architecture | 37 |
| Security and threat model | 20 |
| Quality | 4 |
| Behavior and proofs | 2119 |