Bring your projects
Use ZIPPRI AI Hub organizations, private repositories, and native Git for source history, branches and pull requests.
ZIPPRI / EVIDENCE REGISTRY · BETA R1
Publish what you built.
Prove what you can.
ZIPPRI brings projects, evidence files, immutable release snapshots, SHA-256 checksums and shareable publication receipts into one home—built for researchers, startups, developers and teams.
Evidence is publisher-submitted. ZIPPRI signs file manifests and timestamps; it does not independently verify scientific claims or award third-party certification.
Multi-filePublisher-selected release files
VersionedPermanent publication record IDs
SHA-256File checksums for every release
Ed25519Registry-signed publication manifest
DISCOVER / PUBLIC EVIDENCE
A home for proof, not just files.
Explore publications released by their project owners. Private drafts stay invisible until their owners explicitly publish.
Loading published evidence…
FEATURED / EXTERNAL ARCHIVAL EXAMPLE
RABBIT INDUSTRIES · AGASTYA F3 R2
8 billion source-token milestone
An externally archived company training-evidence case study. This predates the self-service registry and is not presented as a customer-uploaded ZIPPRI Registry record.
CREATE / PUBLISH / VERSION
Create. Upload. Publish.
Use your existing ZIPPRI AI Hub account and project repository. The registry never automatically publishes private uploads.
Sign in to publish evidence
Any verified ZIPPRI customer account with appropriate repository permissions can prepare a draft. New users can sign up through AI Hub.
PRIVATE DRAFT → PUBLIC RELEASE
Beta limits: 10 files · 50 MB totalYour project evidence
GET STARTEDCreate your first project
ZIPPRI keeps your project private until you explicitly publish a version.
STEP 1 OF 2 — YOUR PROJECT
Create or choose a project
Everything starts private. You decide when to publish.
+ Create a new private project
Private by default. Publishing requires your confirmation.
✓
Project selectedSTEP 2 OF 2 — ADD EVIDENCE FILES
Advanced organization and repository controls
+ Create a publishing organization
Your new organization is private to its authorized members. You can then create a private project repository.
+ Create a new project repository (private by default)
Private by default. Only files added to an explicitly published version will become public.
No evidence files selected.
Resumable mode verifies SHA-256 and receives progress from ZIPPRI storage. If upload is interrupted, reselect the same files and resume your private draft.
OPTIONAL / EVIDENCE PASSPORT
Publisher assertions · not reviewedLink what you claim to what you published
For each claim, select one attached evidence file. ZIPPRI signs the claim, file ID and verified SHA-256 inside the same immutable publication manifest. This proves the association, not the scientific truth or quality of the claim.
Attach evidence to a private draft first. Claims are optional (up to 5).
Git commit identity can be checked at publication; file bytes inside Git, scientific claims, and qualified reviewer decisions are separate verification levels. No independent review or accreditation is implied.
Select a repository and prepare your evidence.
A COMPLETE PUBLISHING WORKFLOW
One project. Many evidence versions.
Keep development collaboration and public evidence publishing connected without confusing file existence with research acceptance.
Release selected files
Upload multiple evidence files through existing artifact storage. Every source upload is hashed and inspected before registry publication.
Archive snapshots
Each explicitly published version copies its selected files into a separate immutable publication snapshot, independent of later drafts.
Verify what was published
Download a publisher receipt, signed Ed25519 manifest, SHA-256 hashes and shareable URL; verification is about publication integrity, not scientific truth.
How ZIPPRI fits alongside other tools
| Function | Git providers | Research repositories | ZIPPRI Evidence Registry |
|---|---|---|---|
| Versioned source collaboration | Primary specialty | May link code | Use existing ZIPPRI Git workspace |
| Public evidence files | Releases / repository files | Research deposits | Explicit project publication snapshots |
| Persistent DOI | External integration | Issuer-dependent (e.g. Zenodo) | External DOI can be cited; ZIPPRI does not mint DOIs |
| Cryptographic file manifest | Varies | Varies | SHA-256 + ZIPPRI Ed25519 record signature |
| Independent claims verification | Not automatic | Not automatic | Separate process — not implied by publication |
CLEAR TRUST BOUNDARIES
Integrity first. Claims second.
ZIPPRI's file receipt and signatures are not certificates of performance, originality, regulatory compliance, or research accuracy.
Private until you publish
Draft titles and files are accessible only through authenticated, repository-authorized workflows. Public visitors see published records only.
Publisher control and rights
The publisher confirms distribution rights and public-release consent. Only specifically selected and screened files are copied for public access.
Verifiable manifest
The registry signs canonical publication metadata and file hashes using Ed25519. A public verification endpoint checks the signature and published file bytes.
Limited launch capacity
This beta limits a publication to 10 files, 15 MB each and 50 MB total. More storage, stronger moderation and abuse controls are future expansion gates.
ZIPPRI / CUSTOMER PILOT
Test ZIPPRI with evidence you can safely share.
Use a harmless sample dataset to test the entire journey. Nothing is uploaded or published by this guide.
Public beta test, not certification. Only publish material you have rights to share. Signing the evidence manifest confirms the integrity of a publisher-submitted record, not the correctness of its claims.
Get harmless test files
Download two deterministic test-only documents to your own device. The CSV is larger than 3 MB so you can try resuming an interrupted transfer.
Generated locally in your browser. No test file is sent to ZIPPRI until you explicitly upload it.
Make a private project
Sign in, create your project, and upload both files using Resumable secure upload. For the CSV, interrupt the connection, reopen the draft and reselect the exact file within 24 hours.
Check the private draft and rights permissions. Only then explicitly publish the test version.
Check the publication record
After publishing, paste its ZIPPRI publication ID or public release link. ZIPPRI checks its signed manifest and archived file hashes without requiring an account.
Only verified public releases can return downloadable evidence and an issuer receipt. Private drafts do not appear here.
04 / CUSTOMER CHECKLIST
Capture your pilot results
Mark only steps you personally completed. Verification below comes from ZIPPRI's public API; the other boxes are your own assertions and require independent review.
0 of 4 steps self-reported · No valid public verification captured in this tab.
The report is generated only on your device. It is not submitted to ZIPPRI automatically and is not a certificate or an approved acceptance record.
For the full pilot acceptance, an independent user must also confirm the public ZIP, PDF receipt and evidence hashes from a second browser, then complete a published-file recovery drill. The steps above do not automatically certify a customer account or any project.
COMMON QUESTIONS
Good evidence starts with clear terms.
Can any user publish on ZIPPRI?
Any verified ZIPPRI AI Hub user who is an owner, admin, maintainer or developer of a repository can prepare an evidence release, subject to the beta limits and checks. Anonymous publishing is not enabled.
Can I upload multiple files for one research project?
Yes. Each file is uploaded as a native immutable artifact revision, then deliberately attached to a private evidence draft. Publishing makes selected files publicly downloadable as a versioned snapshot.
Does ZIPPRI issue DOI numbers like Zenodo?
No. ZIPPRI provides its own durable publication URL and cryptographically signed manifest, but it does not currently issue Crossref/DataCite DOI identifiers. A DOI from an authorized external archive can be cited separately.
Is the ZIPPRI receipt an independent certificate?
No. It is an operator-issued record confirming publication identity, timestamp and file fingerprints. It is not independent verification of the submitted project or its claims.
Can I publish changes to a previously released project?
Yes. Create a new version for the same repository. Existing published versions remain separately addressable. Withdrawals disable the public ZIPPRI download endpoint, but cannot recall files that others already downloaded.