Repository navigation
Description
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, andverifydeliberately use different assurance levels, with kernel replay and observed axiom sets required for verified claims.model/*.tomlregistration, named tests, negative fixtures, source reproducibility, and explicit external authority levels are implemented review surfaces.- Released
v0.4.1exists, 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-11gate 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
afflom commentedon Nov 16, 2026
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.
#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.