Skip to content
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
20 commits
Select commit Hold shift + click to select a range
bc9760e
feat(prism-code): check the developer surface against the developer v…
claude Nov 11, 2026
509b2bf
fix(xtask): keep the rendered developer glossary LF on every checkout…
claude Nov 12, 2026
8024046
fix(docs): exclude the developer glossary from the site vocabulary li…
claude Nov 12, 2026
f9812ff
ci(prism-code): sum the package cap from one allowance file per change
claude Nov 12, 2026
ab9ab61
feat(prism-code): system and auth command groups (Part of #446)
claude Nov 12, 2026
5090860
Merge remote-tracking branch 'origin/claude/project-thread-jbxsn0' in…
claude Nov 12, 2026
48f04fc
fix(prism-code): system events follows without racing the clock (Part…
claude Nov 12, 2026
2813675
Merge remote-tracking branch 'origin/main' into claude/roadmap-347
claude Nov 12, 2026
541ac95
fix(model): own src/cli as client in the modules table (Part of #446)
claude Nov 12, 2026
3450fa0
Merge remote-tracking branch 'origin/main' into claude/project-thread…
claude Nov 12, 2026
89e9e9d
feat(prism-code): CLI groups named after the modules (Part of #441)
claude Nov 12, 2026
206a79f
Merge remote-tracking branch 'origin/main' into wip-cli-groups
claude Nov 12, 2026
709c1d8
feat(prism-code): wire the system and auth groups into the dispatcher…
claude Nov 12, 2026
edac86b
docs(prism-code): list the images and containers groups in cli.json, …
claude Nov 12, 2026
6275fed
Merge remote-tracking branch 'origin/claude/project-thread-jbxsn0' in…
claude Nov 12, 2026
a3fd680
docs(prism-code): list the system and auth groups in cli.json and the…
claude Nov 12, 2026
47e3cec
fix(prism-code): system events reads the store afresh on every poll (…
claude Nov 12, 2026
19f0f28
Merge remote-tracking branch 'origin/main' into claude/project-thread…
claude Nov 12, 2026
5716676
Merge remote-tracking branch 'origin/main' into claude/project-thread…
claude Nov 12, 2026
13f68a5
Merge remote-tracking branch 'origin/main' into claude/project-thread…
claude Nov 12, 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
1 change: 1 addition & 0 deletions CONFORMANCE.md
Original file line number Diff line number Diff line change
Expand Up @@ -264,6 +264,7 @@ The three honesty levels:
| `DK-40` | `build` | The prism.volumes namespace of prism-code is a view over the capability file with create, list, inspect and remove: a host-folder mount, a name or provider outside the grant, and a store outside the image's declared world or the active policy are refused with CapabilityDeniedError before any provider runs, attaching a store to a guest raises a typed error naming host effects #216 and #217, and the module never reads or writes a system model and imports only errors and the capability code. |
| `DK-41` | `build` | The prism.system namespace of prism-code reports info, version, df, prune and events over the containers of its own client: info and version name the package, the holo format revision, the runtime and the toolchain and builder image a project's prismpm.lock pins, prune removes exited containers only and no image, events streams the create, start, die and destroy events of the client's containers with since, until and filters, and createPrism and Prism.fromEnv expose the eight other modules of #440 on one client. |
| `DK-42` | `build` | The Rust runtime runs @prism-code/conformance through its shim, prism-conformance-shim, which translates prism/conformance-shim/1 requests to the prismpm library's inspect and verify and judges nothing: every check of the suite runs, the digests checks pass in full, and each check the Rust runtime does not pass is named with its reason in crates/conformance/runtime/declaration.json, so a check that starts to pass or newly fails fails the run. |
| `DK-44` | `build` | The prism-code system and auth command groups are the CLI of prism.system and prism.auth: system info and version name the package, the holo format, the runtime and the toolchain and builder image the project's prismpm.lock pins, events replays and follows create, start, die and destroy from the container store with since, until and filters, df counts every record and prune removes exited containers only and asks first unless forced; auth login checks the credential with the registry before storing it where Docker would, refuses a password on the command line, and no password reaches stdout, stderr or an error in any spelling, and logout names an ambient token it cannot clear. |

## security

Expand Down
1 change: 1 addition & 0 deletions SPEC.md
Original file line number Diff line number Diff line change
Expand Up @@ -4491,6 +4491,7 @@ Every row below is normative, has the honesty level registered in `model/ids.tom
| `DK-40` | `sdk` | The prism.volumes namespace of prism-code is a view over the capability file with create, list, inspect and remove: a host-folder mount, a name or provider outside the grant, and a store outside the image's declared world or the active policy are refused with CapabilityDeniedError before any provider runs, attaching a store to a guest raises a typed error naming host effects #216 and #217, and the module never reads or writes a system model and imports only errors and the capability code. | §12 |
| `DK-41` | `sdk` | The prism.system namespace of prism-code reports info, version, df, prune and events over the containers of its own client: info and version name the package, the holo format revision, the runtime and the toolchain and builder image a project's prismpm.lock pins, prune removes exited containers only and no image, events streams the create, start, die and destroy events of the client's containers with since, until and filters, and createPrism and Prism.fromEnv expose the eight other modules of #440 on one client. | §12 |
| `DK-42` | `sdk` | The Rust runtime runs @prism-code/conformance through its shim, prism-conformance-shim, which translates prism/conformance-shim/1 requests to the prismpm library's inspect and verify and judges nothing: every check of the suite runs, the digests checks pass in full, and each check the Rust runtime does not pass is named with its reason in crates/conformance/runtime/declaration.json, so a check that starts to pass or newly fails fails the run. | §12 |
| `DK-44` | `sdk` | The prism-code system and auth command groups are the CLI of prism.system and prism.auth: system info and version name the package, the holo format, the runtime and the toolchain and builder image the project's prismpm.lock pins, events replays and follows create, start, die and destroy from the container store with since, until and filters, df counts every record and prune removes exited containers only and asks first unless forced; auth login checks the credential with the registry before storing it where Docker would, refuses a password on the command line, and no password reaches stdout, stderr or an error in any spelling, and logout names an ambient token it cannot clear. | §12 |
| `OC-01` | `oci` | Product releases use OCI 1.1 descriptors, manifests, indexes, subjects, annotations, and referrers with registered media types. | §13 |
| `OC-02` | `oci` | A locked build atomically emits a verified root only after every declared source, proof, package, oracle, and release gate passes. | §13 |
| `OC-03` | `oci` | The release graph closes over all artifacts and binds SBOM, provenance, validation, signature, policy, and deployment referrers to exact subjects. | §13 |
Expand Down
1 change: 1 addition & 0 deletions STABILITY.md
Original file line number Diff line number Diff line change
Expand Up @@ -186,6 +186,7 @@ Removed: `prism-code check [args]` with no holo, which ran `prismpm check` in th
| `prism-code` | `manifestProviders`, `ProviderError`, `ProviderNotFoundError`, `ProviderReplyError`, `ProviderFailedError` and their `code`s and `provider.*` checks, the `provider-not-granted` lint warning, the `providers` capability kind and the check `capabilities.providers`; `resolveProviders`, `releaseProviders`, `PROVIDER_MESSAGES`, `PROVIDER_MESSAGES_ENV`, `PROVIDER_TIMEOUT_MS` in `prism-code/node` | [#294](https://github.com/UOR-Foundation/PrismPM/issues/294) |
| `prism-code` | `src/volumes.mjs`: `createVolumes`, its `create`, `list`, `inspect` and `remove`, `attachVolume`, `refusalRecord`, `HOST_EFFECTS`, and the `capabilities.host-folder` and `capabilities.host-effects` checks of `CapabilityDeniedError`. Reached as `prism.volumes` on the client (#441) | [#445](https://github.com/UOR-Foundation/PrismPM/issues/445) |
| `prism-code` | `prism.system` in `src/system.mjs`: `createSystem`, `createEventBus`, `info`, `version`, `df`, `prune` and `events`, their options, the `prism/system-info/1`, `prism/system-version/1`, `prism/system-df/1`, `prism/system-prune/1` and `prism/system-event/1` shapes, `EVENT_ACTIONS`, `EVENT_HISTORY` and `IMAGE_STORE`; `containers.list` and `containers.prune`, and the `onEvent` option of `createContainers` | [#446](https://github.com/UOR-Foundation/PrismPM/issues/446) |
| `prism-code` | The `prism-code system info\|version\|events\|df\|prune` and `prism-code auth login\|logout` groups (`src/cli/system.mjs`, `src/cli/auth.mjs`), the top-level `login` and `logout`, their options and `--json` output, and the rule that `login` takes no password on the command line | [#446](https://github.com/UOR-Foundation/PrismPM/issues/446), [#447](https://github.com/UOR-Foundation/PrismPM/issues/447) |
| `prism-code` | The client: `createPrism` exposing `images`, `containers`, `networks`, `volumes`, `system`, `auth`, `errors` and `verify`, its options, `MODULES` and `memoryCapabilityStore`; `Prism.fromEnv()` and `Prism.create` in `prism-code/node`; the `client.option`, `auth.unavailable` and `images.unavailable` codes | [#441](https://github.com/UOR-Foundation/PrismPM/issues/441) |
| `prism-code` | The CLI groups `prism-code <module> <verb>` in `src/cli/`: `images build`, `inspect`, `pull`, `push`, `verify` and `containers run`, `rm`, `inspect`, each the same as the flat verb it names, and `GROUPS`, `TOP_LEVEL` and `groupVerb` in `src/cli/index.mjs` | [#441](https://github.com/UOR-Foundation/PrismPM/issues/441) |
| `prism-code` | `prism.errors` in `src/errors-namespace.mjs`: the error classes and functions of the package exports, `errors.codes` (the stable code of each class, by class name) and `errors.spec`; every code prism-code raises, each listed with its owning capability in model/sdk-diagnostics.toml and ERRORS.md. Reached as `prism.errors` on the client (#441) | [#448](https://github.com/UOR-Foundation/PrismPM/issues/448) |
Expand Down
7 changes: 7 additions & 0 deletions crates/conformance/src/cases/mod.rs
Original file line number Diff line number Diff line change
Expand Up @@ -741,6 +741,13 @@ pub fn run_at(root: &Path, id: &str) {
&[("sdk/npm/prism-code/test/system.test.mjs", 20)],
"600000",
),
// The `prism-code system` and `auth` command groups of #446 and #447.
"DK-44" => node_suite::verify_exact(
root,
id,
&[("sdk/npm/prism-code/test/system-auth-cli.test.mjs", 16)],
"600000",
),
"DK-35" => verify_node_suite(
root,
id,
Expand Down
1 change: 1 addition & 0 deletions crates/conformance/tests/conformance.rs
Original file line number Diff line number Diff line change
Expand Up @@ -225,6 +225,7 @@ test_case!(conformance_dk_35, "DK-35");
test_case!(conformance_dk_39, "DK-39");
test_case!(conformance_dk_40, "DK-40");
test_case!(conformance_dk_41, "DK-41");
test_case!(conformance_dk_44, "DK-44");
test_case!(conformance_dk_42, "DK-42");
test_case!(conformance_oc_01, "OC-01");
test_case!(conformance_oc_02, "OC-02");
Expand Down
7 changes: 7 additions & 0 deletions features/suites/sdk.feature
Original file line number Diff line number Diff line change
Expand Up @@ -271,3 +271,10 @@ Feature: sdk
When the suite runs every check against the shim
Then the run passes with every gap declared, and the digests checks pass in full
And the checks that pass are exactly the ones DK-42 lists, by feature

@DK-44 @build
Scenario: The prism-code system and auth command groups are the CLI of prism.system and prism.auth: system info and version name the package, the holo format, the runtime and the toolchain and builder image the project's prismpm.lock pins, events replays and follows create, start, die and destroy from the container store with since, until and filters, df counts every record and prune removes exited containers only and asks first unless forced; auth login checks the credential with the registry before storing it where Docker would, refuses a password on the command line, and no password reaches stdout, stderr or an error in any spelling, and logout names an ambient token it cannot clear.
Given a PRISM_HOME with containers, a project with a prismpm.lock, a Docker config folder and an in-process registry
When the system and auth verbs are called as the CLI dispatcher calls them, with good and bad arguments
Then system reports, replays and follows events, counts and prunes as prism.system does, and every bad argument is a usage error
And login stores only a credential the registry accepts, a password on the command line is refused, and no secret appears in any output or error
6 changes: 6 additions & 0 deletions model/ids.toml
Original file line number Diff line number Diff line change
Expand Up @@ -1230,6 +1230,12 @@ suite = "sdk"
level = "build"
statement = "The Rust runtime runs @prism-code/conformance through its shim, prism-conformance-shim, which translates prism/conformance-shim/1 requests to the prismpm library's inspect and verify and judges nothing: every check of the suite runs, the digests checks pass in full, and each check the Rust runtime does not pass is named with its reason in crates/conformance/runtime/declaration.json, so a check that starts to pass or newly fails fails the run."

[[id]]
id = "DK-44"
suite = "sdk"
level = "build"
statement = "The prism-code system and auth command groups are the CLI of prism.system and prism.auth: system info and version name the package, the holo format, the runtime and the toolchain and builder image the project's prismpm.lock pins, events replays and follows create, start, die and destroy from the container store with since, until and filters, df counts every record and prune removes exited containers only and asks first unless forced; auth login checks the credential with the registry before storing it where Docker would, refuses a password on the command line, and no password reaches stdout, stderr or an error in any spelling, and logout names an ambient token it cannot clear."

[[id]]
id = "OC-01"
suite = "oci"
Expand Down
6 changes: 5 additions & 1 deletion sdk/docs/cli.json
Original file line number Diff line number Diff line change
Expand Up @@ -58,7 +58,11 @@
{ "name": "build", "usage": "prism-code build [--check] [--hosted] [--local] [--remote github] [--repo <owner/name>] [--ref <commit>] [--timeout <s>] [--allow-dirty] [--json]", "summary": "Build the project into a holo inside the SDK image the lockfile pins. With `--remote github`, the repository's own GitHub Actions builds one commit instead, pushed to `prism/build/<sha>` so the run is that commit and no other, and this machine verifies what comes back before anything lands under `.prism/build/`: the commit and repository named in the artifact, the holo's SHA-256, the signed provenance (its subject, its repository and commit, and its signature by a workflow of the repository through GitHub's issuer), then `check` at the P0 policy unless `--policy` names one, the recorded fingerprint, and every acceptance vector replayed here. Needs the template's `build.yml` in the repository, a token (`GITHUB_TOKEN`, `GH_TOKEN` or `gh`), and the Sigstore packages or `gh` for the signature. No Docker. With `--check`, validate the model and write nothing: the full check in the image when it is on this machine, or with `--local`; otherwise `prism.toml` here and `lexlean check` of the files under `src/` on the hosted verifier, which skips the lockfile and SDK pins and says so. The hosted check sends the files under `src/`, unlisted but not private." },
{ "name": "verify", "usage": "prism-code verify [--lean] [--hosted] [--local] [--all]", "summary": "Run verify in the SDK image the lockfile pins. With `--lean`, run `lexlean verify` on the project's LexLean project instead: every theorem through Lean and leanchecker with its exact axiom policy, about a minute. It runs in the image when the image is on this machine, or with `--local`; otherwise on the hosted verifier at `https://mcp.uor.foundation/` (profile `prism-app`), which takes a project whose only source root is `src` and passes only when every entrypoint module comes back verified, and writes its record to `.lexlean/hosted/`. The hosted verify sends the files under `src/`, unlisted but not private." },
{ "name": "axioms", "usage": "prism-code axioms [--write] [--json]", "summary": "Compile the project once in the SDK image and print the axiom set Lean observes for every definition and theorem beside the set the source declares; exit 1 while any differs. With `--write`, set each `axioms` member to the observed set and format the project." },
{ "name": "conformance", "usage": "prism-code conformance", "summary": "Run the conformance suite in the SDK image the lockfile pins." }
{ "name": "conformance", "usage": "prism-code conformance", "summary": "Run the conformance suite in the SDK image the lockfile pins." },
{ "name": "system", "usage": "prism-code system <verb> [--project <dir>] [--since <time>] [--until <time>] [--filter <key=value>] [--verbose] [--force] [--json]", "summary": "Report on this installation and tidy it, with the verbs info, version, events, df and prune: `info` and `version` name the package, the holo format, the runtime and the toolchain and builder image the project's `prismpm.lock` pins; `events` prints container create, start, die and destroy events from the container store and follows it until `--until`; `df` says what the container records take; `prune` removes exited containers, asking first unless `--force`." },
{ "name": "auth", "usage": "prism-code auth <verb> [<registry>] [--username <name>] [--password-stdin] [--json]", "summary": "Log in to a registry or out of it, with the verbs login and logout. `login` checks the username and password with the registry, then stores them where Docker would, so `push`, `pull` and `docker` find them; the password comes from `--password-stdin` or a prompt that does not echo, never from the command line. `logout` removes the credential from every store that holds it." },
{ "name": "login", "usage": "prism-code login [<registry>] --username <name> [--password-stdin] [--json]", "summary": "The same as `prism-code auth login`." },
{ "name": "logout", "usage": "prism-code logout [<registry>] [--json]", "summary": "The same as `prism-code auth logout`." }
],
"providers": {
"$comment": "Provider services (#294, experimental). The wire protocol is on the manifest reference page.",
Expand Down
1 change: 1 addition & 0 deletions sdk/npm/prism-code/CHANGELOG.md
Original file line number Diff line number Diff line change
Expand Up @@ -35,6 +35,7 @@ To move to 1.0, read the [migration guide](../../../docs/site/migration/to-1-0.m
- Gap telemetry (experimental). The journey records, as a fingerprint in `$PRISM_HOME/gaps.jsonl`, what a user asked for that Prism or Lean could not do: an answer or spec a validation rule refused (each refusal now names its rule), a valid spec that does not come back from its own answers, a property Lean did not prove that no sampled request breaks, and a generated model the toolchain refused. A fingerprint holds the kind, a construct from a fixed vocabulary, the diagnostic code and the version, and nothing the user wrote. The next call to the hosted verifier carries the unsent fingerprints, counted, in its `_meta` under `foundation.uor/prism-gaps` (`prism/gaps/1`), with a random install ID. `PRISM_TELEMETRY=0` or `DO_NOT_TRACK=1` turns it off; `setup` prints one line saying so, and `--json` reports it as `telemetry`.
- `src/images-namespace.mjs`, the `prism.images` namespace (#442, experimental): `build`, `pull`, `push`, `inspect` and `verify`, reached as `prism.images` on the client (#441). See the root CHANGELOG.
- The nine modules on one client (#441, #446, experimental): `createPrism()` returns `images`, `containers`, `networks`, `volumes`, `system`, `auth`, `errors` and `verify`; `Prism.fromEnv()` in `prism-code/node` configures it from this machine. `prism.system` (`info`, `version`, `df`, `prune`, `events`), `containers.list` and `containers.prune` are new. See the root CHANGELOG.
- `prism-code system info|version|events|df|prune` and `prism-code auth login|logout` (#446, #447, experimental), with `login` and `logout` as top-level spellings. `info` and `version` name the toolchain and builder image the project's `prismpm.lock` pins; `events` reads create, start, die and destroy from the container store, since there is no daemon, and follows it until `--until`; `prune` asks first unless `--force`. `login` checks the credential with the registry (`GET /v2/`) before storing it where Docker would, and reads the password only from `--password-stdin` or a prompt that does not echo: `-p` and `--password` are refused, and nothing printed or thrown holds the secret. Every verb takes `--json`.

### Bugs Fixed
- A built holo says plainly that it does not carry its proof (#582). `prism_build` and its run note now say that the holo holds no signed proof statement, so the default `prism-code check` reports P0. The verdict's reasons for a holo with no attestation section no longer cite closed issues #266, #267 and #284, and now read as the Rust verifier's do: "The holo carries no provenance statement." and the same for proof and replay.
Expand Down
Loading
Loading