Skip to content

[0.5.0] κ-addressing in LexLean, validated against uor-addr #127

Closed

Description

@afflom

Plan item L5.2 of #106 (C9).

Item. uor-addr's canonical forms (at least the ONNX realization and the formats LexLean artifacts use) and κ-label composition, written in LexLean, in the location #110 decides.

Oracles. uor-addr's Rust crate, its stdlib-only Python reference encoders (tools/canonical-*.py), its committed fixtures and κ-labels. A disagreement fails closed and is filed as a defect in one of the two.

Accepted when. Every committed uor-addr fixture yields the same κ-label from the LexLean implementation.

Depends on. #110. Blocks. MNIST UOR-Foundation/mnist#8.


Generated by Claude Code

Activity

  1. added this to the LexLean v0.5 milestone on Oct 16, 2026
  2. added 3 commits that reference this issue on Nov 1, 2026
  3. afflom commented on Nov 12, 2026

    @afflom
    MemberAuthor

    Bounded next-slice coordination: #110's location decision is settled, and the delivered KA-01–06 hash/label/composition work in the existing kappa package will be reused. The current five GGUF/ONNX label-form checks do not canonicalize the binary fixtures.

    Root is reserving SOURCE/R3 PREPARATION ONLY for the smallest GGUF slice: real input bytes → canonical GGUF v3 skeleton → sha256 label, using the three committed GGUF fixtures whose input/label blobs are identical at uor-addr v0.2.0 and current20a1c57. The next locally free KA-07 row is a proposal until the exact register/scenario/test design is reviewed. No parser implementation, source adoption, model writer, build or runtime is admitted by this reservation; an actual named failing test must precede implementation.

    The preparation must resolve the oracle boundary explicitly: LexLean currently links uor-addr0.2.0 with std only; enabling its GGUF oracle adds a dependency feature graph that needs source/license review. It must not silently enable ONNX/default features or change the oracle pin. Existing SHA256 and label machinery must be reused, with no fixture-specific lookup or stub.

    ONNX and full #127 acceptance remain open, including the current upstream six-pair corpus versus the older five label strings; this does not unblock MNIST by itself. Existing contributor history and the #405 forward lane remain intact. Independent scope receipt22cae1c2 records the exact inventory and limits. Please flag any concurrent GGUF implementation reservation before source preparation advances.

  4. afflom commented on Nov 12, 2026

    @afflom
    MemberAuthor

    Reserved #127 GGUF preparation is now composed and independently reviewed as source-only tree3000bfb895d26e5d2c27726fd230e3cc36d1bf02 over actual release/v0.5 2b039. All28 approved inputs are reused exactly; only25 paths differ because three committed labels already match. No parser, generated-model adoption, commit or PR publication has occurred. Independent review99475a83 records the complete composition boundary.

    Completed prerequisites will not be repeated: the three authentic GGUF fixtures and pinned0.2.0 script; one six-call reference capture independently reviewed8b731d47; the20-file static package reviewed4dd1247e; and one official offline Cargo lock update reviewedf0c04734. All130 package versions/sources/checksums are unchanged; dependency entries225→226 solely add uor-addr0.2.0→uor-prism-tensor. Exact produced lock SHA256d6a0ac9f4a15534089a3590bad68d6e94e9922beb8ed02f9ebf7d8c7b88c01b6 is retained externally. No compilation or reference replay was needed.

    The existing frozen official e722 model writer is reusable for the projection algorithm, avoiding a rebuild solely for that task. Its compiled repository root is the preserved #316 checkout, however; changing cwd cannot retarget it. No overlay or writer is admitted there. SPEC/model IDs/CONFORMANCE projections, source/build applicability, capacity and the genuine named failing test remain the next execution boundary. A source-only candidate is not R3 acceptance, and the parser will not be implemented before that failure. Current free-space observations do not establish later build capacity.

    Existing KA01–06 evidence, #316's source/frozen positive and negative evidence, and the #405 owner lane remain untouched. ONNX, native realization/proof checks, distinct implementation plants, products and full #127/MNIST acceptance remain open.

  5. afflom commented on Nov 14, 2026

    @afflom
    MemberAuthor

    What remains, at pinned uor-addr 0.2.0: 12 JSON fixtures (done, KA-02), 3 GGUF and 2 ONNX. #539 (KA-07) covers the GGUF part: kappa/src/Gguf.lex.tex is checked against uor_addr::gguf on all 3 fixtures, inputs at every bound the crate checks and a seeded corpus, under the evaluator and rustc, and 8 deliberately broken copies are each caught. It moves no identity. ONNX (KA-08: protobuf walk, Kahn order, nested subgraphs, recursive proto digest) is the last part, so #127 stays open.


    Generated by Claude Code

  6. afflom commented on Nov 16, 2026

    @afflom
    MemberAuthor

    Accepted through #539, merged into release/v0.5 as 361dc35. At the uor-addr 0.2.0 pin, all 17 committed fixtures (12 JSON, 3 GGUF, 2 ONNX) get the committed κ-label through KA-02, KA-07 and KA-08. The final-head gate is 43898718803, all green, and the merged tree equals the gated tree.


    Generated by Claude Code

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions