Docs Case studies Foundry Case studies: How Foundry was modeled // case study · Foundry
How Foundry was modeled Who the Foundry model is for and what they care about. Then how those concerns became facets .
Iris Prism modeler
“Is every record here traced back to its source?”
Explanation: read it end to end, away from the keyboard.
The records of Foundry by facet Behavior and proofs: 247 records; Application: 1 records Behavior and proofs 247 Application 1
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 proofs 247 Application 1
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/1cargoName prism-forge-kernelcargoVersion 0.1.0cargoDescription 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/PrismPMcargoHomepage https://github.com/UOR-Foundation/PrismPMlibraryRoots PrismForgeKernel.EventAdmission.admitEventPrismForgeKernel.FeatureComposition.admitCompositionPrismForgeKernel.ForgeKernel.dispatchPrismForgeKernel.ProposalAdmission.admitProposalPrismForgeKernel.WorkOwnership.initializePrismForgeKernel.WorkOwnership.transitionacceptanceVectors (previewAcceptance)entryRoot PrismForgeKernel.ForgeKernel.dispatchcoreContract hologram:guest/core-wasm@1requestMaximum (32776 : UInt32)responseMaximum (4096 : UInt32)guestAllocationMaximum (32784 : UInt32)capabilitiesEmpty truefatArchive trueprimaryLayer (0 : UInt8)viewLayer (1 : UInt8)view TextView title Forge kernelheading Forge kernelinputLabel Request: phase event, or gate origin effect record granted deniedsubmitLabel DecideoutputLabel AnswerinputError Invalid requestresponseError Invalid responseTaught 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 Page Modality Records What you get How Foundry was modeled Walkthrough 1 Who the Foundry model is for and what they care about. Then how those concerns became facets. Behavior and proofs Reference 247 Every theorem of Foundry, and how it is proved. The Lean kernel checks each one. Slides and video script Slides and script 2 One slide for each facet of Foundry, with a script to read over it. Record explorer Interactive 0 Search every record of Foundry by name, facet or text. Each result links to the pages that teach it. llms.txt and Markdown twins Agent twin 0 The 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:
explanation Evaluate case study Markdown
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).