Independent verification and reputation from public evidence.
Proof of Ship is the public home for the product narrative, protocol surface, schemas, landing-page source for proofofship.com, and a small Python CLI for deterministic public score math.
What has this person actually built, and how credible is that claim?
- Site: https://proofofship.com
- Docs index:
docs/ - CLI reference:
docs/cli.md - Public surfaces:
docs/public-surfaces.md - Schemas:
docs/schemas/proofofship/ - Examples:
examples/
- public README and docs
- public JSON schemas and checked-in examples
- landing-page source for
proofofship.com - a Python CLI for deterministic score math, badge URLs, URL helpers, and public-surface checks
- contribution, security, and review config for the public surface
- secrets or environment-specific configuration
- operator-only runbooks and machine-local assumptions
- unsupported claims beyond what this repo actually documents and exposes
- proprietary enforcement, anti-abuse, or operator-side trust logic
This repo is the public contract, documentation, schema, and CLI surface for Proof of Ship. Some enforcement and trust-boundary logic remains intentionally proprietary.
- A builder ships work in a public repo.
- A local tool generates a proof envelope.
- Proof of Ship independently re-verifies the claim against the public record.
- Verified work contributes to a deterministic public score surface. Human reputation is cumulative; recent activity is shown separately; non-human actors can remain more recency-sensitive.
- Anyone can inspect the rules and recompute the score from public inputs.
No self-reported prestige. If it cannot be independently verified, it does not count.
The first public product surface is a Python CLI.
pip install -e .proofofship score examples/score.sample.json --handle example-builder --json
proofofship receipts example-builder examples/score.sample.json --json
proofofship check-public-surface --jsonproofofship weight <age_days>— compute recent-activity recency weight (override by actor kind if needed)proofofship score <file> --handle <handle> --json— emit a publicscore.json-style payload with lifetime reputation and recent activityproofofship receipts <handle> <file> --json— emit a publicreceipts.json-style payloadproofofship badge <verified|receipts> <handle>— emit badge URLs or embeddable markdownproofofship urls <handle>— print canonical public profile URLsproofofship validate— validate checked-in public examples against bundled schemasproofofship check-public-surface— verify expected files, valid examples, and absence of obvious secret-like strings
- live landing page at
proofofship.com - public badge assets
- public profile, score, receipts, ledger, and scoreboard route shapes
- public schemas and checked-in examples
- public CLI for scores, receipts, badges, URLs, schema validation, and repo checks
- non-decaying human reputation plus a separate recent-activity signal; stricter recent-activity decay for non-human actors
- GitHub OAuth and account/repo-linking contract
- verifier architecture and verification-depth semantics
- ledger and reputation contracts
- badge guidance and public payload shapes
- GitHub OAuth web login implementation
- account/repo-linking UI
See docs/public-surfaces.md for the live vs repo-shipped vs contract-only map.
docs/— public docs indexdocs/specs/— protocol, ledger, scoring, auth, and architecture specsdocs/cli.md— CLI referencedocs/public-surfaces.md— live vs repo-shipped vs contract-only surfacesdocs/web/site/— static source for the public siteexamples/— checked-in public payload examples
ship-receipts— local receipt generator / evidence layerproofofship— independent verifier and public trust surface
- Site: https://proofofship.com
- Public profiles:
https://proofofship.com/u/<handle> - Public score JSON:
https://proofofship.com/u/<handle>/score.json - Public receipts JSON:
https://proofofship.com/u/<handle>/receipts.json - Public badges:
https://proofofship.com/badges/verified.svg,https://proofofship.com/badges/receipts.svg
Apache 2.0. See LICENSE.