Skip to content

External read-only audit: branch qualification, canonical JSON and equation integrity (2026-11-15) #555

Open

Description

@Knapp-Kevin

Scope

Independent, read-only audit of two distinct repository states on 2026-11-15:

Source, normative SPEC.md, AGENTS.md, VERIFICATION.md, outstanding issues, release listings and existing CI logs were inspected. No local compiler/build, security fuzzing, proof checker execution, or signed Qortara gate was performed.

Observations

High: default-branch quality signal is red and stale

Last recorded main CI workflow 40523844928 failed on 2026-10-27. Its just vv (rest) job fails conformance_rp_11 with RP-11: the README has the capability table; tests on supported host job lanes also fail. honesty and reproducibility passed separately. Therefore main does not have a whole-suite acceptance receipt at this SHA.

By contrast, active release/v0.5 workflow 43767971718 is reported successful, and its reproducibility run passed. The workflow plan can reuse exact-tree evidence; the green conclusion must not be projected onto a different branch/commit.

Request: make the default-branch acceptance state and the precise selected integration/release ref explicit to consumers; either bring main to a qualified state or document its non-release role and refuse using its CI badge as evidence for release-line artifacts.

High for correctness / already tracked: escaped-equivalent duplicate canonical JSON keys

Issue #475 describes source-confirmed collision of decoded JSON keys. PR #520 merged the fix to release/v0.4; the issue remains open for final acceptance/forward-history. Do not create a competing fix; preserve the decoded-key/nested collision and distinct-object regression tests across accepted release revisions.

Significant / already tracked: equation metadata node referential integrity

Issue #552 documents eqn_info node references and a recorded Lean certification failure; later triage narrowed the hypothesized formatter mechanism. Treat the exact cause as under investigation. Acceptance requires a minimal reproducer and a structural invariant that rejects references inconsistent with the actual declaration before proof/certification.

Positive architectural controls

  • check, build, and verify deliberately use different assurance levels, with kernel replay and observed axiom sets required for verified claims.
  • model/*.toml registration, named tests, negative fixtures, source reproducibility, and explicit external authority levels are implemented review surfaces.
  • Released v0.4.1 exists, but this audit does not establish independent tag-bound acceptance.

Requested completion criteria

  • Publish a source/release identity table naming which branch/tag consumers should pin and the matching complete accepted workflow evidence.
  • Close Reject escaped-equivalent duplicate JSON keys before parsing #475 only after qualified delivery at the supported refs and exact verified test/commit bindings.
  • Resolve or explicitly constrain lexlean fmt renumbers core nodes but not the bare node numbers of eqn_info #552 with a reproducible structural-integrity test, instead of claiming an unverified formatter root cause.
  • Reconcile the default-branch RP-11 gate with the README or clearly document and enforce the non-release status of this branch.
  • Maintain accurate verification boundaries: Lean-replayed theorem and axiom policy are not evidence about unmodeled external behavior.

Verdict

CONDITIONAL: suitable to evaluate for narrowly bounded formal specification verification; main is NO-GO as a release-accepted source at the audited SHA. release/v0.5 has stronger CI evidence but not independent reproduction here. Hosted Qortara Logic's read-only evaluator cannot independently execute a repository audit, and no signed Qortara approval is claimed.

Activity

  1. afflom commented on Nov 16, 2026

    @afflom
    Member

    Current source/evidence table, checked against live refs on 2026-11-16 at 22:36 UTC. Each row names its assurance scope; a branch badge does not qualify another commit.

    Ref Exact commit Evidence and remaining limits
    main a74b1f9 #556 externally merged at 04:09:13Z. Actual parents are 71defb4 + fa27108; tree 0af41e38 equals fa271 and the previously examined proposed merge. Existing exact-fa271 push CI43744252595 attempt1 passed72 jobs/838 steps and remains reusable technical evidence. Actual CI43802480909 is terminal with71 successful jobs and one ARM job failure: a new log shows shutdown during unfinished Cargo tests, without an established underlying cause. Actual repro43802480894 passed its job and all seven steps. Prior complete same-tree evidence is preserved separately. The audit's RP-11 finding remains historical evidence for old71def; it is not evidence that this new head fails. The #431/oldTC03 STOP conflict remains unresolved, so this is not blanket release acceptance.
    release/v0.5 361dc35 #539 externally merged at20:12:45Z, ordered parents d07bd64+1ebca4ce. Actual and final head share tree0079156b. Final dispatch43898718803 attempt1 passed all70 jobs/813 steps; exact checkout and actual tree equality verified. Actual repro43947436552 passed1 job/7 steps; actual CI43947436759 is planner-only (1PASS/17SKIP). Scoped technical landing review. Owner explicitly closed #127 with the merged-PR link, covering17 fixtures pinned to uor-addr0.2.0. Original-red R3 observation remains missing as disclosed; no waiver, reconstructed history or unqualified full acceptance is inferred. #128/#468 and actual #404 forward-history obligations remain open.
    release/v0.4 0c6eeb9 #560 externally merged17:36:02Z, ordered parents2e1ff2f5+e9075c21. Actual, reviewed e907 and checked synthetic98b187d6 share tree46604d6d. Final CI43897548879 attempt1 passed71 jobs/831 steps plus3 Intel job skips. Actual repro43920080311 passed; actual CI43920080624 attempt1 completed8 jobs/63 steps successfully with15 job skips, including Intel construction and four conformance lanes plus the x86_64-apple-darwin build. Scoped landing review. Fresh-run success does not establish the claimed all-jobs rerun recovery. Actual forward43920080440 again failed on index.lock, exit128; regeneration skipped. Prior2e1f77/878 full gate retains its original tree scope; #493 SM40/prose/R3/body obligations persist. No blanket release acceptance or STOP waiver.
    v0.4.3 tag fa27108 Annotated tag2a262c93 resolves here. Existing full technical gate and unchanged main tree are recorded above. GitHub release was externally published at00:45:25Z with15 listed assets. Asset metadata is not downloaded payload verification or a STOP waiver.

    #475's narrow v0.4/main closure now has an explicit merged-PR and qualification disposition. Its old canceled/failing gate was not counted as passing; later complete same-tree evidence was reused. The remaining v0.5 gap stays with #404's existing owner; no competing parser patch or repeated tests are started.

    #552 remains under its existing investigation owner. #443 retains the general formatter type-node equality guard; reference remapping/value correspondence and full pipeline regression remain open. Current #443 6ba and #559 023 repair only Kappa's compiler-semantics lock pin. Their existing oracle lanes and exact-head repros now pass, resolving that specific writer blocker within those runs. The workflow still runs golden before calculus and gives records only identity.patch, so fixture-before-consumer custody remains owed. #559's shared taken-arm lemma has bounded source credit; kernel/size/delivered-product qualification remains pending. This table does not close this audit, waive #431/oldTC03, qualify published payloads, or certify unmodeled external behavior. Published v0.4.1 remains a separate tag-bound acceptance question.

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

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions