PrismDevRelOpen the app
Case studies: How Foundry 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 · Foundry

How Foundry was modeled

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

The records of Foundry by facetBehavior and proofs: 247 records; Application: 1 recordsBehavior and proofs247Application1
The records of Foundry by facet. Every record of the Foundry model, counted by facet. Each one is taught by at least one page of this case study.
The data in this figure
records
Behavior and proofs247
Application1

Foundry says what it is in its own model:

Decide the next build phase of a Hologram Forge app, whether an origin may use an effect, and the experience rules Forge is held to.

Subject: Foundry at commit 5fa2a21e5aca, 248 facet records, source digest 6e5e13608777e1a0.

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

Records
248
Covered
248
Pages
5
Facets
2

People, concerns and the application

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

Forge kernel

ForgeKernel::application TextApplication #79 source

Forge kernel 18 entries
profile
prismpm/text-application/1
cargoName
prism-forge-kernel
cargoVersion
0.1.0
cargoDescription
Decide the next build phase of a Hologram Forge app, whether an origin may use an effect, and the experience rules Forge is held to.
cargoRepository
https://github.com/UOR-Foundation/PrismPM
cargoHomepage
https://github.com/UOR-Foundation/PrismPM
libraryRoots
  • PrismForgeKernel.EventAdmission.admitEvent
  • PrismForgeKernel.FeatureComposition.admitComposition
  • PrismForgeKernel.ForgeKernel.dispatch
  • PrismForgeKernel.ProposalAdmission.admitProposal
  • PrismForgeKernel.WorkOwnership.initialize
  • PrismForgeKernel.WorkOwnership.transition
acceptanceVectors
(previewAcceptance)
entryRoot
PrismForgeKernel.ForgeKernel.dispatch
coreContract
hologram:guest/core-wasm@1
requestMaximum
(32776 : UInt32)
responseMaximum
(4096 : UInt32)
guestAllocationMaximum
(32784 : UInt32)
capabilitiesEmpty
true
fatArchive
true
primaryLayer
(0 : UInt8)
viewLayer
(1 : UInt8)
view
TextView
title
Forge kernel
heading
Forge kernel
inputLabel
Request: phase event, or gate origin effect record granted denied
submitLabel
Decide
outputLabel
Answer
inputError
Invalid request
responseError
Invalid response

Taught by How Foundry was modeled, Slides and video script

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 Foundry was modeledWalkthrough1Who the Foundry model is for and what they care about. Then how those concerns became facets.
Behavior and proofsReference247Every theorem of Foundry, and how it is proved. The Lean kernel checks each one.
Slides and video scriptSlides and script2One slide for each facet of Foundry, with a script to read over it.
Record explorerInteractive0Search every record of Foundry by name, facet or text. Each result links to the pages that teach it.
llms.txt and Markdown twinsAgent twin0The Foundry case study as plain text for agents. It has llms.txt, a twin of each page and a feed.

Facets of Foundry

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