ProofPack v1.0.0 · Released

Operating evidence, packaged.

A local-first compiler for turning operating work into structured, shareable evidence.

Turn logs, commands, checks and deployment artifacts into a structured evidence bundle — locally.

product principle

Backstage stays backstage.

ProofPack packages the evidence you choose to share without turning your private operating environment into the deliverable.

Your work happened once. Its evidence should remain useful.

local-first workflow

Choose the evidence. Compile the package. Review the result.

ProofPack v1 keeps the operating workspace and the public-facing evidence package as separate things.

01

Collect intentionally

Choose the logs, commands, checks, and deployment artifacts that belong in the evidence bundle.

02

Compile locally

Build the bundle in the operator's environment instead of uploading the private workspace to a hosted service.

03

Review before sharing

Inspect the report, manifest, selected artifacts, and checksums as one bounded package.

v1 output

A small, reviewable evidence bundle.

The current compiler produces a report, machine-readable manifest, selected evidence artifacts, and a checksum index.

Generated bundle
Manifestartifact_manifest.json
Reportbuild_report.md
Evidenceartifacts/
Checksumschecksums.sha256

release evidence

Released with a reviewable evidence trail.

ProofPack v1.0.0 is released through public documentation and request access.

Release artifact SHA-256:

66832f2d038bab61ccdbc60a2305337393a39fc6a4391a3c7605cd4f2c937cec

This SHA-256 identifies an internally retained v1.0.0 release artifact. No public ZIP download is currently available.

fictional example · not a customer engagement

Acme Relay shows the v1 package — with fictional data only.

Acme Relay is a deliberately fictional operating scenario built from documentation-safe names, domains, timestamps, and artifacts. It demonstrates the package shape, not a customer outcome.

Fictional Acme Relay bundle

  • Fictional service inventory and deployment notes
  • Fictional health-check and verification artifacts
  • Generated report, manifest, selected artifacts, and checksums
  • No customer systems, credentials, outcomes, or private operating data

public-safe boundary

Example evidence, not customer work.

The public example contains no real operator credentials, private infrastructure, customer identifiers, testimonials, revenue, or claimed outcomes.

Review public-safe work samples

ProofPack v1.0.0 · Released

Start with the evidence you need to make useful.

Request ProofPack