Docs Case studies UORust Case studies: System and release // case study · UORust
System and release What UORust ships, its release manifest, and how its holo goes live.
Otto Maintainer
“How do releases and re-pins happen on their own?”
Explanation: read it end to end, away from the keyboard.
Subject: UORust at commit afd5cea950a8 , 331 facet records , source digest f3f743b6834adaff.
System and release records by kind SystemManifest: 1 records; SystemModel: 1 records SystemManifest 1 SystemModel 1
System and release records by kind. The 2 records this page teaches, one bar for each kind. Each kind has its own section below.The data in this figure records SystemManifest 1 SystemModel 1
The system facet is the production system model. It names the product, its application profile, and the artifacts and targets it ships to. The release manifest binds them together. See PrismPM SPEC section 11 and Ship .
The manifest names the application model digest the release must match. System and release facet explains the facet for every Prism model , with the counts of every case study.
Every record Index Record Kind Name 323 System::systemManifestSystemManifest systemManifest 324 System::systemModelSystemModel systemModel
SystemManifest (1) systemManifest System::systemManifest SystemManifest #323 source
applicationModelDigest sha256:a2f3e6e8d6d66c70e2351a24478ffbbe7cef7c26eed9279f47ee0fbe9757af05productId uorustproductVersion 0.1.1componentId uorust-browserartifactId uorust-applicationtargetId pagescontrols application-acceptanceartifact-closuresource-proofspdxTaught by System and release , Slides and video script
SystemModel (1) systemModel System::systemModel SystemModel #324 source
systemModel 7 entries product Product id uorustowner UOR Foundationversion 0.1.1lifecycle developmentsourcePolicy selected LexLean source and kernel proofsupportedPlatforms applicationProfile ApplicationProfile contract prismpm/browser-resident-application/1applicationModelDigest sha256:a2f3e6e8d6d66c70e2351a24478ffbbe7cef7c26eed9279f47ee0fbe9757af05execution browser-sessionpersistentStorage noneexternalServices noneresources capabilities portable-static-holo-applicationartifacts GeneratedArtifact id uorust-applicationrole selected-applicationlicenseExpression MIT OR Apache-2.0components Component id uorust-browserartifact uorust-applicationkind browserversion 0.1.1targets Target id pageskind github-pages-browseradapterDigest sha256:59df071a35deca05e62224e43b82d7bc9b5c649f989a3424fd704123633a539eapiVersion github-pages-artifact@v4minimumReleaseStatus developmentcontrols application-acceptanceartifact-closuresource-proofspdxstandards Taught by System and release
explanation Scale case study Markdown
Words on this page 4 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.