PrismDevRelOpen the app

// Prism practice

Build complete Prism apps.

This is where the UOR Foundation works out how to build a complete Prism app, and refines the way it is done. New to Prism? Start at uor.foundation, the Foundation's home for Prism and the Foundry portal.

Every practice here is shown on real projects and checked before it goes live. Start with a tutorial, follow a how-to guide for the task in front of you, and look up details in the reference. Copy an example, or study a whole project in a case study. What works here goes back upstream to uor.foundation and Foundry, so the whole ecosystem builds on it.

Start buildingOpen the appNew to Prism? Start at uor.foundation

Your developer journey1. Discover: Wren: What is Prism, and is it for me? 2. Evaluate: Iris: Does Prism solve my problem, and can I trust what it claims? 3. Learn: Iris: How do I build my first working app? 4. Build: Iris: How do I make my app do what I need? 5. Scale: Otto: How do I ship, maintain and grow what I built?01DiscoverWren: What isPrism, and isit for me?02EvaluateIris: DoesPrism solvemy problem,and can Itrust what itclaims?03LearnIris: How doI build myfirst workingapp?04BuildIris: How doI make my appdo what Ineed?05ScaleOtto: How doI ship,maintain andgrow what Ibuilt?Your developer journey1. Discover: Wren: What is Prism, and is it for me? 2. Evaluate: Iris: Does Prism solve my problem, and can I trust what it claims? 3. Learn: Iris: How do I build my first working app? 4. Build: Iris: How do I make my app do what I need? 5. Scale: Otto: How do I ship, maintain and grow what I built?01DiscoverWren: What is Prism, and is itfor me?02EvaluateIris: Does Prism solve myproblem, and can I trust what itclaims?03LearnIris: How do I build my firstworking app?04BuildIris: How do I make my app dowhat I need?05ScaleOtto: How do I ship, maintain andgrow what I built?
Your developer journey. The 5 stages of the developer journey, as Caroline Lewko and James Parton describe it. Each shows the question you bring to it and the guide you meet there.
The data in this figure
StepWhat happens
1. DiscoverWren: What is Prism, and is it for me?
2. EvaluateIris: Does Prism solve my problem, and can I trust what it claims?
3. LearnIris: How do I build my first working app?
4. BuildIris: How do I make my app do what I need?
5. ScaleOtto: How do I ship, maintain and grow what I built?

Ways to start building

Pick the one closest to what you have: an idea, existing code, or an app like yours.

Ways to start building 4 items
  1. tutorialTurn a Rust project into a Prism modelRun UORust on a sample workspace and check what it writes. Then read a Rust function beside the LexLean it became.Learn
  2. tutorialBuild your first Prism appDescribe your app once, as a structured prompt, and Prism writes every facet of it, proves what it promises and publishes it.Learn
  3. ExamplesExample appsSmall apps, each built from one prompt and verified, grouped by the pattern they follow. Copy one and change it.Decision tables 21 · Policy decisions 6 · State machines 6
  4. Case studiesCase studiesWhole Prism projects, read record by record at a pinned commit, from their users to their proofs. Each one updates as its project grows.UORust 13 · Prism-DevRel 11 · Rule 30 8 · Verdant Resonance 6 · Foundry 5

Your developer journey

The pages for each stage.

Your developer journey 5 items
  1. 01 · DiscoverWhat is Prism, and is it for me?
  2. 02 · EvaluateDoes Prism solve my problem, and can I trust what it claims?
  3. 03 · LearnHow do I build my first working app?
  4. 04 · BuildHow do I make my app do what I need?
  5. 05 · ScaleHow do I ship, maintain and grow what I built?

Meet your guides

The readers this site is written for, one for each stakeholder of the model. Each page names the guide it was written for.

Examples and case studies

Beside the four Diátaxis types, two collections of worked material: example apps and case studies.

Examples

Small apps, each built from one prompt and verified, grouped by the pattern they follow. Copy one and change it. Example apps.

Examples by patternDecision tables: 21 pages; Policy decisions: 6 pages; State machines: 6 pagesDecision tables21Policy decisions6State machines6
Examples by pattern. 3 patterns in the examples collection. Each bar is one pattern and how many pages it holds.
The data in this figure
pages
Decision tables21
Policy decisions6
State machines6

Case studies

Whole Prism projects, read record by record at a pinned commit, from their users to their proofs. Each one updates as its project grows. Case studies.

Case studies by projectUORust: 13 pages; Prism-DevRel: 11 pages; Rule 30: 8 pages; Verdant Resonance: 6 pages; Foundry: 5 pagesUORust13Prism-DevRel11Rule 308Verdant Resonance6Foundry5
Case studies by project. 5 projects in the case studies collection. Each bar is one project and how many pages it holds.
The data in this figure
pages
UORust13
Prism-DevRel11
Rule 308
Verdant Resonance6
Foundry5

Four kinds of documentation

Four kinds of documentationTutorials (while you study, to do): 2 pages; How-to guides (while you work, to do): 6 pages; Reference (while you work, to know): 3 pages; Explanation (while you study, to know): 10 pageswhile you studywhile you workto knowto doTutorials2 pagesHow-to guides6 pagesReference3 pagesExplanation10 pages
Four kinds of documentation. Daniele Procida's Diátaxis. Each page does one of four jobs. Across: whether you are studying or working. Up: whether the page helps you do or helps you know.
The data in this figure
while you studywhile you work
to doTutorialsHow-to guides
to knowExplanationReference

Every page, by stage and type

Every page, by stage and type 5 rows
Words on this page 9
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.
Diátaxis
A way of organizing documentation into four kinds: tutorials, how-to guides, reference and explanation.
stakeholder
A person or group with an interest in the system, as ISO/IEC/IEEE 42010 defines it.
UOR
Universal Object Reference: the UOR Foundation's framework for naming any object by its content.
decision table
A table of rules, as in OMG DMN 1.5: each row says which inputs lead to which outcome.
developer journey
The stages a developer goes through with a product: discover, evaluate, learn, build and scale (Lewko and Parton).
prompt
One JSON document that describes an app. The builder turns it into every facet of a Prism model.