Other repositories (paperstack, then paperpack) import the reference
implementation instead of reimplementing the specification; scienting-core
will take the role later behind the same vectors.
- pyproject.toml: distribution and import name `paperspec`, version 0.1.0,
Python >= 3.12, no base dependencies; `tools/oracle` is the package, and
`schemas/`, `sql/` and `vectors/` ship as the data subpackages
`paperspec.schemas`, `paperspec.sql` and `paperspec.vectors`. Extras
`schema`, `crypto` and `tools`.
- tools/oracle/__init__.py: the Python 3.14 and cryptography/jsonschema gate
runs only when imported as `tools.oracle` by the repository's own tools.
- crypto.py imports `cryptography` on first use of HKDF and Ed25519, with an
ImportError naming `paperspec[crypto]`; schema.py imports `jsonschema` and
`referencing` in `Store.validator` and `Store.registry`. package.py, db.py
and receipts.py then import on a bare interpreter.
- pixi.toml installs the package editable (pixi.lock re-solved; no conda pin
changed), so the tools and the package resolve to the same code.
- tools/README.md names the library surface and the extras; CHANGELOG.md
records the packaging change under 0.1.0, since check.py requires the
changelog's first heading to equal the format version.
No computed value, vector, fixture, schema or SQL file changed.
Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
- Rename manuspec to paperspec everywhere outside pixi.toml: prose, the
tools, provenance tool names and the fixture key derivations, so every
fixture and vector is rebuilt.
- Move the namespace addresses under the site, mirroring the repository:
schema $id https://paperspec.scient.ing/schemas/<file>, the JSON-LD
context https://paperspec.scient.ing/context/scienting-1.jsonld, and
term IRIs https://paperspec.scient.ing/vocab#<term>. Format
identifiers (scienting-*) and URNs (urn:scienting:) are unchanged.
- tools/site.py (standard library only) builds _site/: every file of the
repository at its own path, each Markdown file rendered as a page with
sidebar navigation, heading anchors matching the forge's, folder
listings, a vocabulary page for the context's IRIs, a heading search
and a 404 page; light and dark themes.
- check.py builds the site and checks that every Markdown file has a
page, every internal link and fragment resolves, no Markdown is left
unrendered, and every $id, the context address and the vocabulary IRIs
are files of the site.
- deploy/: a Caddyfile with the media types and CORS the data needs, and
a guide; .gitea/workflows/site.yml builds on main and publishes with
rsync when the SITE_* secrets are set.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
- Add tools/validate.py: validates packages, and with --correction runs
proposed corrections through the gate against a package without
writing anything (spec/11 §11.4). The gate now refuses a proposal that
fails the correction schema, rule correction.schema.
- tools/load.py validates every package before loading, and with
--bundle --built-from builds a scienting-bundle/1 with the FTS5 search
index and bundle_meta (spec/13 §13.5). Search rows are defined per
unit (sentence, cell, equation outside a sentence, figure-text) with
the parent kind as context.
- Roster keys carry a role, and a key with the role owner may revoke any
receipt (spec/08 §8.7, spec/20); roster schema, store table and the
fixture roster updated. The checker signs a trial revocation to prove
the rule both ways.
- A qa: receipt raises the nodes it sampled except those in its errors
(spec/08 §8.2); the example paper's fidelity counts become 27 F3,
13 F2, 4 F1 and 1 F0.
- The destination chooses the keyed scheme, not the text policy:
hmac-team between the team's machines, hkdf-pages outside the team
(spec/05 §5.8, spec/12 §12.5).
- A TextQuoteSelector must repeat the anchor's plain quote and is absent
for hashed or keyed anchors (spec/18 §18.3).
- Add fixtures/records/suspect.json, a scienting-suspect/1 record.
- Oracle: hashes are kept incrementally and checked after every
correction against a full recomputation; load and write refuse unsafe
manifest paths; Ed25519, HKDF and schema validation come from the
cryptography and jsonschema packages; canonical JSON uses the built-in
encoder with an exact RFC 8785 fallback.
- The tools need Python 3.14 with cryptography and jsonschema; the py310
CI environment is dropped and the workflow runs the default only.
- Resolve every [CHECK] note in the docs, READMEs and context; add
CONTRIBUTING.md; every tool answers --help and refuses unknown options.
Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
alexmandClaude