Skip to content
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
25 commits
Select commit Hold shift + click to select a range
acb321b
docs(adr): ADR-016 .holo normative home, canonical bytes, version policy
humuhumu33 Oct 29, 2026
036832b
Merge origin/main into adr/016-holo-canonical-bytes
humuhumu33 Nov 1, 2026
817fd35
feat(workbench): render the workbench in the Hologram brand on shadcn…
humuhumu33 Nov 5, 2026
8ba214f
test(workbench): drive the keyboard-only journey through native multi…
humuhumu33 Nov 5, 2026
898acb0
test(golden): refresh the shared goldens and rebind ct-02 for the Hol…
humuhumu33 Nov 5, 2026
b1e877f
test(golden): import the reviewed native records for the Hologram wor…
humuhumu33 Nov 5, 2026
d55302b
style(prism-code): give the dev studio the Hologram tokens and shadcn…
humuhumu33 Nov 5, 2026
7a5301d
feat(holo): prismpm build writes the build provenance statement (part…
humuhumu33 Nov 5, 2026
f742c5c
feat(view): widen the design catalogue to the Hologram roles and prov…
humuhumu33 Nov 5, 2026
898dcdf
feat(view): ship browser closure v2 with Hologram fonts, icons and a …
humuhumu33 Nov 5, 2026
88e2c4c
test(golden): refresh the shared goldens and rebind ct-02 for closure…
humuhumu33 Nov 5, 2026
deb2f2e
chore(golden): sign off the provenance change to the application gene…
humuhumu33 Nov 5, 2026
25b426b
test(golden): import the reviewed native records for closure v2 and t…
humuhumu33 Nov 5, 2026
1a247ad
Merge origin/main into adr/016-holo-canonical-bytes
humuhumu33 Nov 5, 2026
68104d7
fix(ci): pass the format gate, the prism-code size cap and the docs l…
humuhumu33 Nov 5, 2026
4a4f0b1
fix(ci): keep every packed npm text file LF on Windows checkouts
humuhumu33 Nov 5, 2026
5be4eee
test(golden): refresh the shared goldens for the merge of main
humuhumu33 Nov 5, 2026
6392c78
Merge remote-tracking branch 'origin/main' into merge/adr-016-main
humuhumu33 Nov 5, 2026
1e1d01e
build(prism-code): raise the package cap to 1212 KiB for closure v2 a…
humuhumu33 Nov 5, 2026
984436e
fix(ci): pass rustfmt, the module check and the fixtures on PR 550
humuhumu33 Nov 5, 2026
f1e4ea3
Merge origin/main (#549) into adr/016-holo-canonical-bytes
humuhumu33 Nov 5, 2026
526d392
test(golden): refresh the shared goldens for the merge of main (#549)
humuhumu33 Nov 5, 2026
fd39da7
test(golden): import the reviewed native records for the merge of mai…
humuhumu33 Nov 5, 2026
70322f4
test(release): the product evidence fixture lists the closure v2 export
humuhumu33 Nov 5, 2026
46c344c
test(hologram): refresh the reviewed oracle pins for closure v2
humuhumu33 Nov 5, 2026
File filter

Filter by extension

Filter by extension


Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
8 changes: 8 additions & 0 deletions .gitattributes
Original file line number Diff line number Diff line change
Expand Up @@ -9,6 +9,14 @@ sdk/npm/**/*.mjs text eol=lf
sdk/npm/**/*.rego text eol=lf
sdk/npm/**/*.d.ts text eol=lf
sdk/npm/**/*.json text eol=lf
sdk/npm/**/*.md text eol=lf
sdk/npm/**/*.css text eol=lf
sdk/npm/**/*.html text eol=lf
sdk/npm/**/*.toml text eol=lf
sdk/npm/**/*.tex text eol=lf
sdk/npm/**/*.sh text eol=lf
sdk/npm/**/*.wit text eol=lf
sdk/npm/**/*.lock text eol=lf
schemas/**/*.json text eol=lf
# The matrix is generated and compared byte for byte; the corpus is hashed (#287).
COMPLIANCE.md text eol=lf
Expand Down
4 changes: 2 additions & 2 deletions .github/workflows/npm-prism-code.yml
Original file line number Diff line number Diff line change
Expand Up @@ -125,8 +125,8 @@ jobs:
npm pack --dry-run --json > pack.json
size=$(node -e 'console.log(JSON.parse(require("fs").readFileSync("pack.json","utf8"))[0].unpackedSize)')
echo "unpacked size: $size bytes"
# 1320 KiB is the prism-code package cap. prism-code vendors the @prism-code/verify build (src/vendor/verify.mjs, about 288 KiB, so holo.verify() has no dependency) and adds its own code. Raised from 768 KiB to fit the M3 features in flight (export, middleware, generate, replay, about 115 KiB together), then to 1088 KiB for the authoring front door (#325, about 65 KiB), then to 1160 KiB for setup and open: the agent configuration, the bundled prism skill (16 KB) and the holo:// handler (about 63 KiB), then to 1208 KiB for the machine half of setup, the build tiers, axioms and init's next steps (about 44 KiB), then to 1320 KiB for prism-code mcp, the guided journey (#325, about 110 KiB); the next lever is depending on @prism-code/verify once it is published instead of vendoring it.
test "$size" -le 1351680
# 1324 KiB is the prism-code package cap. prism-code vendors the @prism-code/verify build (src/vendor/verify.mjs, about 288 KiB, so holo.verify() has no dependency) and adds its own code. Raised from 768 KiB to fit the M3 features in flight (export, middleware, generate, replay, about 115 KiB together), then to 1088 KiB for the authoring front door (#325, about 65 KiB), then to 1160 KiB for setup and open: the agent configuration, the bundled prism skill (16 KB) and the holo:// handler (about 63 KiB), then to 1208 KiB for the machine half of setup, the build tiers, axioms and init's next steps (about 44 KiB), then to 1320 KiB for prism-code mcp, the guided journey (#325, about 110 KiB), then to 1324 KiB for closure v2 provenance verification and the Hologram studio stylesheet (about 2.7 KiB); the next lever is depending on @prism-code/verify once it is published instead of vendoring it.
test "$size" -le 1355776
node scripts/check-package.mjs pack.json
rm pack.json
- name: The entry points import cleanly
Expand Down
8 changes: 7 additions & 1 deletion CHANGELOG.md
Original file line number Diff line number Diff line change
Expand Up @@ -18,6 +18,10 @@ To move to 1.0, read the [migration guide](docs/site/migration/to-1-0.md).
## [Unreleased]

### Features Added
- Browser closure v2 (SPEC §1.2.1): every generated browser page, the Text/1 page and the Text/3 workbench, now ships the Hologram brand beside the six-file page: Geist, Geist Mono and Archivo web fonts with their OFL licences, `icon.svg`, `icon-512.png` and a per-application `manifest.webmanifest`, so pages render in the brand fonts and install on phones with no remote request. The files are the pinned `hologram-brand` vendored dependency (`vendor/hologram-brand`). `provenance.json` becomes `prismpm/browser-provenance/2`, which names the SHA-256 of every other closure file; `prism-code` verifies both versions.
- The generated workbench and the `prism-code dev` studio use the Hologram tokens on shadcn/ui new-york-v4 anatomy (warm paper and warm dark grounds, one brand mark, shadcn buttons, inputs, cards, alerts, tables and tabs). Three brand-kit values that fail WCAG are corrected in the adapter: the focus ring, light destructive text and brand orange as text.
- The private DK-38 design catalogue grows to 25 tokens per theme (nine appended colors and a Hologram font family), and admission now requires WCAG text contrast of 4.5:1 and focus contrast of 3:1 through a conservative integer rule. `HologramDesign.lex.tex`, generated from the brand kit's tokens by `scripts/hologram-design.mjs`, proves its catalogue admitted by kernel evaluation with no axioms.
- `prismpm build` writes provenance by default (#268, `docs/proposals/268-build-provenance.md`, experimental, part 2 of 2): every holo a plain `prismpm build` writes carries one unsigned SLSA provenance v1 statement in its attestation section, with no flag. Min mode, the default, holds the same bytes as `prism-code`'s `provenanceBundle` and is deterministic; `--provenance=max` adds the arguments, platform, invocation id and timestamps; `--no-provenance` writes none and warns that the holo can never reach P1. The statement is a placeholder with an empty signature, so a built holo stays P0 until `attest` adds a signed one. `PP3018` is new. A product release (`-t`) and the archive `prismpm verify` builds carry no statement, and neither flag combines with `-t`. Conformance HO-32 to HO-35.
- The machine half of `prism-code setup`, build tiers and `prism-code axioms` (experimental). Before the agents, `setup` checks Node 22, finds Docker on the PATH or, on Windows without Docker Desktop, inside a WSL distribution, and records that program in `$PRISM_HOME/config.json`, so every delegated verb spawns it and mounts the project under `/mnt/<drive>/`. It pulls the SDK image the lockfile pins, creates a cache volume per image that later runs mount at `/tmp`, and writes `* text eol=lf` to the project's `.gitattributes`. `prism-code verify --lean` runs `lexlean verify` alone, without the Docker socket: every theorem with its exact axiom policy, about a minute. `prism-code axioms` compiles the project once and reports the axiom set Lean observes for every declaration beside the declared one; `--write` sets them. See `sdk/npm/prism-code/CHANGELOG.md`.
- `prism-code setup` and `prism-code open` (experimental): one run of `npx prism-code@latest setup` adds the UOR MCP server (`lexlean`, `https://mcp.uor.foundation/`) to every agent it finds on the machine, registers a `holo://` link handler for the OS, and remembers the preferred agent. Claude Code is configured with `claude mcp add --transport http --scope user`, or in `~/.claude.json` when the CLI is not on the PATH. Codex gets a `[mcp_servers.lexlean]` table, and Cursor and VS Code get their `mcp.json` entries. Claude Desktop gets the Connectors step printed, because its config file takes no remote server. The one `prism` skill, which covers building a new app, the commands and the MCP server, ships in the package and is written to `~/.claude/skills` for Claude Code and `~/.agents/skills` for Codex, Cursor and VS Code; the `prism-sdk` skill an earlier setup installed is removed where setup's marker is. A server already present is left alone, a file that does not parse is never rewritten, and `--dry-run` prints every file and command. The handler is a copy of five package files in `$PRISM_HOME/handler`: under `HKCU\Software\Classes\holo` on Windows, an `osacompile` applet with a `holo` URL type on macOS, and an `x-scheme-handler/holo` desktop entry on Linux. When another program, such as the Hologram app, already opens `holo://`, setup leaves it alone and says so. `prism-code open holo://build?agent=<id>&q=<sentence>` opens a terminal for Claude Code or Codex. The terminal shows the sentence and starts the agent with it as one argument after Enter. Cursor and VS Code get their install link and the sentence on the clipboard. Claude and ChatGPT get their prompt URL. The sentence reaches the agent through a one-time ticket file, never through a shell, Windows Terminal or AppleScript. A link to another host, an unknown agent or parameter, or a sentence over 2000 characters is refused with an `open.*` code and exit 2.
- `prism.volumes` in `prism-code` (#445, experimental, part of the nine-module proposal #440): `create`, `list`, `inspect` and `remove` as a view over the capability file, in `src/volumes.mjs`. A volume is a named, declared store from a provider, not a mounted folder. A host folder, and anything outside the grant, the image's declared world or the active policy, is refused with `CapabilityDeniedError`, and a guest cannot reach a store until host effects land (#216, #217). Not reachable from the package yet, because #441 connects the modules.
Expand All @@ -40,6 +44,8 @@ To move to 1.0, read the [migration guide](docs/site/migration/to-1-0.md).
- The OSCAL structural validator is bound through `standards.lock` as the `oscal-1.1.0-structural` oracle, the `oscal` profile of `prismpm oracle` (#209, SPEC §10.1). Acceptance is JSON structural validity only, not control implementation or whole-standard conformance.

### Breaking Changes
- `prismpm export-browser` and `verify-browser-publication` return `prismpm/browser-export/2` and `prismpm/browser-publication-integrity/2`, whose file lists hold exactly closure v1 (six files) or closure v2 (sixteen). Releases built now export sixteen files, so a consumer that pins the six-file closure or a `/1` receipt, such as a Pages publication contract, must move to closure v2. The `/1` contracts stay registered.
- A plain `prismpm build` of an application now needs a `prismpm/sdk-lock/2` or `/3` lock, because the provenance statement is derived from it (#268). An absent or `/1` lock is refused with `PP3018` before compiling; bind the SDK with `prismpm update --toolchain <digest-ref>`, migrate the lock, or pass `--no-provenance`.
- `experimental_pull` refuses a policy object with members a policy file cannot have (#292), such as `capabilities` or `replay`, with `policy.invalid`, because a pull's policy is what `check` reads. A `policy` that is not a string or an object, such as `null`, is refused the same way; `null` used to mean the default policy, P2. For a holo with an attestation section, the verdict's `holo` member is now the fingerprint of the file as given, as in `check`, and a statement line that cannot be read is reported as `pull.attestation` even when the policy would also fail.
- `experimental_verify`, `experimental_createClient` and `Application.experimental_verify` no longer take `statements` (experimental). Self-written statements with `envelope: { verified: true }` raised a holo from P0 to a passing P2 with no signature checked. They are now refused as an unknown option, `policy.invalid`. `check` with a signer still reaches P1 and P2 from the signed statements in the holo. `@prism-code/verify` keeps the option, for callers that check signatures against a trust root they hold.
- `prism-code run <holo>` no longer exits 1 for every failed verdict (#348): it exits with the code of the error that explains the verdict. A provenance, document or policy reason, which is every holo today, stays 1; a proof reason is 10; a world outside the grant is 2.
Expand All @@ -60,7 +66,7 @@ To move to 1.0, read the [migration guide](docs/site/migration/to-1-0.md).
- `prism-code inspect <holo> [--json] [--format <path>]`, `inspect(bytes)` and `Application.inspect()` (#271): the format revision, every section with sha256 and BLAKE3 of its bytes (ADR-015), the manifest, the model, the provenance, the declared world and the attestations, read from the section table without compiling the guest; `--json` prints `prismpm/holo-inspection/1` as canonical JSON, `--format` prints one value by dotted path and exits 2 when the path has no value.
- `prismpm inspect <path.holo> [--json] [--format <path>]` (#271, the Rust half of the same shape): the archive is read through the modeled `Foundation.Holo.V1.Wire` section table — the format revision, every section with sha256 and BLAKE3 of its bytes (ADR-015), the manifest, the model document, the provenance, the declared world and the attestation list — without compiling the guest, and a test holds the value key for key against the `prismpm/holo-inspection/1` that `prism-code inspect` prints for the reference archive. `--format` prints one value by dotted path and exits 2 when the path has no value or the selector is malformed. A registry-qualified reference still inspects an immutable product release.
- `verifyTransparency(bundle, trustedRoot)` in `@prism-code/verify` (#275, `docs/proposals/275-transparency-log.md`): checks the Rekor v2 inclusion proof, the signed checkpoint and the RFC 3161 timestamps of a Sigstore bundle offline against a pinned trusted root, using the signed time and never the clock; new schema `trusted-root.schema.json` in `@prism-code/spec`, and `integratedTime` is optional in `sigstore-bundle.schema.json` because Rekor v2 omits it. Tested against 22 Sigstore conformance bundles. `prism verify` does not call it yet (#272).
- Build provenance (#268, `docs/proposals/268-build-provenance.md`, experimental, part 1 of 2): the statement every built holo will carry. `@prism-code/spec` gains the `schemas/attestation/provenance-v1.schema.json` predicate schema, the `HoloProvenance` types and the `PROVENANCE` constants (SLSA v1, build type `https://uor.foundation/prism/holo-build/v1`, modes `min` and `max`); `prism-code` gains `provenanceStatement`, `provenanceBundle`, `attachProvenance`, `readProvenance` and `resolvedDependencies`, which derive the statement from the archive and `prismpm.lock` (subjects the four content blobs, builder the pinned SDK image, dependencies the lock), write it as an unsigned bundle in the attestation section, and refuse a lock that does not describe the archive. Min mode records nothing that varies between runs; max mode adds arguments, platform, invocation id and timestamps. `Attestation.signed` reports whether any signature is non-empty. `prismpm build` does not write it yet: the Rust half, with `--provenance=min|max` and `--no-provenance`, follows #267's wire model change.
- Build provenance (#268, `docs/proposals/268-build-provenance.md`, experimental, part 1 of 2): the statement every built holo will carry. `@prism-code/spec` gains the `schemas/attestation/provenance-v1.schema.json` predicate schema, the `HoloProvenance` types and the `PROVENANCE` constants (SLSA v1, build type `https://uor.foundation/prism/holo-build/v1`, modes `min` and `max`); `prism-code` gains `provenanceStatement`, `provenanceBundle`, `attachProvenance`, `readProvenance` and `resolvedDependencies`, which derive the statement from the archive and `prismpm.lock` (subjects the four content blobs, builder the pinned SDK image, dependencies the lock), write it as an unsigned bundle in the attestation section, and refuse a lock that does not describe the archive. Min mode records nothing that varies between runs; max mode adds arguments, platform, invocation id and timestamps. `Attestation.signed` reports whether any signature is non-empty. The Rust half is the entry above.
- `prismpm lock` and `prismpm update` (#265): `lock` writes or refreshes the pinned inputs of `prismpm.lock` without building, leaving every pin that still resolves alone, and `lock --check` fails with PP5401 when the lock is stale; `update` also moves the toolchain and generator pins, `update --toolchain <digest-ref>` pins a new SDK image (creating the lock when absent), and `--dry-run` writes nothing. Both print the old and new digests as `prismpm/sdk-lock-change/1`, and a lock that cannot be resolved exits 2 (PP1101).
- `holo.verify()` and typed errors in `prism-code` (#276, experimental): `experimental_verify(holo, options)`, `Application.experimental_verify()` and `experimental_createClient()` return the `prism/verdict/1` of `@prism-code/verify` (vendored as one file, so the package still has no dependencies) and never report a level the evidence does not support; options come from `PRISM_MINIMUM_LEVEL`, the client and the call, in that order, and `throw: true` throws the failed verdict as the typed error that explains it. `PrismError` is the base of every error; `VerificationError`, `ProofMismatchError`, `CapabilityDeniedError`, `DeterminismViolationError` and `ReplayError` each carry a stable `code` and map to the check ids of a verdict reason. `PrismCodeError` is now a `PrismError` and keeps its codes.
- `prism-code attest` and `prism-code verify-attestation` (#272, experimental, `docs/proposals/272-attest-verify.md`): sign an in-toto statement about a holo into its attestation section, keyless with the GitHub Actions OIDC token or with `--key`, and check the bundles against a signer policy (exact `--certificate-identity` or `--certificate-identity-regexp`, and `--certificate-oidc-issuer`, or `--key`) with typed errors; `experimental_attest`, `experimental_verifyAttestations` and `experimental_verifyBundle` in `prism-code/node`. Uses the optional `sigstore` packages. `verifyTransparency` now also reads Rekor v1 `dsse` 0.0.1 and Rekor v2 `dsse` 0.0.2 entries, because the public instance still logs attestations to Rekor v1. The Rust half follows #267's wire change.
Expand Down
4 changes: 4 additions & 0 deletions CONFORMANCE.md
Original file line number Diff line number Diff line change
Expand Up @@ -148,6 +148,10 @@ The three honesty levels:
| `HO-28` | `build` | verify-attestation checks every attestation of the requested type in the oracle's order: subjects against the holo's blobs, the DSSE signature under the signing certificate or the given key with the chain and its signed certificate timestamps at a signed time, the exact certificate identity and OIDC issuer, and the transparency evidence with Rekor v1 dsse 0.0.1, Rekor v2 dsse 0.0.2 and hashedrekord 0.0.2 bodies checked against the envelope, offline against a pinned trusted root; the bundles the JavaScript signer writes verify, and the Sigstore conformance bundles pass and fail as they do there. |
| `HO-29` | `build` | attest signs an in-toto Statement v1 about the holo's content blobs with a local P-256 or Ed25519 key into the attestation section as a Sigstore bundle v0.3 in the shape the JavaScript signer writes, leaves the input holo untouched, strips back to it byte for byte, and verifies offline with the public key. |
| `HO-30` | `build` | Every refusal of attest and verify-attestation is a registered diagnostic with its check: PP3101 signing, PP3102 signature, PP3103 identity, PP3104 transparency, PP3105 subject, PP3106 no attestation, PP3107 trusted root, and PP1001 for a policy that would let any signer pass. |
| `HO-32` | `build` | A build stamped with provenance carries exactly one unsigned SLSA provenance v1 statement in the attestation section with no flag, keeps every other row byte for byte, records the identities of the stamped archive, writes in min mode the same bytes as the JavaScript reference on every run, and stays at P0. |
| `HO-33` | `build` | The provenance statement's subjects, build type, external parameters, builder and dependencies equal the lock and the archive, and PP3018 refuses a lock that does not describe the build and an archive that already has a statement. |
| `HO-34` | `build` | --provenance=max adds exactly the arguments, platform, invocation id and whole-second timestamps, and min records none of them. |
| `HO-35` | `build` | --no-provenance writes no statement and needs no lock, and an application build that asked for provenance with nothing to derive it from is refused with PP3018 before compiling. |

## lifecycle

Expand Down
Loading
Loading