Skip to main content

gnos

gnos is a local-first tool that stores documents as chunks and manages them with manifests. Add files, attest reproducibility, and materialize documents back to disk.

Quick start

gnos init

gnos add README.md

gnos materialize doc <doc_id> --output README.out.md

What you can do

  • Add files and store their chunks locally.
  • Generate doc-manifests that describe how to reconstruct the original bytes.
  • Attest that a manifest can reproduce the original document.
  • Materialize documents back to disk when you need them.
  • Bring your own chunkers for custom strategies.

Why use gnos?

  • Verifiable manifests. A stable schema that actually reconstructs the original bytes.
  • Local chunk store. Chunks are content-addressed and live on your machine.
  • Rebuild anytime. Materialize documents back to disk from manifests + chunks.
  • Derive safely. Create alternate chunk views without changing identity.

Compared to typical chunking tools, gnos gives you a concrete manifest format and a local store you can trust.

Common workflows

Add a file

gnos add notes.md

Add a directory as a collection

gnos add --collection docs/

Verify a manifest directly

gnos attest manifest <manifest_hash>

Shallow integrity check (hash-only)

gnos attest manifest <manifest_hash> --shallow

Derive a non-identity manifest

gnos derive <doc_manifest_hash> --chunking <method>

Materialize a collection

gnos materialize collection <collection_id> --dir ./out

Commands

  • gnos init
  • gnos add <path>
  • gnos add --collection <path>
  • gnos attest manifest <manifest_hash> [--doc-id H] [--shallow]
  • gnos attest file <path> --doc-id H
  • gnos attest doc <doc_id>
  • gnos derive <manifest_hash> --chunking <method>
  • gnos materialize doc <doc_id> --output <path>
  • gnos materialize collection <collection_id> --dir <path>
  • gnos status [--doc <doc_id>]
  • gnos chunker list [--verbose]
  • gnos inspect <hash>
  • gnos list --objects|--documents|--document-manifests|--collection-manifests|--derived-manifests
  • gnos --version

How it works (short)

  • Documents are raw bytes. The document hash is the identity.
  • Chunks are stored by hash. Manifests describe how to reconstruct bytes.
  • Attestation verifies integrity and, when applicable, reconstruction.

Learn more

  • docs/index.md (overview of all docs)
  • docs/spec.md (v1 spec)
  • docs/cli.md (CLI behavior)
  • docs/manifest.md (manifest schemas)
  • docs/chunking.md (chunker rules)
  • docs/plugins.md (custom chunkers)

Metadata

Release files for gnos 0.0.3

For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.

Source distribution (sdist)

Source distribution for gnos 0.0.3
File Size Uploaded Provenance
gnos-0.0.3.tar.gz 34.8 kB With provenance Details

Built distribution (wheel)

Table of built distributions (wheels) for gnos 0.0.3
File Interpreter ABI Platform
gnos-0.0.3-py3-none-any.whl Python 3 none any Details

Total release size: 60.9 kB

Release files / gnos-0.0.3.tar.gz

Download URL gnos-0.0.3.tar.gz
Size 34.8 kB
Tags Source
SHA-256 checksum
How to use checksums
1564ff1be0eb2a55df46807b0a5ee90f76509af7a745d94112c615f890fdf956
BLAKE2b-256 checksum
How to use checksums
bb7014663110a381db6b078638692c705dbd1e94cc2f1fd399d31c31b20bfa55
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/6.1.0 CPython/3.13.7

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 Feb 3, 2026.

Transparency log

Release files / gnos-0.0.3-py3-none-any.whl

Download URL gnos-0.0.3-py3-none-any.whl
Size 26.1 kB
Tags Python 3
SHA-256 checksum
How to use checksums
df346b420b60ad76f9f62d98185c424dce8f9919bd9d4548d228eb9a0d485cc3
BLAKE2b-256 checksum
How to use checksums
0b68a06a6bb6573a05b4bfbcbcc0367b2ec5783804e595691ee39a88d8343c99
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/6.1.0 CPython/3.13.7

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 Feb 3, 2026.

Transparency log

Security for gnos 0.0.3

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

All 2 files in this release have been uploaded with provenance metadata.

Select from 2 files

Attestation for gnos-0.0.3.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 Feb 3, 2026.

Transparency log

A 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.

Anthropic, PBC Visionary sponsor Bloomberg Visionary sponsor Hudson River Trading Visionary sponsor Meta Visionary sponsor NVIDIA Visionary sponsor Microsoft Sustainability sponsor Depot Continuous Integration AWS Cloud computing and Security Sponsor Datadog Monitoring Fastly CDN Google Download Analytics Sentry Error logging StatusPage Status page