Repository navigation
Add a versioned installed proof-carrying exact-query API - #63
Closed
tugrapaydiner wants to merge 14 commits into
Closed
tugrapaydiner wants to merge 14 commits into
tugrapaydiner wants to merge 14 commits into
Conversation
This was referenced Oct 16, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Scope
Stack this release-engineering checkpoint on draft PR #62 without changing
faster-queries,main, the existing automatic engine policy, frozen benchmark evidence, packet formats, native ABI semantics, or research conclusions. No merge or package release is requested by this draft.The proof-carrying exact-query engine previously lived only in
experiments/compiled_query. This PR makes the same ABI-3 implementation available through a documented, versioned installed API while retaining the experiment sources and evidence.Public contract
spectra.exact, API version 1 and native ABI 3.ExactProblemconstruction and strict canonical SBC1/SBQ1 packet decoding.spectra/_native/exact_binary.cpp; the platform extension is built explicitly on first use rather than shipping an unverified prebuilt binary.spectra exact build,spectra exact verify, and updatedspectra doctorCLI paths.Verification completed
Final cross-platform run:
38797065291.Two earlier failed workflow runs remain visible. The first loaded the unrelated repository training fixture because the dependency-light public tests were not isolated. The second completed all Windows API checks but failed while deleting a loaded
.pyd; the final checker restores its working directory, preserves the requested receipt outside the temporary tree, and treats the Windows extension lock as process-lifetime cleanup.Boundaries
This is release and portability progress, not a new speed result or algorithmic novelty claim. Native execution requires a supported host C++ compiler at explicit build time. The wheel contains source rather than an opaque prebuilt extension. The prior exposed synthetic timings, negative cells and automatic-policy limitations are unchanged. There is still no operator-defined workload, outside-team replication, maintained adoption, or independent priority determination.
The full public-package workflow is enabled for this stacked review and should be judged separately from the dedicated exact API matrix.