Skip to content
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension


Conversations
Failed to load comments.
Loading
Jump to
The table of contents is too big for display.
Diff view
Diff view
  •  
  •  
  •  
The diff you're trying to view is too large. We only load the first 3000 changed files.
1 change: 1 addition & 0 deletions CONFORMANCE.md
Original file line number Diff line number Diff line change
Expand Up @@ -636,6 +636,7 @@ the error registry does not sanction (R5, `ERRORS.md`).
| `SL-06` | `build` | The compiler computes its content identities with the standard library's certified `Sha256` package instead of the `sha2` crate: the shipped `lexlean` crate links the committed production export of `LexLeanStd.Sha256` through an in-crate link that resolves to that file and nothing else, its manifest has no `sha2` dependency, and `Sha256Digest::of`, `FramedHasher`, and `tree_digest` compute through the package; through the compiler's own API the digest of every example NIST states (the examples of FIPS 180-4 and the million-`a` message of FIPS 180-2) and every NIST CAVP SHA-256 short- and long-message vector, each cited by a `some-true` row of `model/authorities.toml` that vendors it or states its digest,, of every message length from 0 to 300 bytes and around each power of two up to 4 MiB, and of a seeded corpus agrees with the authority's digest and with the `sha2` crate as an oracle that can falsify and never establish, and the frames and tree rows agree with an independent recomputation of the §21.1 and §11.5 encodings, a disagreement failing closed and never resolved by adopting the oracle's digest; and a planted bit of the first round constant in a built copy of the package, a link that differs from the export by one byte, a `sha2` dependency added to the manifest, a message truncated by one byte, and a frame length written little-endian are each detected. |
| `SL-07` | `build` | Every content identity the compiler computes is byte-identical under the standard library's `Sha256` package to the identity it computed with the `sha2` crate: every tracked file of the repository digests identically under the compiler's `Sha256Digest::of` and under `sha2`; the compiler-semantics IDs of languages 1.0, 1.1, and 1.2 equal the values pinned in the committed example locks; the frame, tree, source, and semantic identities equal their independent recomputations (`AR-05`, `AR-06`, `SM-10`, `CF-07`, `CF-09`, `TX-10`); every example other than `uor-atlas`, the standard library, the compiler project, and the bootstrap project recompute their locks and pins on `check`; and a bit changed in a tracked file's digest, in a pinned compiler-semantics ID, or in the order of a source-ID recipe's frames is detected. |
| `SL-08` | `build` | The compiler running the standard library's `Sha256` package reproduces that package: the digest of every file that the `provenance.json` of every committed production export names equals the digest `sha2` gives its bytes; `lib.rs` of the two SHA-256 packages holds none of the digests their provenance records; and, under the pinned Lean, rebuilding the standard library with the compiler yields packages byte-identical to the committed ones and a `lib.rs` for `sha256` that is the file the compiler links, so that regenerating the export a second time changes nothing; a bit changed in a recorded digest, a digest written into `lib.rs`, and a link that is not the rebuilt `lib.rs` are each detected. |
| `SL-12` | `build` | The standard library's Host module declares the command request and event types as language-1.2 data; a consumer constructs all fourteen requests and eight events, and changing the spawn environment from a list of name/value pairs to text makes that consumer fail type checking. This claim establishes the interface only, with no host execution or effect authority. |

## tooling

Expand Down
4 changes: 2 additions & 2 deletions README.md
Original file line number Diff line number Diff line change
Expand Up @@ -121,7 +121,7 @@ Use it for safety critical code, audited or regulated artifacts, documents whose
| Language-1.2 compiler-tooling modules: a closed, typed program over a registry of the external Lean interface (types with exact constructors and index requirements, calls with exact signatures), with flat index-exhaustive matching, licensed partial and mutual recursion, complete recursive traversal, command registration, invocation and evaluation as semantic data, both backends from one linked value, and no member that holds Lean text | `TL-01`..`TL-11` | `build` |
| The language-1.2 authoring notation: a readable `.lex.tex` text for a semantic module, in bijection with its canonical JSON, whose every position and variant is read from the schema, with readable forms for types and terms and a generic form for every other value, formatted canonically by `fmt` failing closed, the only form in which a language-1.2 source of the product is written (the data form is refused under language 1.2, and `lexlean::sdk` is the explicit conversion), the same for the compiler-tooling modules in the generic notation, with no compiler-semantics ID that depends on which form an embedded module is written in, with no product source owned by a generator but five named records, read and written by programs only through the authoring API (`lexlean::sdk`), and, for a native core module, a readable program over the shared table of kernel terms whose numbering is the order of its text | `AU-01`..`AU-14` | `build` |
| The runtime of generated Lean as native modules: the portable, collection, model, and reasoning runtimes of language 1.2 are LexLean source that every generated module imports, migrated losslessly and audited against their exact axioms, the released runtime text of languages 1.0 and 1.1 is frozen data equal to their released output, and no other Lean runtime text remains in the compiler but the decoder of core module 2 | `RT-01`..`RT-04` | `build` |
| The standard library: language-1.2 source beside the compiler whose members are certified production roots, each validated against its oracle by a seeded differential of its evaluator and rustc realizations; bytes and text over `Bytes`, an output buffer of a given capacity written in order; SHA-256 against FIPS 180-4, the NIST CAVP vectors, and the `sha2` crate, and that SHA-256 as the compiler's own digest, linked from the committed export with no `sha2` in the shipped crate; and the `std-models` and `std-reasoning` source packages, generic over types, whose laws are kernel-checked theorems and whose application is the `helpdesk` example | `SL-01`..`SL-08` | `build` |
| The standard library: language-1.2 source beside the compiler whose members are certified production roots, each validated against its oracle by a seeded differential of its evaluator and rustc realizations; bytes and text over `Bytes`, an output buffer of a given capacity written in order; SHA-256 against FIPS 180-4, the NIST CAVP vectors, and the `sha2` crate, and that SHA-256 as the compiler's own digest, linked from the committed export with no `sha2` in the shipped crate; and the `std-models` and `std-reasoning` source packages, generic over types, whose laws are kernel-checked theorems and whose application is the `helpdesk` example; the `LexLeanStd.Host` source interface, checked by an independently authored consumer | `SL-01`, `SL-02`, `SL-03`, `SL-04`, `SL-05`, `SL-06`, `SL-07`, `SL-08`, `SL-12` | `build` |
| κ-addressing: the κ-label (sha256 axis) and the JSON canonical form of uor-addr written as the `kappa` source package beside the standard library, outside `language/` and `schemas/` so that no language identity moves, with the D3 data handle (a kind and the label of its canonical form) in its wire form; held to uor-addr as an oracle by its twelve committed JSON fixtures, the label form of its committed GGUF and ONNX labels, and a seeded differential of the evaluator and rustc realizations; the five hash axes of uor-addr (sha256, blake3, sha3-256, keccak256, sha512) and the five categorical compositions of uor-addr (G2, F4, E6, E7, E8) on each of them are also held to the oracle by a seeded differential; the GGUF and ONNX forms are outside the package | `KA-01`..`KA-06` | `build` |
| The bootstrap project: the compiler's own components as language-1.2 source compiled by LexLean's production pipeline to certified Rust packages, the exact axiom-output parser and its closed Lean-name check, the primitive scanner of §12.2, the preservation lexer and token audit, the target calculus's checker, the Rust crate validator, and the Rust printer, each held to the Rust it replaces (the stage-0 oracle) by the committed vectors and a seeded differential of its evaluator and rustc realizations, with planted defects detected and the production export committed | `BS-01`..`BS-09` | `build` |
| Source packages: a language-1.2 project imports the modules of a locked, content-addressed package of its workspace: `[[source_package]]` and `lexlean-workspace.toml`, the pins in `lexlean.lock` recomputed by every command, imports closed at link, no re-export of a package's production roots, and the package's modules replayed by the importer's `verify` with their origin in the records | `PK-01`..`PK-05` | `build` |
Expand All @@ -147,7 +147,7 @@ just vv
just release
```

All 482 registered conformance IDs are implemented and pass. `just vv` runs the complete normative acceptance gate (SPEC.md §9.2). `just release` runs `vv` and the §30 criterion; it is refused until 1.0.0.
All 483 registered conformance IDs are implemented. `just vv` runs the complete normative acceptance gate (SPEC.md §9.2). `just release` runs `vv` and the §30 criterion; it is refused until 1.0.0.

The [`lean4-prod`](https://github.com/UOR-Foundation/lean4-prod) differential is validation evidence only. A missing oracle fails on Linux x86 64 and prints `NOT VALIDATED` elsewhere. Releases live on `release/vX.Y`, and a tag before 1.0.0 does not claim the §30 criterion.

Expand Down
5 changes: 4 additions & 1 deletion SPEC.md
Original file line number Diff line number Diff line change
Expand Up @@ -7716,6 +7716,8 @@ a member whose outcome differs from its oracle on any input is not committed.
A member's declaration admits exactly the effects its runtime closure realizes
on its target, so the eligibility report of every member is its own text.

Host is a types-only module of the standard library. It declares FailureKind, Failure, EntryKind, Entry, Child, Waited, Start, Event and Request. Event.start carries a Start record with arguments excluding the executable name, fallible working-directory and executable-path results, environment name/value pairs and the stderr-terminal flag. Entry records carry an optional file identity. Request.wait carries child identifiers and a wait budget; Event.waited carries finished statuses and a clock value. Request paths and arguments are String; incoming host text and file contents are Bytes. The typed consumer constructs every request and event, and a changed spawn environment type is rejected (SL-12). These declarations are ordinary data: constructing a Request performs no effect and grants no authority to execute it.

The first module, `Text`, is bytes and text over `Bytes`. A `String` has no
scalar iteration in language 1.2, so text is handled as its UTF-8 bytes, a
character class is a comparison of `UInt8` by `equal`, and a member that is
Expand Down Expand Up @@ -11308,6 +11310,7 @@ Every row below is normative, has honesty level `build`, and is projected byte-f
| `SL-06` | `stdlib` | The compiler computes its content identities with the standard library's certified `Sha256` package instead of the `sha2` crate: the shipped `lexlean` crate links the committed production export of `LexLeanStd.Sha256` through an in-crate link that resolves to that file and nothing else, its manifest has no `sha2` dependency, and `Sha256Digest::of`, `FramedHasher`, and `tree_digest` compute through the package; through the compiler's own API the digest of every example NIST states (the examples of FIPS 180-4 and the million-`a` message of FIPS 180-2) and every NIST CAVP SHA-256 short- and long-message vector, each cited by a `some-true` row of `model/authorities.toml` that vendors it or states its digest,, of every message length from 0 to 300 bytes and around each power of two up to 4 MiB, and of a seeded corpus agrees with the authority's digest and with the `sha2` crate as an oracle that can falsify and never establish, and the frames and tree rows agree with an independent recomputation of the §21.1 and §11.5 encodings, a disagreement failing closed and never resolved by adopting the oracle's digest; and a planted bit of the first round constant in a built copy of the package, a link that differs from the export by one byte, a `sha2` dependency added to the manifest, a message truncated by one byte, and a frame length written little-endian are each detected. | §17.22 |
| `SL-07` | `stdlib` | Every content identity the compiler computes is byte-identical under the standard library's `Sha256` package to the identity it computed with the `sha2` crate: every tracked file of the repository digests identically under the compiler's `Sha256Digest::of` and under `sha2`; the compiler-semantics IDs of languages 1.0, 1.1, and 1.2 equal the values pinned in the committed example locks; the frame, tree, source, and semantic identities equal their independent recomputations (`AR-05`, `AR-06`, `SM-10`, `CF-07`, `CF-09`, `TX-10`); every example other than `uor-atlas`, the standard library, the compiler project, and the bootstrap project recompute their locks and pins on `check`; and a bit changed in a tracked file's digest, in a pinned compiler-semantics ID, or in the order of a source-ID recipe's frames is detected. | §21 |
| `SL-08` | `stdlib` | The compiler running the standard library's `Sha256` package reproduces that package: the digest of every file that the `provenance.json` of every committed production export names equals the digest `sha2` gives its bytes; `lib.rs` of the two SHA-256 packages holds none of the digests their provenance records; and, under the pinned Lean, rebuilding the standard library with the compiler yields packages byte-identical to the committed ones and a `lib.rs` for `sha256` that is the file the compiler links, so that regenerating the export a second time changes nothing; a bit changed in a recorded digest, a digest written into `lib.rs`, and a link that is not the rebuilt `lib.rs` are each detected. | §17.22 |
| `SL-12` | `stdlib` | The standard library's Host module declares the command request and event types as language-1.2 data; a consumer constructs all fourteen requests and eight events, and changing the spawn environment from a list of name/value pairs to text makes that consumer fail type checking. This claim establishes the interface only, with no host execution or effect authority. | §17.22 |
| `KA-01` | `kappa-addressing` | κ-addressing is the language-1.2 project `kappa` of the workspace, beside `stdlib` and outside `language/` and `schemas/`, under the module prefix `LexLeanKappa`, whose manifest declares the standard library as its one source package (`std`, the path `stdlib`) and no artifact or glossary, and whose modules `Label`, `Json`, `Word`, `Sha512`, `Keccak`, `Blake3`, `Axis`, and `Compose` verify under the pinned Lean with exact axiom policies; its roots `kappaLabel`, `isLabel`, and `handleWire` of `Label`, `canonicalJson` and `jsonLabel` of `Json`, `labelOn`, `isLabelOn`, and `jsonLabelOn` of `Axis`, and `composeG2On`, `composeF4On`, `composeE6On`, `composeE7On`, `composeE8On`, `composeG2`, `composeF4`, `composeE6`, `composeE7`, and `composeE8` of `Compose` are production roots eligible for `rust-std` with exactly their declared effects; and adding the package moves no compiler-semantics identity: the identities of languages 1.0, 1.1, and 1.2 equal the values pinned in the committed locks, and no file of `language/` or `schemas/` names the package. | §10.5, §17.22 |
| `KA-02` | `kappa-addressing` | The κ-label of the package is the one of uor-addr: `kappaLabel` of canonical bytes is `sha256:` followed by the sixty-four lowercase hexadecimal digits of their SHA-256, seventy-one bytes, and `isLabel` accepts exactly that form, which it accepts on every committed `.kappa-label` file of uor-addr; the data handle of decision D3 is a kind and that label, `handleWire` writing it as the kind, `@`, and the label for a kind of lowercase letters, digits, and hyphens and refusing every other kind; and for each of the twelve JSON fixtures of uor-addr's byte-identity test, the label `jsonLabel` gives from the raw input equals the committed address and the address `uor_addr::json::address` gives, a disagreement failing closed and never resolved by adopting the oracle's label. | §17.22, §21.7 |
| `KA-03` | `kappa-addressing` | The canonical JSON form of the package is that of uor-addr (RFC 8785 with Unicode NFC: members in the byte order of their NFC UTF-8 keys, no insignificant white space): `canonicalJson` is a production root whose lowered program under the calculus evaluator and whose rendered `rust-std` package under the pinned rustc give exactly the bytes of `uor_addr::json::canonicalize` on a seeded corpus of nested objects, arrays, strings with escapes and control characters and the Latin-1 letters in composed and decomposed form, integers, booleans, and null; it refuses, with no output, malformed JSON, a duplicate member name, a number that is not an integer (a fraction, an exponent, or minus zero), and a string outside the subset of Unicode whose NFC form it computes (ASCII, Latin-1, and the combining marks U+0300 to U+0303, U+0308, U+030A, and U+0327 after a letter that composes with them), and it never guesses an NFC form; and a planted member order, a planted escape, and a planted composition are each detected by the differential. | §17.22, §21.7 |
Expand Down Expand Up @@ -11344,7 +11347,7 @@ Every row below is normative, has honesty level `build`, and is projected byte-f
| `NS-06` | `normative-source` | The hand-edited normative inputs of the repository are the `.lex.tex` modules of the specification project: `model/` holds only the projected files and the copies an authority row vendors, every Markdown file at the root is a projection or is on the closed list of hand-written documents, the projections carry the notice that names their source, and no hand-written document restates a registered statement, a plant of each being refused naming R1. | §27.2, §27.5, §27.10 |
| `NS-07` | `normative-source` | `cargo xtask spec` changes the chapter modules of the specification project by item: it replaces a block, inserts one after a block, and ports the hunks of a merged SPEC.md that lie outside derived regions, each through the authoring SDK, and it writes nothing unless the regenerated SPEC.md equals the intended text outside derived regions, refusing a first line that matches no block or two and a hunk that spans two blocks. | §24.8, §27.5 |

**Total required capability IDs:** 482.
**Total required capability IDs:** 483.

No row may be downgraded to `some-true` or `open`. Upstream Lean facts are ledger/authority rows, not substitutions for these build behaviors.

Expand Down
Loading
Loading