SwarmandBee/defendable-compute-proof-receipt-v0.1

Defendable Compute Proof Receipt · v0.1

The first open, schema-anchored, hash-receipted attestation record for compute assets (GPUs, servers, edge appliances).

A Proof Receipt establishes that a compute asset is identified · visible to runtime · clear of unintended workloads · configured to an operating baseline · passes functional/stress validation — at a specific timestamp, with a defensible evidence chain.

This dataset publishes the v0.1 schemas, protocols, and one real example: the smash RTX 5090 post-renter verification cycle (2026-05-25).

🚨 Important · this is NOT a valuation. A Proof Receipt is a condition record only. It does not establish market value, certified appraisal, warranty status, insurance acceptance, lender acceptance, or legal title. Authorized vocabulary: Proof Receipt · Validated Compute Condition Record · Rent-Ready Evidence Package · Benchmark-Backed Asset Record.

What's in this dataset

dir	content
schemas/	5 JSON Schema (draft 2020-12) files defining the data model
examples/	smash RTX 5090 example: JSON receipt + human-readable MD twin + completion receipt
protocol/	10-phase post-rental protocol + benchmark validation + evidence capture + failure taxonomy

The 5 schemas

1. compute_asset_identity.schema.json — host + GPU(s) + runtime + privacy-aware identifiers
2. compute_proof_receipt.schema.json — top-level receipt artifact (use_case, precheck, findings, remediation, validation, verdict)
3. benchmark_observation.schema.json — per-test observation (test_origin · test_scope · result · evidence_locator · limitations)
4. service_state_observation.schema.json — docker · model server · rental platform · GPU process · storage · runtime
5. receipt_manifest.schema.json — provenance manifest published alongside the receipt

The real example · smash RTX 5090 · 2026-05-25

Observed lifecycle:

1. Renter exited
2. Docker rental artifacts cleaned
3. GPU reset to persistence enabled + 550W rental cap
4. High VRAM condition discovered (28,114 MiB used despite zero containers)
5. Investigation identified the cause as first-party (local SwarmCurator vLLM holding 28,104 MiB)
6. Local model services stopped without touching Vast services
7. RTX 5090 returned to 2 MiB idle / 0% util / ~51 °C / ~21.55W draw / 550W cap / persistence enabled
8. Vast remote validation passed: system requirements · ResNet18 · ECC · NCCL (1 GPU) · combined stress-ng + gpu-burn 60s · test instance destroyed
9. Verdict: 🍯 HONEY — asset returned to verified idle state and passed platform-remote functional/stress validation for rental readiness

The full example is in examples/smash_rtx5090_proof_receipt.example.json (machine-readable) + .md (human-readable twin) + completion_receipt.md (plain-text witness).

Use cases

• Vast.ai readiness lane — issue a Proof Receipt post-cleanup, publish receipt URL in the listing description
• ITAD intake — capture asset condition at receipt-of-equipment time
• Resale readiness — buyer-side evidence package
• Fleet audit — periodic condition record across enterprise GPU inventory
• AIOV future feedstock — when valuation comes later, the condition record is its foundation
• Schema spec for the open AI-trust / compute-attestation community — fork it, extend it, cite us

Doctrine

Tribunal begins before training. No proof, no honey.

The Tribunal gate refuses to issue HONEY unless:

1. All schema-mandatory observations PASS
2. No unresolved findings
3. Named platform-remote or third-party functional/stress validation passed
4. Receipt linter passes (no banned vocabulary in any field)
5. Every evidence artifact is sha256-hashed in the manifest

PROPOLIS-class findings (auto-reject): unknown GPU process · NVIDIA runtime unavailable · CDI device missing · rental platform service down · remote validation failure · unverified asset identity · claim exceeds evidence.

Vocabulary discipline

Authorized terms in receipt fields:

• Proof Receipt
• Validated Compute Condition Record
• Rent-Ready Evidence Package
• Benchmark-Backed Asset Record

Banned in any value field (linter rejects):

• appraisal · valuation · certified · guaranteed · warranted · insurance-backed · lender-accepted · legally proves · accredited

These claims require separate, external attestation chains.

v0.2 roadmap (not in this dataset)

• CLI implementation (defendable-compute intake | observe | remediate | validate | receipt | verify-hashes)
• DefendableLedger publisher integration
• Vast.ai adapter
• AIOV future-integration (separate downstream product)

Source repo

Full v0.1 specification + workspace:

• https://github.com/SudoSuOps/defendableos/tree/main/products/defendable_compute_proof_receipt/v0.1

Operator + Contact

Swarm and Bee LLC · Florida · D-U-N-S 138652395 · DBA Swarm & Bee AI · a surface of DefendableOS

• Email · build@swarmandbee.ai
• X · @swarmandbee
• LinkedIn · Donovan Mackey
• GitHub · SudoSuOps

License

CC-BY-4.0 · attribution to Swarm and Bee LLC · Defendable Compute Proof Receipt v0.1.

---

Books and records. No proof, no honey. To the shed. 🐝