// 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
The data in this figure
| Step | What happens |
|---|---|
| 1. 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? |
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
- 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
- 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
- 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
- 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
- 01 · DiscoverWhat is Prism, and is it for me?
- 5 case studies from Slides and video script
- 02 · EvaluateDoes Prism solve my problem, and can I trust what it claims?
- How one prompt becomes every facet explanation
- 12 case studies from Case studies
- 03 · LearnHow do I build my first working app?
- 2 tutorials from Turn a Rust project into a Prism model
- The facets of a Prism app reference
- 9 explanation from Architecture facet
- 7 case studies from Architecture walkthrough
- 04 · BuildHow do I make my app do what I need?
- 6 how-to guides from How to build a decision table app
- 2 reference from Prompt reference
- 34 examples from Example apps
- 19 case studies from Behavior and proofs
- 05 · ScaleHow do I ship, maintain and grow what I built?
- System and release case study
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.
- KaiDeveloper new to PrismA working Prism model of my own Cargo workspace, without writing it by hand.
- IrisPrism modelerTo see how a complete model is laid out, one record kind at a time.
- VeraSecurity reviewerEvidence that what the model claims about threats and controls is true.
- WrenDevRel authorTo know which records no page teaches yet, and who each page is for.
- OttoMaintainerEverything kept in step when the subject changes, with no generated page edited by hand.
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.
- Decision tables 21 pages
- Policy decisions 6 pages
- State machines 6 pages
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.
- UORust 13 pages
- Prism-DevRel 11 pages
- Rule 30 8 pages
- Verdant Resonance 6 pages
- Foundry 5 pages
Four kinds of documentation
The data in this figure
| while you study | while you work | |
|---|---|---|
| to do | Tutorials | How-to guides |
| to know | Explanation | Reference |
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.