PrismDevRelOpen the app
Explanation: How one prompt becomes every facet

Evaluate

How one prompt becomes every facet

Learn

Architecture facetDesign views facetFeatures and journeys facetSecurity and threat model facetQuality facetBehavior and proofs facetSystem and release facetExtension facets facetApplication facet

// explanation · Evaluate

How one prompt becomes every facet

Why the behavior and a few choices determine a whole Prism app, and what checks each facet.

A Prism app is one model with several facets, each with its own standard. Every facet but behavior follows from the behavior by fixed rules. A rule becomes a feature. A property becomes a control whose evidence is a proof. The request size limit becomes a quality threshold. So a prompt that states the behavior, and only what cannot be derived from it, decides the whole app. The builder writes it the same way every time.

What each part of a prompt becomes18 nodes and 9 links. app (prism/spec/1) to Behavior; stakeholders, concerns, components to Architecture; (derived from app) to Design views; journeys to Features and journeys; threats to Security and threat model; quality to Quality; pattern, machine to Behavior and compliance; license to Compliance; repository to System and release.app (prism/spec/1)stakeholders, concerns, components(derived from app)journeysthreatsqualitypattern, machinelicenserepositoryBehaviorArchitectureDesign viewsFeatures and journeysSecurity and threat modelQualityBehavior and complianceComplianceSystem and releaseWhat each part of a prompt becomes18 nodes and 9 links. app (prism/spec/1) to Behavior; stakeholders, concerns, components to Architecture; (derived from app) to Design views; journeys to Features and journeys; threats to Security and threat model; quality to Quality; pattern, machine to Behavior and compliance; license to Compliance; repository to System and release.app (prism/spec/1)stakeholders, concerns,components(derived from app)journeysthreatsqualitypattern, machinelicenserepositoryBehaviorArchitectureDesign viewsFeatures and journeysSecurity and threat modelQualityBehavior and complianceComplianceSystem and release
What each part of a prompt becomes. Left, the parts of a prompt. Right, the facets of the app the builder writes from them. Design views come from the app itself.
The data in this figure
FromLinkTo
app (prism/spec/1)→Behavior
stakeholders, concerns, components→Architecture
(derived from app)→Design views
journeys→Features and journeys
threats→Security and threat model
quality→Quality
pattern, machine→Behavior and compliance
license→Compliance
repository→System and release

One prompt, every facet

One prompt, every facet 9 rows
PromptFacetRecordsChecked against
app (prism/spec/1)Behaviorthe model the guest is built from, a theorem per property, acceptance vectorsLexLean, Lean kernel, prismpm verify
stakeholders, concerns, componentsArchitecturestakeholders, concerns, components, edges, viewpoints, viewsISO/IEC/IEEE 42010:2022
(derived from app)Design viewsan OPM object-process view; UML component, sequence and state-machine viewsISO/PAS 19450, OMG UML 2.5.1
journeysFeatures and journeysa feature per rule and property, a journey per stakeholderPrismPM features (PP2014 to PP2018)
threatsSecurity and threat modelassets, STRIDE threats, risks, controls with evidence, accepted risksISO/IEC 27034, 27005 (PP2019 to PP2022)
qualityQualitycharacteristics, subcharacteristics, requirements, measures with thresholdsISO/IEC 25010:2023
pattern, machineBehavior and compliancethe pattern's obligation; for a state machine its states and transitions, a UML state-machine view, and theorems that final states are never left and no run leaves the reachable statesOMG DMN 1.5, OASIS XACML 3.0, OMG UML 2.5.1
licenseCompliancean obligation per standard, each naming its evidencethe standards above, SPDX
repositorySystem and releaseprism.toml granting nothing, site/app.json, register rows, scenarios, tests, OpenSpecUOR-Foundation/template gate and Pages

Each facet has its own page, with how every case study declares it. See the facets and the case studies.

From structure to language

The prompt is structured like an MCP tool call, so every part of it is checked before anything is written. An example the rules contradict is refused with the reason. So is a property with a counterexample. Plain language can sit in front of it: a sentence becomes this prompt, then goes through the same checks, facets and proofs.

explanationEvaluateMarkdown

Words on this page 3
facet
One view of a model, such as its architecture, its security or its quality. Each facet holds records.
MCP
Model Context Protocol: an open protocol through which AI agents call tools such as the Prism builder.
prompt
One JSON document that describes an app. The builder turns it into every facet of a Prism model.