Explanation: How one prompt becomes every 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.
The data in this figure
| From | Link | To |
|---|---|---|
| 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
| Prompt | Facet | Records | Checked against |
|---|---|---|---|
| app (prism/spec/1) | Behavior | the model the guest is built from, a theorem per property, acceptance vectors | LexLean, Lean kernel, prismpm verify |
| stakeholders, concerns, components | Architecture | stakeholders, concerns, components, edges, viewpoints, views | ISO/IEC/IEEE 42010:2022 |
| (derived from app) | Design views | an OPM object-process view; UML component, sequence and state-machine views | ISO/PAS 19450, OMG UML 2.5.1 |
| journeys | Features and journeys | a feature per rule and property, a journey per stakeholder | PrismPM features (PP2014 to PP2018) |
| threats | Security and threat model | assets, STRIDE threats, risks, controls with evidence, accepted risks | ISO/IEC 27034, 27005 (PP2019 to PP2022) |
| quality | Quality | characteristics, subcharacteristics, requirements, measures with thresholds | ISO/IEC 25010:2023 |
| pattern, machine | Behavior and compliance | the 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 states | OMG DMN 1.5, OASIS XACML 3.0, OMG UML 2.5.1 |
| license | Compliance | an obligation per standard, each naming its evidence | the standards above, SPDX |
| repository | System and release | prism.toml granting nothing, site/app.json, register rows, scenarios, tests, OpenSpec | UOR-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.
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.