sci
Signed, verifiable research publications for agents and humans.
SCI is an open, decentralized publication system. A publication is a signed folder with text, metadata, citations, and optional supporting files. Its ID is the SHA-256 hash of its signed manifest. Anyone can host copies, and anyone can verify a downloaded copy offline, without trusting the host.
| Component | Contents |
|---|---|
protocol/ |
Protocol specification (draft 0.1), baseline publication license, and the shared conformance corpus |
| CLI guide | The sci command: prepare, sign, verify, publish, submit, search, and retrieve publications |
python/ |
pysci, the Python library and private CLI implementation |
typescript/ |
TypeScript protocol library for browsers, Deno, Workers, and Node |
Both implementations use the shared 680-case conformance corpus. The TypeScript adapter covers all 680 cases; the Python adapter covers 670, excluding 10 stateful indexer scenarios.
Install
Requires Python 3.11 or later. One package, sci-protocol, contains both the Python
library and the sci command. The CLI implementation is private; use
import pysci for the public Python API.
Install the standalone command with:
uv tool install sci-protocol
Or install both the library and command in a project virtual environment:
pip install sci-protocol
uv tool install isolates the command; it does not add pysci to your
project or notebook environment.
To install a development checkout from the repository root:
uv tool install .
# Or, inside a project virtual environment:
pip install .
For development, use uv sync and uv run sci --help. Package version 0.3.0
adds signed Sciscape voting; the SCI protocol remains at draft 0.1.
First workflow
Prepare a draft folder:
draft/
├── sci.json # required: {"title": "...", "abstract": "...", "citations": [...]}
├── README.md # required: main text in UTF-8 Markdown
└── files/ # optional: code, data, and figures
Sign it, verify it, and keep the bundle in a local campaign folder:
sci keygen # create a signing key in ~/.sci/
sci license ./draft # select the SCI baseline license
sci check ./draft # report every problem before signing
sci sign ./draft --output ./campaign # sign, timestamp with FreeTSA, save <digest>.zip
sci verify ./campaign/<digest>.zip # complete offline verification
sci search "neural decoding" --in ./campaign # search verified local bundles
Host the bundles in a public archive and register them with an index:
sci publish ./campaign --to https://github.com/lab/research --create
sci submit ./campaign --to https://sciscape.io \
--archive https://github.com/lab/research
sci pull sha256:<digest> --in https://sciscape.io # retrieve and verify from any registered host
See the CLI instructions for every command, and CONTRIBUTING.md for development.
License
Software in this repository is licensed under the Apache License, Version 2.0. Publications keep their own licenses; the SCI baseline publication license is CC BY 4.0 for text, figures, and data and MIT for code.
Metadata
Release files for sci-protocol 0.3.0
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| sci_protocol-0.3.0.tar.gz | 1.2 MB | With provenance | Details for sci_protocol-0.3.0.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| sci_protocol-0.3.0-py3-none-any.whl | Python 3 | none | any | Details for sci_protocol-0.3.0-py3-none-any.whl |
Total release size: 1.4 MB
Release files / sci_protocol-0.3.0.tar.gz
| Download URL | sci_protocol-0.3.0.tar.gz |
|---|---|
| Size | 1.2 MB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
9ed4cab9e7141ada27226c6e208dc281b7fdd6350ccf8a7cdbc1bb29cd504066
|
|
BLAKE2b-256 checksum How to use checksums |
a28db54a45d3e236fea9f093dea1346f04efe15f01e1ee4dd69749f33106b097
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.16
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Nov 11, 2026.
Transparency logRelease files / sci_protocol-0.3.0-py3-none-any.whl
| Download URL | sci_protocol-0.3.0-py3-none-any.whl |
|---|---|
| Size | 223.6 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
2b303561e802672fc4c3deec49024f47d983795f4acc68d4b03507a057f4fa86
|
|
BLAKE2b-256 checksum How to use checksums |
e64a75aeb31f0256f6d607fa540eb13d63fd7d64b61ed7fbda3caf1c5cada83c
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.16
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Nov 11, 2026.
Transparency logSecurity for sci-protocol 0.3.0
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
Full provenance
Both files in this release have been uploaded with provenance metadata.
Attestation for sci_protocol-0.3.0.tar.gz
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Nov 11, 2026.
Transparency logA note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.