Query — exact-source research lookup

Look up exactly where a published Universal Law research artifact lives and verify that local bytes match its pinned source identity. The package is standard-library at runtime, read-only, and has no scientific-status authority: it reports commit/path/hash/scope metadata from the curated meta-framework catalog and does not determine theorem acceptance.

Citation · Help · Security · MIT license

Try it from source

You need Git and Python 3.11 or newer. This first check needs no catalog, installation, or private Drive access; after cloning, it runs offline.

git clone https://github.com/d6g8k5htny-coder/query-.git
cd query-
python -B -S research_query.py --help

For a real lookup, clone the public catalog as a sibling checkout:

git clone https://github.com/d6g8k5htny-coder/meta-framework.git ../meta-framework
python -B -S research_query.py --registry ../meta-framework/registry.json --key side24-coefficient

The catalog supplies the pinned source identities. Record the catalog commit along with the query commit when reproducing a lookup.

Installation is a separate capability

To install the command in your Python environment from this checkout:

python -m pip install --no-deps .
universal-law-query --registry ../meta-framework/registry.json --key side24-coefficient

The package has no runtime dependencies. Installation may download build tools; the setuptools build backend requires version 77.0.3 or newer for SPDX license metadata. Offline installation with --no-build-isolation requires those build tools to be installed already. These commands install local source, not a claimed PyPI release.

Installing from the checkout, and the installation control in tests/test_install_contract.py, leave setuptools' build/ and src/universal_law_query.egg-info/ in the checkout. Both are listed in .gitignore, so git status stays clean, and the source dry-run builder (which selects tracked files only) is unaffected. They are not harmless: setuptools reuses build/lib/ without removing anything, so a file left there (for example by an install from another commit) would otherwise be installed by the next install even though src/ does not contain it, and a stale SOURCES.txt in the egg-info directory would otherwise add package data; the installation control above cannot see either. The checkout's setup.py therefore refuses to build when build/lib/ holds anything this source tree did not produce (REFUSED: stale build output …, naming the files), before copying anything and again afterwards; every symlink under build/lib/ is refused wherever it points, because the wheel staging step would follow it, and so is a symlink among the package sources in src/, because the copy would ship its target. Bytecode under build/lib/ is accepted only from the run that compiles it (build_py --compile with bytecode writing enabled); a cache file found by a run that does not recompile it, such as --skip-build or a build under python -B, is refused. Every bdist command (bdist_wheel, bdist_egg, bdist_dumb, bdist_rpm) refuses a leftover in its own staging tree under build/bdist.*/, which it archives as found (an interrupted build leaves one). It does not refuse a tree that the same command kept earlier in the same run, as bdist does between two formats, because that tree is the command's own output; a spec-only bdist_rpm keeps nothing. For bdist_rpm, the spec, source archive and icon that every full run rewrites, and a successful run leaves behind, are not leftovers. A sibling command's tree is never read, and a named pipe or other special file in any tree is refused. The wheel and editable-wheel commands also refuse a pre-generated --dist-info-dir that differs in any name or byte from this build's own metadata, which a separate setup.py dist_info run regenerates for the comparison (REFUSED: pre-generated metadata …; a regular WHEEL, which both commands rewrite, is admitted), and the wheel command repeats the build/lib/ check, so --skip-build cannot bypass it; with --skip-build every expected output must be present with the bytes of its source. The legacy install, install_lib and bdist_egg commands run the same check on the directory install_lib copies from (--build-dir), with or without --skip-build; bytecode there is accepted only in build/lib/ right after the same run recompiled it. The egg-info manifest is regenerated from the tree and a stale SOURCES.txt is never read back, so it can add a file neither to a wheel nor to a setup.py sdist archive; any other file left in the egg-info directory is refused, because an sdist and a direct bdist_wheel would copy it into the archive, and so is a leftover sdist release tree (universal_law_query-0.1.0/), which an sdist would archive whole. A symlink among the files the manifest names (for example LICENSE or README.md, which the wheel's metadata copies or embeds) is refused whenever the metadata is generated, for a wheel, an sdist or an install alike. A symlink or hard link in or at the egg-info directory, or a symlinked build/, is refused before anything is written, because setuptools' metadata writers and build copies would otherwise write through to whatever the link points at; a directory named with a trailing / or /., or reached through .. after a symlinked directory, counts as the link. A hard link under build/lib/ is refused because its bytes are shared with another path, so the tree is not this build's output; the build copy itself unlinks its destination before writing and does not write through. A Windows junction counts as a symlink throughout. A --dry-run build (an option setuptools 81 removed) writes nothing and is not refused for that; leftovers are still refused. An editable install copies nothing and runs from src/; the editable-wheel command still refuses a symlinked build/, where a strict editable build keeps its link tree. The output directory (dist/ or --dist-dir) is taken as given, as are inputs an option names explicitly, such as bdist_rpm --icon. pyproject.toml also declares that the package ships no package data. Nothing is deleted for you; remove the leftovers before installing: git clean -fdX -- build src/universal_law_query.egg-info. tests/test_install_provenance.py installs temporary copies of the checkout, clean and deliberately contaminated, and checks that the installed files are exactly the tracked package files. A fresh checkout, as in CI, has neither directory. An untracked .py module placed directly in src/universal_law_query/ is source, not a leftover, and is installed like any other module; other untracked files there are not installed, because the package declares no package data, except the typing files setuptools always includes (py.typed, *.pyi). The build rewrites every file it produces and then compares each module's bytes with its source, so a file already sitting at a path this build writes (a module from another commit, or bytecode under --compile) is replaced, never shipped; setup.py bdist_wheel --skip-build compares instead of rebuilding and refuses differing bytes. A refusal in a custom --build-lib directory names that directory, since the git clean remedy reaches only the checkout's build/. Editable installs (pip install -e) run from src/ and are unaffected. The custom source archive below does not carry setup.py; it has no leftovers of its own, and installation from it is not one of its offline checks.

The canonical implementation lives in src/universal_law_query/. Historical root commands — research_query.py, catalog_entry_helper.py, and verify_portable_stubs.py — remain thin compatibility wrappers so existing python -B -S workflows continue to work.

The wrapper and package CLI are parity-tested for stdout, stderr, exit status, lookup, verification and refusal paths.

Pinned identities and non-theorem boundary

• Portable pin sets are in:
  • portable/CANDIDATE_DOWNSTREAM_GATE_STUBS.json
  • portable/CANDIDATE_PUBLIC_REPLAY_STUBS.json
  • portable/RN_FIXED_REMOTE_REPLAY_STUB.json
• verify_portable_stubs.py enforces exact byte identity (commit, path, bytes, sha256) for public artifacts.
• --check-math-tip reports TIP_DRIFT when current Math- default-tip bytes diverge from the pinned downstream-gate stubs. It compares bytes, not tip commit equality: documentation-only Math commits can leave this check green while the recorded math_tip needs an identity refresh.
• Scientific effect is NONE: this repository does not change theorem status, prize disposition, lemma_closed, or acceptance registers.

Topic → exact lookup key

Topic	Exact lookup key
SIDE24 coefficient	side24-coefficient
Quantitative lifetime density	lifetime-remainder
RN probability-to-count interface	rn-count-interface
RN fixed-remote height-window estimate	rn-fixed-remote-window
P15 original-coordinate family	p15-realized-covers
P15 unrestricted price counterexample	p15-price-boundary
P15 restricted transformed-price successor	p15-price-budget
P15 full probability range and sharp factor	p15-full-price

Unknown keys are refused rather than guessed. Exact-byte verification rejects path traversal, symlink payloads, mutable refs and private catalog artifacts.

Full-checkout engineering controls

python -B -S -m unittest -v test_research_query.py test_catalog_entry_helper.py test_verify_portable_stubs.py
python -B -S -m unittest discover -s tests -p 'test_*.py' -v
python -B -S verify_portable_stubs.py
python -B -S verify_portable_stubs.py --check-math-tip

These commands are for the full Git checkout. The older root tests remain as compatibility controls; package tests are the canonical implementation tests. Full discovery also runs the source-builder, dated peer-handoff and installation controls. It needs Git, the tracked checkout inputs, portable fixture JSON and already available pip/build tools; it is not the archive's stdlib-only subset. The real portable verification commands additionally need public network access.

For an offline run of the existing installation control, first verify that pip, setuptools>=77.0.3 and wheel are already available, then set PIP_NO_INDEX=1 and PIP_DISABLE_PIP_VERSION_CHECK=1 for the checkout test commands. The control uses --no-deps, --no-build-isolation and a temporary local target. Missing build tools are a missing capability, not permission to download them during an offline run.

Extracted package archive: offline help and unit subset

The custom source archive supports Python 3.11+ help and exactly five offline fixture-test modules (15 methods). Build it as shown under Source publication dry run, extract it outside the source checkout and run from that extracted directory; local symlink creation is needed by one refusal fixture. No catalog, installation or network is needed for these checks:

env -u PYTHONPATH -u PYTHONHOME -u PYTHONOPTIMIZE QUERY_STUB_VERIFY=1 python -B -S research_query.py --help
env -u PYTHONPATH -u PYTHONHOME -u PYTHONOPTIMIZE QUERY_STUB_VERIFY=1 python -B -S -m unittest discover -s tests -p 'test_*.py' -v

Repeat with -B -O -S for an optimized outer runner. The selected tests keep their own normal -B -S child commands; an optimized outer run is not an optimized-child claim. QUERY_STUB_VERIFY=1 makes the positive mocked-fetch fixture run; the suite separately tests the deliberate skip switch. Synthetic verified results and the skip message are not live portable coverage.

The explicit payload contains 11 public root files, the five package files and only these five test modules: test_catalog.py, test_catalog_entry.py, test_cli.py, test_stub_verify.py and test_wrapper_parity.py. Together they are 21 payloads, plus the generated SOURCE_MANIFEST.json and BUILD_INFO.json.

The archive intentionally excludes the source builder, its tests, dated peer-handoff tests/data, installation tests, root compatibility tests and portable candidates. Do not use archive-wide discovery as evidence that the full checkout suite passed. The checkout-side archive regression verifies exact members and hashes, extracted product origins, source-path isolation and required-member omissions, including the initializer's package-root contract.

Lookup with --registry needs a separately supplied public catalog; local byte verification also needs the catalog's corresponding workspace files. Record those inputs' identities separately. A portable-verifier wrapper without its candidate inputs does not establish coverage, even if it reports an empty verified list. Installation and installed-console verification remain separate from these offline source checks.

To verify local bytes, pass a catalog and a workspace directory:

python -B -S research_query.py --registry <catalog.json> --verify --workspace <workspace-dir>

The workspace must hold every artifact the catalog lists at <workspace-dir>/<repository>/<path> (for example Math-/coefficients/side24_v1/PROOF.md), with exactly the catalog's bytes and sha256. Verification covers the whole supplied catalog and refuses with exit status 2 at the first missing, symlinked or mismatched file; --verify without --workspace also refuses with exit status 2. The public meta-framework/registry.json pins artifacts at many different commits, so one current checkout per repository is not guaranteed to satisfy it. A verified list means exact bytes only, not currentness or theorem acceptance.

Candidate public catalog stubs

catalog_entry_helper.py remains a compatibility wrapper for universal_law_query.catalog_entry. It refuses sandbox repositories, symlinks, unsafe paths and mutable commits. A printed stub is not catalog integration or theorem acceptance.

Portable candidates remain under portable/; the verifier checks exact public bytes at declared commits. Private sandbox material is never fetched or published.

Source publication dry run

scripts/build_source_release.py is a checkout-only API: it needs a clean Git HEAD/index and tracked selected inputs, and its output must be outside the checkout. It builds the package archive described above with normalized metadata and embedded SOURCE_MANIFEST.json / BUILD_INFO.json, preserving tracked-only selection and public-file/symlink guards.

In both modes the builder reads the repository at the checkout it is given. Its Git commands run without the inherited variables that select another repository, work tree, index or object store (GIT_DIR, GIT_WORK_TREE, GIT_INDEX_FILE and the others listed in the script), so such a variable cannot put another repository's commit into the manifest. The recorded commit is the commit that HEAD resolves to: a HEAD that names an annotated tag records the tagged commit, and a HEAD that leads to no commit is refused. An existing output file that has another hard link is refused as well, because writing through it would overwrite the file behind the other name, and that can be a file inside the checkout.

For the complete package archive, call build_source_archive(repo, output, epoch, strict_members=True). Strict mode compares the selected names with the curated lists and refuses before anything is written when a required member is missing, or when a selected path is not a listed name (for example a directory standing where a listed file should be). LICENSE alone is optional: without it the archive holds 20 payloads and release_eligible is false. Strict mode also requires HEAD's own tree to hold the same members as regular files, and every selected file to hold exactly that blob's bytes, read with replacement refs ignored. Index hints, checkout normalization, a replaced commit or a symlink entry checked out as a plain file therefore cannot place other content under the recorded commit. The default call makes none of these checks; it stays permissive so that partial fixtures keep working, and it will write a smaller archive without an error.

To build and extract the complete archive from a clean checkout:

python -B -S -c "import sys; from pathlib import Path; sys.path.insert(0, 'scripts'); from build_source_release import build_source_archive; print(build_source_archive(Path('.'), Path('../query-archive/source.tar.gz'), 1700000000, strict_members=True))"
rm -rf ../query-archive/extracted
mkdir -p ../query-archive/extracted
tar -xzf ../query-archive/source.tar.gz -C ../query-archive/extracted
cd ../query-archive/extracted

Then run the extracted-archive commands above from that directory. The extraction directory is recreated empty so stale files from an earlier run can't mask archive omissions. The builder refuses a dirty working tree and an output path inside the checkout; untracked __pycache__/ directories count as dirty, so run earlier checkout commands with -B. The epoch argument (1700000000 here) sets the archive timestamps and is recorded in BUILD_INFO.json; record it with the commit when comparing archive hashes.

The repository uses the MIT license in LICENSE. The current release_eligible field means that LICENSE is present in the selected payload after the builder's guards; it does not mean extracted tests passed or authorize a release. A successful dry run is neither publication nor theorem acceptance. Standard setuptools source distributions are a separate producer: this custom allowlist does not define their membership or establish an offline-install or installed-console result.

The archived trial repository retains historical cross-repository engineering tests. For current coordination and integration, follow main's agent entry and current workflow. The curated public artifact routing authority remains meta-framework/registry.json.