Live Validation

Live validation proves a real provider environment, not just local SDK behavior. Use it before making production claims about IPFS, pinning, gateways, clusters, Filecoin, or policy-backed workflows.

Skipped live-provider scripts are not evidence.

Minimum Evidence

At minimum, keep output that proves:

provider health
encrypted write
read by CID
CID verification
proof metadata
cleanup or retention behavior
redaction of tokens and plaintext

For sharing, messages, sync, Filecoin, or policy workflows, validate those records too.

CLI Checks

npx -p @meshkit/cli meshkit doctor --json
npx -p @meshkit/cli meshkit providers test --json

Repository Live Scripts

Run these only with explicit environment variables:

MESHKIT_LIVE_IPFS=1 MESHKIT_IPFS_API=http://127.0.0.1:5001 npm run providers:ipfs:live
MESHKIT_LIVE_PINNING=1 MESHKIT_PINNING_ENDPOINT=https://pinning.example MESHKIT_PINNING_TOKEN=... npm run providers:pinning:live
MESHKIT_LIVE_GATEWAY=1 MESHKIT_GATEWAY_URL=https://gateway.example MESHKIT_GATEWAY_CID=bafk... npm run providers:gateway:live
MESHKIT_LIVE_CLUSTER=1 MESHKIT_CLUSTER_API=https://cluster.example MESHKIT_CLUSTER_TOKEN=... npm run providers:cluster:live
MESHKIT_LIVE_FILECOIN=1 MESHKIT_FILECOIN_ENDPOINT=https://filecoin.example MESHKIT_FILECOIN_STORAGE=ipfs-http MESHKIT_IPFS_API=http://127.0.0.1:5001 npm run providers:filecoin:live

What To Save

command name
package version or commit
sanitized environment summary
provider endpoint category, not secret values
JSON output
expected failures
follow-up owner for failures

What Not To Save

provider tokens
bearer headers
private keys
decrypted payloads
capability token secrets
unredacted config files

Interpreting Results

Result	Meaning
Pass	The validated workflow worked in that environment at that time
Skip	No evidence; required opt-in or credentials were missing
Fail	Do not make production claims until the failure is understood
Pass for bytes only	Does not prove capsules, mailboxes, sync, policies, or Filecoin