Skip to content
UOR-FoundationPublic

About

Build, run and ship self-verifying AI applications that just work. From edge to cloud.

Topics

Resources

Code of conduct

Contributing

Security policy

Stars

5 stars

Watchers

0 watching

Forks

Latest commit

 

History

1,824 Commits

Folders and files

NameName
Last commit message
Last commit date
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 

PrismPM

PrismPM compiles authoritative Prism models into verified software artifacts. A model is a closed .lex.tex source graph: LexLean produces its semantic snapshot and Lean, Lean checks the proofs, lean4-prod exports only named verified roots, and generic generators produce Cargo, Core-Wasm, View, browser, and Hologram artifacts. Prism application behavior is never supplied by handwritten Lean or target-specific application code.

The historical v0.1.0 release is a systems-modeling prototype; v0.2.0 introduced portable applications. The production-system SDK candidate is v0.4.0, and it is releasable only when the generated prism-stdlib and prism-calculator crates, Calculator.holo, the independent Hologram execution evidence, and the public calculator-example Pages application and complete CalculatorSystem reference all pass the atomic release contract in SPEC.md.

Version 0.4.0 is not an accepted production-system release. Component tests, contract fixtures and a successful Pages upload do not establish that acceptance. Release status records the remaining release boundaries.

Artifact model

authoritative .lex.tex + lock
             |
             +-- LexLean snapshot, generated Lean/LaTeX, proof evidence
             +-- lean4-prod LCNF and named-root coverage
             +-- generated Cargo crate and registry package
             +-- import-free hologram:guest/core-wasm@1 guest
             +-- evaluated View -> portable HOLOVIEW + browser adapter/assets
             `-- binary Hologram v4 ApplicationName.holo

hologram-live is the .holo format authority. Holo/1 is the Prism profile defined by prism-stdlib; its physical container is Hologram archive version 4. Every .holo begins with HOLO\x04\x00. model.prism.json is the separate canonical Prism model document. JSON is never accepted as a .holo archive.

Calculator: getting started

Open this repository in its VS Code devcontainer. From the container shell:

cargo run --locked --offline -p prismpm -- \
  --project examples/Calculator check
cargo run --locked --offline -p prismpm -- \
  --project examples/Calculator build
cargo run --locked --offline -p prismpm -- \
  --project examples/Calculator verify

The project root is examples/Calculator. Its sole application authority is src/Calculator.lex.tex plus lexlean.lock. Successful verification writes a content-addressed build beneath examples/Calculator/.prism/build/ and an acceptance result beneath examples/Calculator/.prism/verified/. The build contains:

  • Calculator.holo, the composed Core-Wasm plus portable View application;
  • cargo/prism-calculator-0.1.0.crate and its complete generated package;
  • core-wasm/prism_calculator_core_wasm.wasm;
  • generated Hologram and browser View artifacts; and
  • the model, Lean, LCNF, provenance, identity, and manifest evidence.

Inspect and headlessly plan the archive with the pinned Hologram Live binary:

hologram --json holo inspect path/to/Calculator.holo
hologram --json holo plan path/to/Calculator.holo

The ordinary headless plan intentionally reports that the portable View surface is unavailable. prismpm verify also builds the pinned independent Hologram oracle and opens the same archive with a display-independent portable surface, runs every modeled request directly and through View intents, then checks detach and idempotent shutdown.

After publication, ordinary Rust consumers use the generated API:

[dependencies]
prism-calculator = "=0.1.0"
use prism_calculator::{calculate, Operation};

assert_eq!(calculate(Operation::Add, 20, 22), Ok(42));

The public reference application is UOR-Foundation/calculator-example. Its publication contract requires the exact content-addressed model, repeated PrismPM acceptance, the published registry crate and only the generated browser closure (six files before closure v2, sixteen since; see SPEC §1.2.1). Registry publication remains deferred as recorded in release status.

Verification scope

CONFORMANCE.md is the generated capability/test inventory. VERIFICATION.md records revision-specific component evidence; it is not a substitute for current complete SDK, downstream and live acceptance. The Browser application profile remains refused with PP2011 until its generated runtime, authenticated effects, durable recovery and full owning verification are complete. The Server application profile declares and validates its host effects and generates a host adapter (an API package and a driver package that links a workspace binding) with a scripted-host acceptance suite; the core of a server application is built through production (PP2025 refuses an export the host adapter cannot bound), a served application listens on the loopback interface only and answers RFC 9112 requests through the generated adapter, and prismpm verify of a server application builds the consumer's locked workspace around the production core and accepts the program (every vector with its effect transcript, the binding and the served exchanges); a release of one holds the consumer's workspace, assembly and every replay check its acceptance against the model and the released files, and prismpm replay-acceptance rebuilds the released program and answers every vector without the source.

Development and acceptance

The host needs only Git, Docker with Buildx, the Dev Container CLI, and repository credentials. Rust, Lean, Wasm, Node, browser, and conformance tools run inside the pinned devcontainers. Dependency acquisition is an explicit setup phase; build and acceptance are locked and offline afterward.

just vv

just vv is the normative repository gate. Application completion is reported only by prismpm/application-acceptance/1, and ecosystem completion additionally requires the final cross-repository release manifest. See CONFORMANCE.md, ERRORS.md, and VERIFICATION.md.

For a built immutable product release, prismpm conformance NAME@sha256:DIGEST runs the SDK-contained registered feature and diagnostic corpus and attaches its digest-bound canonical production-acceptance transcript. The same command is available through the shared action; it does not rebuild the release or infer coverage from registry membership.

prismpm export-browser NAME@sha256:DIGEST --output site exports an already acquired release's exact browser files after source-free integrity replay. The destination must be new, in a caller-owned project directory without group or other write permission. This does not authorize publication or establish product acceptance; a publisher must verify those separately before deployment.

A template instance whose system model names the github-pages-browser target publishes to GitHub Pages from one workflow file: copy action/starter/publish-pages.yml to .github/workflows/publish-pages.yml and pin the PrismPM Action revision. Its one job runs the shared Action's publish-pages command, which builds the locked release once, runs export-browser on it, checks the exported files against the release's system manifest and build manifest digests, and refuses a system manifest that does not name the Pages target before anything is uploaded; the commit-pinned actions/upload-pages-artifact and actions/deploy-pages then publish the checked closure. The check is byte integrity against the release's own evidence, not deployment acceptance.

Key Documents

  • RELEASE-STATUS.md — Current release status and required acceptance
  • VERIFICATION.md — Detailed verification evidence, digests, and test descriptions
  • SPEC.md — Atomic release contract specification
  • docs/vocabulary.md — Prism nouns and verbs mapped to Docker's
  • CONFORMANCE.md — Conformance requirements
  • COMPLIANCE.md — Generated matrix of which runtime passes which part of the runtime contract
  • ERRORS.md — Error code registry
  • STABILITY.md — Stability tiers and pre-1.0 versioning policy
  • RELEASES.md — How releases are cut, what each may contain, and support windows
  • SECURITY.md — How to report a vulnerability, and how to verify a release

About

Build, run and ship self-verifying AI applications that just work. From edge to cloud.

Topics

Resources

Code of conduct

Contributing

Security policy

Stars

5 stars

Watchers

0 watching

Forks

Releases

Packages

Contributors

Languages