The oracle had two import names, `tools.oracle` for the tools and
`paperspec` for other repositories, which could load the same code twice
in one process and needed a gate keyed on the module name. It now lives
in the standard src layout under its one name.
- git mv tools/oracle -> src/paperspec; the 22 rule modules are unchanged.
- The tools import `paperspec`. `tools/__init__.py` now holds the Python
3.14 and cryptography/jsonschema check and puts src/ first on sys.path,
so the tools run this checkout's code with or without pixi. The
package's own __init__ checks nothing and exposes __version__.
- pyproject.toml: version from git tags via setuptools-scm
(guess-next-dev, node-and-timestamp, src/paperspec/_version.py,
gitignored). The packages stay listed rather than found because
schemas/, sql/ and vectors/ stay at the root: the spec links to them and
the site serves the schemas at their $id URLs.
- pixi.toml: a `dev` feature and environment with setuptools,
setuptools-scm and python-build, and `pixi run -e dev wheel`.
- check.py scans src/paperspec for rule IDs; README, CONTRIBUTING, the
FAQ, the overview, the vectors and tools READMEs and the changelog point
at the new path. The FAQ no longer says the oracle is not a library.
pixi.lock is not re-solved in this commit: with a dynamic version, pixi
builds the package metadata to lock, which needs the conda environment
installed. Run `pixi lock` and commit the result before pushing; the site
workflow installs with --locked.
pixi run check passes; no computed value, vector, fixture, schema or SQL
file changed.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
- hashing.algorithm names the hash function in every document; a consumer refuses one it does not implement (doc.hash.algorithm)
- ML-DSA-65 (FIPS 204) is an implemented signature scheme: pure-Python reference in tools/oracle/mldsa.py checked against NIST ACVP vectors, a receipt signed by the new roster key dana, and signature vectors for key generation and a deterministic signature
- roster keys may carry a did:key, which the validator checks against the public key (doc.roster.did), and a witness purpose for parties that cosign log checkpoints
- model provenance: a correction's author and an annotation's generator name the model with provider, version and the hashes of its weights, prompt and parameters, and where it ran
- the transparency log gains the tlog-tiles static layout (fixtures/records/log/), a project settings.log with origin, witnesses and threshold, and an acceptance rule; the fixture checkpoint is cosigned by a witness
- store.sql: roster_keys accepts cose and ml-dsa-65 and gains a did column
- spec chapters 01, 08, 11, 18, 20 and 23, the rationale, glossary, fixture, vector and tool guides updated; stress harness covers ML-DSA
Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
alexm
