---
title: "How Rule 30 was modeled"
url: https://afflom.github.io/prism-devrel/case-studies/rule30/
diataxis: explanation
developer-journey: evaluate
collection: case-studies
collection-group: "Rule 30"
subject: https://github.com/afflom/rule30
commit: e3be477fded263029479127363f7fb6a3597e7d4
---

# How Rule 30 was modeled

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

**Figure: 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.

| | Count |
| --- | --- |
| Architecture | 37 |
| Security and threat model | 20 |
| Quality | 4 |
| Behavior and proofs | 2119 |

Subject: [Rule 30](https://github.com/afflom/rule30) at commit [`e3be477fded2`](https://github.com/afflom/rule30/tree/e3be477fded263029479127363f7fb6a3597e7d4), 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.

2180 records, 2180 covered, 8 pages, 4 facets.

## 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.

### `evidence`

`ResearchArchitecture::evidence` · Concern · #541 · [source](https://github.com/afflom/rule30/blob/e3be477fded263029479127363f7fb6a3597e7d4/rule30-api/src/ResearchArchitecture.lex.tex)

- index: `0`

Taught by: case-study, architecture, slides

### `maintainer`

`ResearchArchitecture::maintainer` · Stakeholder · #566 · [source](https://github.com/afflom/rule30/blob/e3be477fded263029479127363f7fb6a3597e7d4/rule30-api/src/ResearchArchitecture.lex.tex)

- index: `0`

Taught by: case-study, architecture

### `ownership`

`ResearchArchitecture::ownership` · Concern · #572 · [source](https://github.com/afflom/rule30/blob/e3be477fded263029479127363f7fb6a3597e7d4/rule30-api/src/ResearchArchitecture.lex.tex)

- index: `1`

Taught by: case-study, architecture

### `velocity`

`ResearchArchitecture::velocity` · Concern · #595 · [source](https://github.com/afflom/rule30/blob/e3be477fded263029479127363f7fb6a3597e7d4/rule30-api/src/ResearchArchitecture.lex.tex)

- index: `2`

Taught by: case-study, architecture

## 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.

| Concern | Named by |
| --- | --- |
| evidence | [Architecture: 2](https://afflom.github.io/prism-devrel/case-studies/rule30/architecture/#ResearchArchitecture-evidenceViewpoint) |
| ownership | [Architecture: 2](https://afflom.github.io/prism-devrel/case-studies/rule30/architecture/#ResearchArchitecture-ownershipViewpoint) |
| velocity | [Architecture: 2](https://afflom.github.io/prism-devrel/case-studies/rule30/architecture/#ResearchArchitecture-velocityViewpoint) |

## Learning paths

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

- Discover: [Slides and video script](https://afflom.github.io/prism-devrel/case-studies/rule30/slides/).
- Evaluate: [Security and threat model](https://afflom.github.io/prism-devrel/case-studies/rule30/security/), [Quality model (ISO/IEC 25010)](https://afflom.github.io/prism-devrel/case-studies/rule30/quality/).
- Learn: [Architecture walkthrough](https://afflom.github.io/prism-devrel/case-studies/rule30/architecture/).
- Build: [Behavior and proofs](https://afflom.github.io/prism-devrel/case-studies/rule30/behavior/), [Record explorer](https://afflom.github.io/prism-devrel/case-studies/rule30/explorer/), [llms.txt and Markdown twins](https://afflom.github.io/prism-devrel/case-studies/rule30/agents/).

## Pages of this case study

| Page | Modality | Records | What you get |
| --- | --- | --- | --- |
| [How Rule 30 was modeled](https://afflom.github.io/prism-devrel/case-studies/rule30/) | Walkthrough | 4 | Who the Rule 30 model is for and what they care about. Then how those concerns became facets. |
| [Architecture walkthrough](https://afflom.github.io/prism-devrel/case-studies/rule30/architecture/) | Walkthrough | 37 | Who Rule 30 is for, what they care about, its parts and how they connect. |
| [Security and threat model](https://afflom.github.io/prism-devrel/case-studies/rule30/security/) | Walkthrough | 20 | The assets of Rule 30, its threats, risks and controls, and the risks it accepts on purpose. |
| [Quality model (ISO/IEC 25010)](https://afflom.github.io/prism-devrel/case-studies/rule30/quality/) | Reference | 4 | What good quality means for Rule 30, and the numbers that measure it. |
| [Behavior and proofs](https://afflom.github.io/prism-devrel/case-studies/rule30/behavior/) | Reference | 2119 | Every theorem of Rule 30, and how it is proved. The Lean kernel checks each one. |
| [Slides and video script](https://afflom.github.io/prism-devrel/case-studies/rule30/slides/) | Slides and script | 4 | One slide for each facet of Rule 30, with a script to read over it. |
| [Record explorer](https://afflom.github.io/prism-devrel/case-studies/rule30/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](https://afflom.github.io/prism-devrel/case-studies/rule30/agents/) | 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. |

## Facets of Rule 30

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

| Facet | Records |
| --- | --- |
| [Architecture](https://afflom.github.io/prism-devrel/facets/architecture/) | 37 |
| [Security and threat model](https://afflom.github.io/prism-devrel/facets/security/) | 20 |
| [Quality](https://afflom.github.io/prism-devrel/facets/quality/) | 4 |
| [Behavior and proofs](https://afflom.github.io/prism-devrel/facets/behavior/) | 2119 |

